09:56 <jcarlos> One question please. I have a copy of my RK3188 tablet recovery partition (recovery.img). I got it with rkflashkit. If I unpack the img file with unpackbootimg command I get recovery.img-zImage and recovery.img-ramdisk.gz. Are those files rkcrc-signed, o must I sign them with "rkcrc -k" before flash them to /kernel and /recovery partitions?

09:57 <jcarlos> In other words, how can I know if a file is rkcrc-signed?

12:51 <naobsd> jcarlos: yes, kernel-only(zImage) and ramdisk-only(cpio+gz) files need to be converted with rkcrc -k.

12:52 <naobsd> jcarlos: first 4 bytes are K R N L

12:53 <jcarlos> naobsd: So when you unpack you lose the sign?

12:54 <naobsd> what is "unpack"?

12:54 <naobsd> kernel+ramdisk file format is different

12:54 <jcarlos> unpackbootimg

12:55 <naobsd> it doesn't have KRNL

12:56 <jcarlos> naobsd: Ahh. So you must sign only when using kernel or ramdisk alone, not when there are packed

12:56 <naobsd> if you want kernel-only and ramdisk-only image, it needs header (start with KRNL) and trailing crc

12:56 <jcarlos> Ok, ok

12:56 <jcarlos> I understand now

12:57 <naobsd> kernel+ramdisk format is different, it can be packed by mkbootimg for RK

12:57 <jcarlos> Mmmm

12:57 <jcarlos> mkbootimg in cyanogenmod is for RK?

12:58 <jcarlos> Or must I use a different version?

12:58 <naobsd> I don't know about recent CM source, probably no

12:58 <jcarlos> So I must replace mkbootimg with an RK-adapted version?

12:58 <naobsd> you should use different(RK) version until it supports RK format clearly

13:00 <jcarlos> naobsd: An url for this RK version, please?

13:01 <naobsd> https://github.com/naobsd/cm_system_core/tree/ics-rockchip-naobsd/mkbootimg here is my version (there are some other mkbootimg for RK)

13:01 <naobsd> it can be compiled without full android build

13:03 <naobsd> cc -o mkbootimg mkbootimg.c -lcrypto

13:03 <naobsd> unpackbootimg is same as CM

13:04 <naobsd> mkbootimg --kernel zImage --ramdisk ramdisk.gz -o newboot.img

13:05 <naobsd> you can check mkbootimg is really for RK by unpack boot.img then repack boot.img without modification. both images must be same

13:09 <jcarlos> naobsd: Thanks

21:34 <jcarlos> One question please. I have a copy of my RK3188 tablet recovery partition (recovery.img). I got it with rkflashkit. If I unpack the img file with unpackbootimg command I get recovery.img-zImage and recovery.img-ramdisk.gz. But my "file" command says recovery.img-zImage is not a "Linux kernel ARM boot executable zImage" file, it says simply "data". Am I missing anything?

21:36 <Markus34> Hello, This is the first time I come here, may I Ask some questions ?

22:51 <FergusL> just go on Markus34 !

22:51 <FergusL> there is a motto that says : don't ask to ask, just ask

22:51 <FergusL> I looked at the latest Rk3188 tablets Markus34

22:52 <FergusL> they've gotten even cheaper

22:52 <FergusL> but i don't know of recent progress regarding installing Linux on i

22:52 <FergusL> I'm really looking forward to doing that as well

22:53 <Markus34> I allready have and use a pengpod700, but would like know if it's possible on a Rockchip tablet as well

22:54 <FergusL> I think it was for Rk3166 but that must be almost one year ago

22:54 <FergusL> a guy said he was working on one model, Pipo S1 iirc, and then he disappeard !

