[Samsung Gear 2] biktor_gj:
Unless my watch breaks (which I honestly hope it doesn't happen anytime soon) I'm not giving up ;)

Not much to say except stuck here:

[ 1.695397] [0] 1 s3c-fb exynos3-fb.0: PSR mode is 2(0: VIDEO, 1: DP, 2: MIPI)
<3>[ 1.695890] [0] 1 s3c-fb exynos3-fb.0: failed to request min_freq for mif
<3>[ 1.695947] [0] 1 s3c-fb exynos3-fb.0: failed to request min_freq for int
<6>[ 1.696121] [0] 1 s3c-fb exynos3-fb.0: IOVMM: IOVM SIZE = 0x40000000 B, IOVMM from 0x10000000.
<6>[ 1.696238] [0] 1 s3c-fb exynos3-fb.0: IOVMM: IOVM SIZE = 0x40000000 B, IOVMM from 0x50000000.
<6>[ 1.696331] [0] 1 s3c-fb exynos3-fb.0: IOVMM: IOVM SIZE = 0x30000000 B, IOVMM from 0x90000000.
<6>[ 1.696412] [0] 1 s3c-fb exynos3-fb.0: IOVMM: IOVM SIZE = 0x10000000 B, IOVMM from 0xc0000000.
<6>[ 1.696494] [0] 1 s3c-fb exynos3-fb.0: IOVMM: IOVM SIZE = 0x10000000 B, IOVMM from 0xd0000000.
<4>[ 1.696627] [0] 1 s3c-fb : Probing Framebuffer 0s3c-fb : Probing Framebuffer 1s3c-fb : Probing Framebuffer 2s3c-fb : Probing Framebuffer 3s3c-fb : Probing framebuffer 4
<4>[ 1.700382] [0] 1 s3c-fb exynos3-fb.0: failed to find bootloader framebuffer
<4>[ 1.700445] [0] 1 s3c-fb exynos3-fb.0: couldn't copy bootloader framebuffer into default window; clearing instead
<4>[ 1.700516] [0] 1 s3c-fb -- s3c fb clear fb -- start
<4>[ 1.700559] [0] 1 s3c-fb -- s3c_fb_clear_fb: BUF BEGIN CPU ACCESS
<4>[ 1.700720] [0] 1 s3c-fb -- s3c_fb_clear_fb: BUF BEGIN CPU ACCESS- DONEs3c-fb -- s3c fb clear fb -- end
<4>[ 1.701150] [0] 1 s3c-fb -- s3c fb inactivate window 0
<1>[ 1.701202] [0] 1 Unable to handle kernel NULL pointer dereference at virtual address 00000020
<1>[ 1.701265] [0] 1 pgd = c0004000
<1>[ 1.701299] [0] 1 [00000020] *pgd=00000000
<0>[ 1.701351] [0] 1 Internal error: Oops: 5 [#1] PREEMPT SMP ARM
<4>[ 1.701402] [0] 1 CPU: 0 Not tainted (3.4.39 #15)
<4>[ 1.701457] [0] 1 PC is at s3c_fb_probe+0xbc4/0xf80
<4>[ 1.701504] [0] 1 LR is at console_unlock+0x224/0x24c
<4>[ 1.701550] [0] 1 pc : [<c052b3b4>] lr : [<c002e38c>] psr: 60000013
<4>[ 1.701594] [0] 1 sp : df843e08 ip : 60000013 fp : df843e6c
<4>[ 1.701641] [0] 1 r10: 00000004 r9 : e0188000 r8 : df8eb380
<4>[ 1.701688] [0] 1 r7 : 000000c8 r6 : 00000008 r5 : df813810 r4 : dfa8ba00
<4>[ 1.701741] [0] 1 r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000042
<4>[ 1.701796] [0] 1 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
<4>[ 1.701855] [0] 1 Control: 10c5387d Table: 4000406a DAC: 00000015
<4>[ 1.701903] [0] 1 CPU 0 / CLUSTER 0
<4>[ 1.701937] [0] 1 DFSR: 00000005, ADFSR: 00000000, IFSR: 00000000, AIFSR: 00000000
<4>[ 1.701993] [0] 1 CPUFREQ: 0 KHz
<4>[ 1.702025] [0] 1

I found out that even if the 3.10 kernel boots and powers up the display, it's not going to be of much use unless I rewrite the entire gralloc library so it can use the framebuffer bundled in the exynos drm driver, so I've spent most of past week reassembling the S5 Mini (kminilte) kernel with the original bundled tizen kernel from samsung.

Fun fact of the day: Exynos 3470 (k mini lte/ degas/ some more phones and tablets) and Exynos 3250 are virtually the same. In fact the Exynos 3250 is written in the kernel tree as 0xE3472, so I'm guessing 3250/3470/3472 are essentially the same. Could it have 4 cores, but they disable 2 to lower the power consumption? who knows...