00:28 <Elijah_> sjoerd: radxa rock pro

00:28 <Elijah_> Running off the SD card

00:29 <Elijah_> Kernel 3.18 does seem to be working aside from the HDMI video

00:43 <Elijah_> wanted to get the usbtv driver

00:43 <Elijah_> it does seem to be recognizing my EasyCap now, will have to find an NTSC source to test it out

00:48 <Elijah_> interestingly, the MAC address is still not what's passed on the kernel command line

05:05 <cyrozap> Hi, all, I'm trying to wrap my mind around the RK3188 boot process, but I've had a hard time finding up-to-date information. I have a Tronsmart MK908 II that I'd like to boot with U-Boot and use the latest kernel, but I know there's a whole proprietary booloader that gets in the way with its weird partitioning scheme and parameter file. I've recently stumbled upon [this](https://github.com/apxii/rk

05:05 <cyrozap> boottools) which makes me think that I might be able to use U-boot, but it hasn't been updated in two years.

05:07 <cyrozap> There's also https://github.com/neo-technologies/rockchip-mkbootimg and https://github.com/neo-technologies/rockchip_u-boot, but I'm not sure how they would fit or even if they would be useful for what I'm trying to do.

07:06 <naobsd> cyrozap: what do you want to do?

07:23 <cyrozap> naobsd: In a nutshell, I want Arch Linux ARM running on my MK908.

07:25 <cyrozap> naobsd: Also, kinda what this guy is doing: http://www.omegamoon.com/blog/index.php

07:26 <cyrozap> I just want that pure, Linux-y goodness on my tiny TV PC without all the Android cruft ;)

07:28 <naobsd> then I think bootloader is not important part, proprietary loader is also good for that

07:37 <cyrozap> Are there any instructions on getting plain linux booting on it anywhere? Everything I've seen is just "Here, run these .exe's and flash your device with these images. Sources? What are those?"

07:38 <naobsd> do you have kernel source for your device?

07:38 <cyrozap> Yes, but only 3.0.101 (plus patches): https://github.com/omegamoon/Rockchip-GPL-Kernel

07:41 <naobsd> hmm, source without history... not so good, but if it's surely working, better than nothing

07:41 <naobsd> then you can make kernel binary from source

07:41 <naobsd> what you need is root file system

07:42 <naobsd> there is tarball on archlinuxarm.org

07:44 <naobsd> http://os.archlinuxarm.org/os/ArchLinuxARM-armv7-latest.tar.gz will work

07:47 <cyrozap> Ok, so the general idea is, create an ext4 image, loopback mount it, extract the tarball to the mounted image, unmount, and use that as the "system.img" partition?

07:47 <naobsd> ah, well,

07:48 <naobsd> you may need to modify kernel command line in parameter

07:48 <cyrozap> What exactly is the "boot" partition? I'm familiar with a BIOS/UEFI boot flow, but ARM/Android stuff seems totally different...

07:48 <naobsd> system partition may not so large

07:49 <naobsd> it's almost Rockchip stuff than ARM/Android stuff

07:49 <naobsd> boot partition is for initramfs(root fs on ram)

07:50 <cyrozap> Ah, so is it just a raw initramfs image or is something tricky done to it?

07:50 <naobsd> well

07:50 <cyrozap> Because I know how to work with those

07:50 <naobsd> with rockchip bootloader, you can put cpio(+gz) initramfs (with RK header) to boot partition, or

07:51 <naobsd> you may put kernel+initramfs image on boot partition

07:52 <naobsd> (you may put kernel+initramfs+resource(RK specific, dtb + logo package) image on boot if you are using rk3288 or later SoC)

07:52 <naobsd> if you put ramdisk only image on boot partition, you also need to put kernel image on kernel partition

07:54 <naobsd> for kernel/ramdisk separated image, you need to convert raw kernel binary/raw ramdisk image by mkkrnlimage command

07:56 <naobsd> for kernel+ramdisk combined image, you need to use mkbootimg command _Rockchip version_ (there is AOSP version which doesn't work for Rockchip devices)

07:58 <cyrozap> Ok, I think that's enough to get me started. Thanks for your help!

08:00 <naobsd> you may use rkcrc (instead of mkkrnlimg) from https://github.com/linux-rockchip/rkflashtool

08:01 <naobsd> about mkbootimg for Rockchip, there are several forks, probably this will work https://github.com/neo-technologies/rockchip-mkbootimg

08:03 <naobsd> you can use rkflashtool to modify parameter and flash images

08:07 <cyrozap> Yup, I already have both :)

08:08 <cyrozap> Though it appears as though rkflashtool can't flash the Loader.bin itself--I used the Windows utility to wipe the flash earlier today and I had to use it again to recover.

08:08 <cyrozap> I suppose that means mask-rom flashing hasn't been reversed yet?

08:09 <cyrozap> (that is, flashing while booted from the mash ROM)

08:09 <cyrozap> *mask

08:09 <naobsd> yes and no

08:09 <naobsd> protocol is known

08:10 <naobsd> data for NAND cannot be made yet, or just no one tried yet

08:10 <naobsd> flashing loader on eMMC is known to work

08:11 <naobsd> you can send loader with rkflashtool l/L with mask rom mode

08:12 <naobsd> you can write IDB (which contains loader and some other data) with rkflashtool j

08:16 <cyrozap> I see, I didn't really know what those did. So if I wanted to flash a loader (*.bin) from neo-technologies/rockchip-bootloader, would I use L or j?

09:47 <naobsd> *.bin is not for rkflashtool.

09:47 <naobsd> sorry, I have to go out

13:52 <rperier> what does florian mean with "Please include a Fixes tag to help keep track of changes." ? I need to add something like "[BUG]" in the title of the patch ?

13:52 <rperier> hi all btw :)

14:11 <mmind00> rperier: Format is

14:11 <mmind00> Fixes: 12bytesOfId ("Original commit subject")

14:12 <mmind00> if you submit a patch fixing some previous commit

14:53 <rperier> mmind00: this part is for the "short commit message" and for the long commit message, you're supposed to explain your changes right ?

14:55 <mmind00> rperier: normally the fixes part sits directly above the Signed-off-by ... like http://pastebin.com/RRvwHppd

15:01 <rperier> ohh I see

15:02 <rperier> good to know :)

15:02 <rperier> thanks

15:08 <mmind00> glad to help ;-)

15:13 <rperier> :)