[Samsung Gear 2] biktor_gj:
The sensor is the same yes, but the interfaces are completely different. Despite the fact that camera libraries from the Gear 1 don't work in any Android Wear > 4.3, the Gear 1 uses all Exynos 4 code (like the Galaxy 2)

The Gear 2, uses a similar code to what can be found on the Galaxy S5 for the camera communication, which is entirely different code.

It's interesting to see from a developer perspective at least, this is where it dies when you attempt to open it in Android:

[ 84.499129] [0] 1661 FIMC_IS runtime resume in
[ 84.499765] [0] 1661 [RSC] fimc_is_runtime_resume: QoS LOCK [INT(135000), MIF(400000), CAM(0), DISP(100000)]
[ 84.499826] [0] 1661 [RSC] fimc_is_runtime_resume: QoS LOCK [CPU(400000)]
[ 84.499868] [0] 1661 exynos3_fimc_is_cfg_clk
[ 84.499952] [0] 1661 sclk_mpll_pre_div : 400000000
[ 84.499994] [0] 1661 xusbxti : 24000000
[ 84.500086] [0] 1661 mcu_isp_400 : 400000000
[ 84.500118] [0] 1661 mcu_isp_400_div0 : 200000000
[ 84.500152] [0] 1661 aclk_mcuisp_div1 : 100000000
[ 84.500225] [0] 1661 isp_266 : 100000000
[ 84.500272] [0] 1661 aclk_div0 : 50000000
[ 84.500321] [0] 1661 aclk_div1 : 50000000
[ 84.500373] [0] 1661 aclk_div2 : 50000000
[ 84.500420] [0] 1661 isp_uart : 66666666
[ 84.500479] [0] 1661 isp_spi1 : 100000000
[ 84.500539] [0] 1661 isp_spi0 : 100000000
[ 84.500582] [0] 1661 isp_cam1 : 24000000
[ 84.500739] [0] 1661 FIMC-IS runtime resume out
[ 84.547350] [0] 1661 [@]fimc_is_fw2.bin version : 5E3250 5132-2014/03/05 12:39:55]O13LHC02SB
[ 84.547841] [0] 1661 [@]Camera: the default FW were applied successfully.
[ 84.548027] [0] 1661 fimc_is_ischain_power : PA_FIMC_IS_GIC_C : 0x000000fc
[ 84.548074] [0] 1661 [@]fimc_is_ischain_power(1) - A5 Power on
[ 84.548117] [0] 1661 [@]fimc_is_ischain_power(1)
[ 84.548157] [0] 1661 [@][ISC:D:0] fimc_is_ischain_open(0)
[ 84.548296] [0] 1661 [@][SCC:V:0] fimc_is_scc_video_open
[ 84.548378] [0] 1661 [@][SCP:V:0] fimc_is_scp_video_open
[ 84.566286] [0] 2633 [@]IS Version: 244.130 [0x00]
[ 84.651332] [1] 1661 [@][ISP:V:0] [SS0:V:0]
[ 84.651371] [1] 1661 [ISP:V:0] [3A0:V:0]

So, I can see the firmware is pushed, the camera processor is activated, and the scalers are attached. Original Tizen Kernel didn't use the "ISP" device (still don't know what that is ;)) I enabled it at board-b2-camera.c, and now it starts.

When ISP tries to link itself to 3a0 device (which I don't know either what it is or what it does), a kernel crash happens.

This kernel crash comes from this piece of code:

/drivers/media/video/exynos/fimc-is-device-sensor.c:

...
int fimc_is_sensor_g_module(struct fimc_is_device_sensor *device,
struct fimc_is_module_enum **module)
{
int ret = 0;

BUG_ON(!device);
BUG_ON(!device->subdev_module);
...

The device is found (first BUG_ON line), but the subdev_module isn't, so the kernel stops un BUG_ON function.

Before patching some other code line I can't find right now, it wasn't even finding the 3aa device. It said something like "I'm looking for device 3aa.0 but I'm not finding it, and something is telling me the 3aa device is 3aa.5, which doesn't exists)

So, something is going on with the 3aa device, and it seems it's what's making it crash. Still looking though!

By the way, the 3aa device is one of the devices used by tizen for the camera, so it's possible that it's patched in some way to work for that and that's why it's crashing on ISP...

We'll see ;)

Edit: forgot to say, wether I can make the camera work or not, there are still some builds to come, so don't worry, we're not done yet ;)