naobsd has quit [Remote host closed the connection]
<Elijah_>
sjoerd: radxa rock pro
<Elijah_>
Running off the SD card
<Elijah_>
Kernel 3.18 does seem to be working aside from the HDMI video
<Elijah_>
wanted to get the usbtv driver
<Elijah_>
it does seem to be recognizing my EasyCap now, will have to find an NTSC source to test it out
<Elijah_>
interestingly, the MAC address is still not what's passed on the kernel command line
Ueno_Otoko has joined #linux-rockchip
Ueno_Otoko has quit [Ping timeout: 240 seconds]
Ueno_Otoko has joined #linux-rockchip
kapouer has quit [Quit: kapouer]
azend|vps_ has joined #linux-rockchip
afaerber_ has quit [Ping timeout: 250 seconds]
afaerber_ has joined #linux-rockchip
azend|vps_ has quit [Read error: Connection reset by peer]
azend|vps_ has joined #linux-rockchip
azend|vps_ has quit [Ping timeout: 260 seconds]
azend|vps_ has joined #linux-rockchip
Sadneophyte has joined #linux-rockchip
Sadneophyte has quit [Ping timeout: 265 seconds]
cyrozap has joined #linux-rockchip
Ueno_Otoko has quit [Ping timeout: 265 seconds]
<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
<cyrozap>
boottools) which makes me think that I might be able to use U-boot, but it hasn't been updated in two years.
<cyrozap>
I just want that pure, Linux-y goodness on my tiny TV PC without all the Android cruft ;)
<naobsd>
then I think bootloader is not important part, proprietary loader is also good for that
<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?"
<naobsd>
do you have kernel source for your device?
<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?
<naobsd>
ah, well,
<naobsd>
you may need to modify kernel command line in parameter
<cyrozap>
What exactly is the "boot" partition? I'm familiar with a BIOS/UEFI boot flow, but ARM/Android stuff seems totally different...
<naobsd>
system partition may not so large
<naobsd>
it's almost Rockchip stuff than ARM/Android stuff
<naobsd>
boot partition is for initramfs(root fs on ram)
<cyrozap>
Ah, so is it just a raw initramfs image or is something tricky done to it?
<naobsd>
well
<cyrozap>
Because I know how to work with those
<naobsd>
with rockchip bootloader, you can put cpio(+gz) initramfs (with RK header) to boot partition, or
<naobsd>
you may put kernel+initramfs image on boot partition
<naobsd>
(you may put kernel+initramfs+resource(RK specific, dtb + logo package) image on boot if you are using rk3288 or later SoC)
<naobsd>
if you put ramdisk only image on boot partition, you also need to put kernel image on kernel partition
JohnDoe_71Rus has quit [Ping timeout: 245 seconds]
dlezcano has quit [Ping timeout: 240 seconds]
<naobsd>
for kernel/ramdisk separated image, you need to convert raw kernel binary/raw ramdisk image by mkkrnlimage command
JohnDoe_71Rus has joined #linux-rockchip
<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)
dlezcano has joined #linux-rockchip
<cyrozap>
Ok, I think that's enough to get me started. Thanks for your help!
<naobsd>
you can use rkflashtool to modify parameter and flash images
<cyrozap>
Yup, I already have both :)
<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.
<cyrozap>
I suppose that means mask-rom flashing hasn't been reversed yet?
<cyrozap>
(that is, flashing while booted from the mash ROM)
<cyrozap>
*mask
<naobsd>
yes and no
<naobsd>
protocol is known
sunilmohan has quit [Ping timeout: 265 seconds]
<naobsd>
data for NAND cannot be made yet, or just no one tried yet
<naobsd>
flashing loader on eMMC is known to work
<naobsd>
you can send loader with rkflashtool l/L with mask rom mode
<naobsd>
you can write IDB (which contains loader and some other data) with rkflashtool j
<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?
kapouer has joined #linux-rockchip
Ueno_Otoko has quit [Ping timeout: 276 seconds]
<naobsd>
*.bin is not for rkflashtool.
<naobsd>
sorry, I have to go out
naobsd has quit [Quit: naobsd]
VargaD has quit [Ping timeout: 250 seconds]
kapouer has quit [Quit: kapouer]
VargaD has joined #linux-rockchip
diego71_ is now known as diego71
cnxsoft has joined #linux-rockchip
c0d3z3r0 has quit [Ping timeout: 240 seconds]
ssvb_ has quit [Read error: Connection reset by peer]
ssvb_ has joined #linux-rockchip
ssvb_ has quit [Read error: Connection reset by peer]
ssvb_ has joined #linux-rockchip
Ueno_Otoko has joined #linux-rockchip
vickycq has quit [Quit: WeeChat 1.0.1]
vickycq has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
cnxsoft has joined #linux-rockchip
vickycq has quit [Ping timeout: 256 seconds]
vickycq has joined #linux-rockchip
naobsd has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
dlezcano has quit [Remote host closed the connection]
<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 ?