22:55 <Markus34> But what about this git repository(https://github.com/dnkn/rk3188_tablet) ?

22:55 <FergusL> first thing I would do when looking at a model would be googling "<model name> linux"

22:56 <Markus34> Isn't it for rk3188 sources to compile ?

22:57 <FergusL> yes, it must be

22:57 <FergusL> but it's different from one model to aniother

22:57 <FergusL> all tablets don't have the same components

22:58 <FergusL> and even with the same components, the electrical circuits on the electronic boards (PCBs) can be different

22:58 <FergusL> all that has to be taken in account

22:58 <Markus34> Yes, your right

22:59 <Markus34> I'll hold on until I find

22:59 <FergusL> look on XDA developers forum

22:59 <FergusL> there are forum for specific devices

23:00 <FergusL> often same devices have different names depending on manufacturer

23:01 <Markus34> Ok, thanks for your answers

23:01 <Markus34> cheers

23:01 <FergusL> you're welcome, again I'm interested in the same thing as you !

23:01 <FergusL> why do you want linux on an rk tablet ?

23:03 <devgiant> you guys can read more about the dnkn/rk3188_tablet kernel sources on the forum post at http://www.freaktab.com/showthread.php?7732-rk3188-tablet-kernel-sources

23:03 <FergusL> also, in the folders of this repo, there must be a "board" folder with files inside that defines connections depending on the board model, there you should find the names of the corresponding boards or even devices

23:04 <Markus34> My researches have pointed to this link (http://linux-rockchip.info/mw/index.php?title=Main_Page), and seemed to be a good start !

23:04 <FergusL> also, note that kernel does not necessarily mean Linux

23:04 <FergusL> well it does because of the name...

23:05 <FergusL> but not "Linux" as one might mean it : Linux being a whole os including a desktop environement etc...

23:11 <FergusL> that's an interesting question for the peopling knowing the details here btw

23:11 <Markus34> devgiant, it's a very good link indeed

23:12 <FergusL> what are the next step for running linux instead of Android when one has the kernel sourcesd ?

23:16 <devgiant> Markus34: some of the work is already done, but there is more stuff to be sorted out

23:17 <naobsd> oh, one more git repo without history...

23:17 <FergusL> hehe...

23:18 <naobsd> btw, anyone can try Linux on RK devices without kernel source

23:18 <Markus34> how ?

23:18 <Markus34> virtualization ?

23:19 <naobsd> just using stock kernel

23:20 <FergusL> yes, but where is the "switch", the configuration that makes that it starts a Linux distro instead of Android ?

23:20 <naobsd> of course it doesn't satisfy someone who want kernel source

23:22 <naobsd> here is one example http://androtab.info/rockchip/multiboot/

23:22 <naobsd> it's just PoC, not so good example, but it should work

23:23 <devgiant> im thinking in trying this

23:23 <devgiant> https://plus.google.com/+IanMORRISON/posts/9DvTKTy99Yy

23:24 <devgiant> (on my rikomagic mk802iv)

23:27 <naobsd> please try any "Linux for RK". what I wanted to say is, it's not only some specific product

23:29 <naobsd> I think if there is kernel source, it's better than nothing, of course.

23:29 <FergusL> did you try on any device ?

23:29 <FergusL> to run linux

23:31 <naobsd> me? sorry, I don't have "any device". I tried my ramdisk on some(few) RK3188 and RK3066 sticks

23:32 <naobsd> well, "please try any "Linux for RK". what I wanted to say is, it's not only some specific product" this doesn't say please use "Linux for RK" with my ramdisk.

23:33 <jcarlos> One question please. I have a copy of my RK3188 tablet recovery partition (recovery.img). I got it with rkflashkit. If I unpack the img file with unpackbootimg command I get recovery.img-zImage and recovery.img-ramdisk.gz. But my "file" command says recovery.img-zImage is not a "Linux kernel ARM boot executable zImage" file, it says simply "data". Am I missing anything?

23:33 <naobsd> you may use "someone's Linux only for your RK device" if it's available

23:37 <naobsd> my ramdisk is not Linux distro. I just said there is another way to run Linux other than "Linux distro only for some specific RK product"

23:37 <naobsd> my ramdisk is one of "another way"

23:37 <FergusL> what is "your ramdisk" ?

23:37 <naobsd> http://androtab.info/rockchip/multiboot/

23:40 <naobsd> this is just an example. no need to follow my rule such as "put linuxroot.img or make linuxroot directory"

23:40 <FergusL> really interesting

23:40 <FergusL> this is important info

23:40 <FergusL> I'm sure I'm not the only one being confused about "what" is Linux

23:40 <naobsd> I'll change my rule soon ;)

23:41 <FergusL> ha ?

23:41 <FergusL> should anything work with multiboot ?

23:42 <naobsd> sorry, what is "anything" for example?

23:43 <naobsd> basically it just do "switch_root /new_mounted_rootfs /new_init_command"

23:43 <FergusL> Xorg server

23:45 <naobsd> http://youtu.be/UROLssY4yv4 http://youtu.be/cFDDMQu1Syc

23:46 <naobsd> well

23:46 <FergusL> that's great

23:46 <naobsd> I have no idea that what kernel function can be run on someone's stock kernel

23:47 <FergusL> so a screen and touch interface should work similarly

23:48 <naobsd> ah, I don't say it supports all RK hardware function

23:48 <naobsd> TS should work with stock kernel

23:49 <FergusL> because that's the kernel that defines all pinout and output types, right ?

23:49 <FergusL> so it's abstracted

23:49 <naobsd> but I have no idea that some Linux program such as X can handle TS event from device driver for your device

23:49 <FergusL> ok

23:50 <naobsd> but you should be able to get source of distro, it's possible to modify source outside of kernel

23:52 <naobsd> I don't guarantee that everything can work nicely

23:52 <naobsd> but you may try yourself, not waiting someone's Linux specialized for some product

23:53 <naobsd> it's important anyone can try, even if it's not perfect

23:53 <FergusL> so ultimately it's really stupid to make tutorials for ONE device

23:53 <FergusL> it should be generic

23:53 <FergusL> with guidelines