Hi,
I've just bought a Justop mk809b (or mk809bii depending on your naming scheme), it does all I need (serving multimedia to my TV) but runs hot so I'm planning to fit either a heatsink or cooling fan (or both).
First of all though I'd like to patch the kernel to export the CPU temperatures to sysfs so I can see whether my alterations make any differences (if this is already supported in a particular kernel please let me know), and ideally to then allow variable fan control based on CPU temps.
I'm not new to Android device and kernel hacking, but I am new to the Rockchip platform, my previous experience was with the Samsung Galaxy Tab (getting Meego/Linux booting on the device.)
It appears that most of the Android stick manufacturers don't release kernel source, but that there have been some leaks and perhaps also some kosher source releases. From my forum research it looks like at least some of the kernels used for Android systems are binary patched (e.g. to simply increase the output res), but perhaps some are also built from source, there are so many it's quite hard to tell what's what. The things like PicUntu (sp?) compile their own kernels but I'd prefer to stick with Android as it works well on the TV screen.
It appears there are a fair few mk808 releases (Android "ROM" updates), but fewer for the mk809 - it's hard to know whether this is due to the mk808 being older, as certainly the core hardware looks to be pretty much the same, with presumably a change in the wifi (and where included Bluetooth) chipset.
What is the situation re closed source modules - graphics, wifi and Bluetooth? My device has MediaTek MT5931SA Wifi and MediaTek MT6622N Bluetooth and a quick search doesn't turn up any Linux drivers, so presumably it would be a case of reverse engineering or simply compiling the same kernel with the same compiler so they can still be used (which was what we did on the Samsung Galaxy Tab).
I'd appreciate any comments and any recommendations from people who've been doing this for a while on this platform, especially on things like kernel source repos that produce code known to work with Android (and the closed binaries); tools to extract and create img files and pre-built cross compilers (e.g. is there one that tends to be used that can be downloaded from e.g. CodeSourcery or is it a case of building your own to match the kernel in question? - yuck!)
Thanks
I've just bought a Justop mk809b (or mk809bii depending on your naming scheme), it does all I need (serving multimedia to my TV) but runs hot so I'm planning to fit either a heatsink or cooling fan (or both).
First of all though I'd like to patch the kernel to export the CPU temperatures to sysfs so I can see whether my alterations make any differences (if this is already supported in a particular kernel please let me know), and ideally to then allow variable fan control based on CPU temps.
I'm not new to Android device and kernel hacking, but I am new to the Rockchip platform, my previous experience was with the Samsung Galaxy Tab (getting Meego/Linux booting on the device.)
It appears that most of the Android stick manufacturers don't release kernel source, but that there have been some leaks and perhaps also some kosher source releases. From my forum research it looks like at least some of the kernels used for Android systems are binary patched (e.g. to simply increase the output res), but perhaps some are also built from source, there are so many it's quite hard to tell what's what. The things like PicUntu (sp?) compile their own kernels but I'd prefer to stick with Android as it works well on the TV screen.
It appears there are a fair few mk808 releases (Android "ROM" updates), but fewer for the mk809 - it's hard to know whether this is due to the mk808 being older, as certainly the core hardware looks to be pretty much the same, with presumably a change in the wifi (and where included Bluetooth) chipset.
What is the situation re closed source modules - graphics, wifi and Bluetooth? My device has MediaTek MT5931SA Wifi and MediaTek MT6622N Bluetooth and a quick search doesn't turn up any Linux drivers, so presumably it would be a case of reverse engineering or simply compiling the same kernel with the same compiler so they can still be used (which was what we did on the Samsung Galaxy Tab).
I'd appreciate any comments and any recommendations from people who've been doing this for a while on this platform, especially on things like kernel source repos that produce code known to work with Android (and the closed binaries); tools to extract and create img files and pre-built cross compilers (e.g. is there one that tends to be used that can be downloaded from e.g. CodeSourcery or is it a case of building your own to match the kernel in question? - yuck!)
Thanks
Comment