[Samsung Gear 2] biktor_gj:
Well it's hard to say since a lot of problems might arise from the kernel, I'll try to explain what I have done and where to go from here:

I've been working with two kernel trees:

1. Tizen shipped kernel (exynos 3250&3470 support)

2. S5Mini kernel (only exynos 3470)

I dismantled the tizen kernel into pieces and backported the machine configuration files and every driver I could find. I also have rewritten the kernel config file basing it on the tizen defonfig, universal board and kmini board. It should have all it needs now ;)

While doing this, I got rid of the DMA-CMA function Samsung has developed for Tizen (a function to reserve memory in contigous blocks, to say it in a very bad and very approximate 'human readable' way). This was colliding with the ION memory manager, which is what most android phones use, and a part of the S3C framebuffer requirements.

With the memory issues out of the way, I got rid of the exynos DRM driver and reworked the universal board's display which was designed originally for the s3c framebuffer and cleaned it up to remove the unused display panels.

From there I've spent about a week patching the S3C frame buffer driver to make it work with the new kernel. It partly works, but it cant wake up the display from suspend, which will probably take time to fix too.

That's more or less where I am right now, so fix tasklist goes as follow:

1. LCD poweron from suspend (the driver tells it to but the message gets lost somewhere and screen stays off)

2. DC motor regulator gives an error and makes the kernel crash. I noticed it while on recovery

Probably a lot more will come...

In this kernel, which is what Ill work on exclusively from now on, it's working:

Boot (yay!)

MMC (read/write)

Display on framebuffer mode (as long as screen stays on ;))

Touch screen

Audio (untested but correctly detected and exposed)

Bluetooth (same as above)

USB: ADB and MTP

All android required functions from the kernel seem to be working, but probably there'll be some issues with the charger reporting (I think it might come from the same issues with the vibrator)

Also the recovery/normal boot up works as in the other kernels

From now, besides fixing the issues fron the kernel I need to:

Make TWRP compile in my android source. I swear I followed all the instructions I could find, but it takes ages each time and it always breaks. Does anyone know any good porting guide for TWRP?

Android port:

I used one of my first wear boot images and of course it didnt boot, but it entered a bootloop when failing to load the missing eGL driver, since it was trying to load the emulator library. That's A TON MORE than what it did with any other kernel I used. I 'borrowed' the device tree from cyanogenmod for the gradalte and the kmini lte devices and will be trying to compile android this weekend. I'm optimistic that if I manage to compile it, I might be able to get to the desktop with this kernel, even if half of the things aren't working right now, at least it's more feasible than rewriting the graphics allocator from scratch, which was the other choice if I was to keep the drm driver...

Time will tell!

If anyone can find me a Cyanogenmod flash dump / cwm zip / tar file from any of these devices, it would be great:

Samsung Degas (tablet)

Samsung Kmini lte (g800 - the exynos 3470 variant, not the MSM one)

Samsung Grada LTE (I think its called galaxy light or something like that...)

They all share the cpu on the exynos and would come really handy to retrieve proprietary libraries...