<gb_master>
I mean, the instructions there are for the standard radxa rock (as far as I understood)... I'd just like to know if they work for the pro version as well
FreezingCold has quit [Remote host closed the connection]
<amstan>
woo! mainline kernel, i'm working on that right now
<amstan>
though... sd/mmc is probably going to run at low speeds
<gb_master>
hello amstan
<amstan>
hello
<gb_master>
my plan is to have everything on SD
<gb_master>
I mean, not touching the NAND
<gb_master>
do you have the pro version?
<amstan>
i don't own a radxa, i'm developing on the kernel for my board
<gb_master>
really experimental-ish :)
<amstan>
i had pretty good luck with upstream kernel, but there's still things to be done, even on our private chromeos kernel
<gb_master>
good
<amstan>
the mmc driver currently is missing tuning, so it's only running at 25% of the capable speed
<gb_master>
wow
<amstan>
that's one of the things missing
<gb_master>
the instructions are the same for the radxa?
<amstan>
i'm working on implementing that
<amstan>
what instructions?
<gb_master>
ok, I thought that your board and the radxa one were similar as they were using rk3188 (I'm presuming yours uses rk3188)
<amstan>
nope, 3288
<amstan>
but the mmc driver is common
<gb_master>
ah cool
<gb_master>
usb driver as well?
<amstan>
dwc? probably
FreezingCold has joined #radxa
<gb_master>
as I'm doing this because of an issue I have on plugging an external HD drive to the radxa rock
<gb_master>
it keeps on resetting the HDD drive time after time
<gb_master>
something like "reset high speed USB device number 4 using usb20_host" all over dmesg
<gb_master>
but I know that the HDD is working, as with the PC and rasp-pi it works
<gb_master>
so, I hoped that with a more recent kernel things could get better
<amstan>
gb_master: do other usb devices work?
<gb_master>
yes, I think so
<gb_master>
mrueg, the mkbootimg-rockchip ebuild should be updated in order to create the unmkbootimg binary and not the unpackbootimg
<mrueg>
gb_master: well i haven't played around with it for a while
<gb_master>
I just did :)
<gb_master>
FYI, I mean...
<mrueg>
gb_master: give me a sec, i'll fix it
<gb_master>
problem is that, as it is now, it doesn't install
<naobsd>
gb_master: mrueg: about unmkbootimg/unpackbootimg, I think most people only know about unpackbootimg, unmkbootimg is not common
<Astralix>
gb_master: one thing at a time.
<gb_master>
yes, but the problem is that the ebuild was not installing anymore
<naobsd>
amstan: I saw DRM patches for RK3288, but it doesn't contain any RK3188 support
<amstan>
ah yes
<amstan>
you're right
<amstan>
rk3288 only
<Astralix>
Download a simple image like the server image for SD and install that on your sd card.
<naobsd>
gb_master: basic instruction is same, but I think that page is outdated a little
<Astralix>
Check if it boots and then try to exchange only the kernel
<gb_master>
Astralix: I already have gentoo running by overwriting the rootfs of the ubuntu image
<Astralix>
hi naobsd
<naobsd>
gb_master: is there any reason not to follow discussion on google groups at first?
<gb_master>
I was following that... I just wanted to know if it worked with the radxa pro
<gb_master>
apparently it will
<naobsd>
gb_master: there is working image. linux-next is changed frequently, it may not work at some point
<naobsd>
gb_master: I don't have pro, you have pro, there is image, you can confirm it very easily.
<gb_master>
I used the snapshot pointed out in the google group thread
<Astralix>
gb_master: Does it work, or do you still have a problem?
<gb_master>
I'm trying it right now
<naobsd>
gb_master: you may try u-boot binary on my site. DO NOT texts are just for nooobs
<gb_master>
I might, yes
<gb_master>
what do I need to do to use u-boot?
<naobsd>
but both RK proprietary loader/u-boot can boot mainline kernel,
<Astralix>
gb_master: about initramfs, there was some reason it was used that came from (l)ubuntu. And you need it if you boot from NAND to early install rknand_ko.ko
<gb_master>
I don't know, what do you advice? uboot or prop loader?
<gb_master>
I'd like to have both kernel.img and boot.img on the SD, without touching the NAND
<Astralix>
for that you don't need uboot
<gb_master>
uboot offers some advantages?
<Astralix>
if you like to boot kernel from tftp / bootp, you need uboot
<Astralix>
naobsd, does that work?
<gb_master>
mmm I don't need that
<naobsd>
gb_master: no advantage, basically. but I added some hacks, it might be useful
<mrueg>
can uboot boot grub?
<naobsd>
mrueg: any loader can boot any ARM binary
Bludot has joined #radxa
<gb_master>
ok, so let's try with uboot
<gb_master>
rk3188 sdcard, I'd say, isn't it?
<mrueg>
naobsd: so in theory I could just load grub as my second stage bootloader?
<naobsd>
mrueg: if grub is available, I don't know about it
<naobsd>
gb_master: "outdated" on my sdboot page may be wrong description, sorry. it works. I just want to update that page ;)
<gb_master>
ok, no problem
<gb_master>
so, you'd say that uboot might be a wise choice
<naobsd>
Astralix: u-boot is not only for RK3188, RK3288 uses u-boot too. and RK doesn't maintain u-boot for RK3188 anymore, u-boot for RK3288 is still maintained
<Astralix>
Are you sure?... wait a second, I need to check my emails...
<naobsd>
Astralix: and u-boot for RK3188 community ver. ;) is not only for eMMC
<Astralix>
I talked about the officially supported
<Astralix>
But that is, what it makes so difficult... In and out...
<naobsd>
I heard from hipboi about u-boot for RK3188
<Astralix>
first uboot was for a special prject and for rk3188
<Astralix>
then it was discontinued and only 3288 was supplied with uboot.
<naobsd>
at least u-boot for RK3188 is based on old u-boot. u-boot for RK3288 is relatively new code base (like 2014.04 vs 2014.07, I forgot exact ver. for now)
<Astralix>
then they shipped dev boards with coreboot
<naobsd>
I know some rk3288 board uses different loader, but all consumer product uses u-boot
<Astralix>
As I was informed, coreboot is targeting a different OS
<Astralix>
Whereas uboot may be the next generation loader for RK3288 based androids
<gb_master>
I need to modify the parameters in the uboot zip?
<naobsd>
Astralix: u-boot for RK doesn't support network, tftp/bootp doesn't work
<Astralix>
So there is no further interest for gb_master to try that thing :)
<naobsd>
Astralix: probably ChromeOS for RK uses coreboot
<gb_master>
ah
<Astralix>
ah, right, this one might too, but uboot can boot chrome too
<naobsd>
gb_master: just try as is at first
<gb_master>
ok
<gb_master>
so, I need to modify the parameters in the zip?
<gb_master>
(I don't know how uboot works, but there's nothing in the parameters saying where the rootfs is)
<naobsd>
well
<naobsd>
yes
<naobsd>
try files from radxa_boot_bits.7z
<naobsd>
ah wait
<naobsd>
you're trying sd boot with u-boot, right? then any paramater should work
<gb_master>
well, I haven't done anything yet
<naobsd>
if you want to do boot from NAND with u-boot, parameter must have "uboot" partition and uboot.img need to be flashed to "uboot" partition
<naobsd>
rest of things are free
<gb_master>
I just want to boot from SD when the SD is in
<naobsd>
parameter in my sdboot/u-boot zip is minimal example
<naobsd>
you may try sd boot at first, then mainline next
<naobsd>
then you may try files in my sdboot/u-boot zip
<naobsd>
my zip is just for "boot from SD", not for "boot whole some system from SD". it only contain minimal files
<gb_master>
ok
<Astralix>
naobsd, where do you have this uboot? Is in your github repos?
<gb_master>
so, I'd try sdboot miniroot at first?
<naobsd>
not for != restricted. you can add any thing you want
<naobsd>
Astralix: yes, I wrote about source on my page
<gb_master>
btw, when I dd sdboot_rk3188.img I think it overwrites my partition table
<naobsd>
gb_master: if you like step-by-step, yes
<naobsd>
gb_master: you can edit/restore partition table
<naobsd>
gb_master: or you can avoid MBR overwrite by "skip=1 seek=1"
<Astralix>
There are far to many pages written about RKxxxx
<naobsd>
well? I think we're talking about my sdboot/u-boot pages
<naobsd>
gb_master: that is one of "outdated/I want to update" part on my page...
<gb_master>
hehe
<naobsd>
README in u-boot zip doesn't overwrite MBR
<naobsd>
but
<naobsd>
then some people will complain "when I put files on SD card partition, sd boot is broken, why???"
<naobsd>
so, in general, no good point for most people ;)
<gb_master>
yep, probably
<Astralix>
I put myself to standby now... have to get up early
<naobsd>
Astralix: good night
<gb_master>
good night
<gb_master>
and thanks again
<Astralix>
welcomed. Anytime again
<naobsd>
many people say "open source is better", but most of them don't touch source code when it's available ;)
<gb_master>
true
<gb_master>
and I'm probably one of them
<naobsd>
but one more difference: there is source code
<naobsd>
we can fix/add something
<naobsd>
if we can.
<gb_master>
it'll be my next step
<gb_master>
for the moment I just need to get rid of all the "reset high speed USB device number 4 using usb20_host" messages in my dmesg when I plug my external HDD
<gb_master>
hopefully, with a newer kernel I will be OK
<naobsd>
currently no USB device support, no network support, no standard mmc driver, no file system support, etc etc
<naobsd>
gb_master: are you using self-power HDD?
<gb_master>
it uses an external power
<naobsd>
hm
<gb_master>
and I'm sure the HDD is fine, as it works with my PC and with the rasp-pi
<naobsd>
mrueg: is there rkflashtool package(portage? I forgot name)
<mrueg>
naobsd: yes it is
<mrueg>
but only version 5.1
<mrueg>
sys-apps/rkflashtool
<naobsd>
gb_master: supplied power from USB port may be different, but no problem with external power
<gb_master>
I know
<gb_master>
that's why I wanted to try with a newer kernel
<gb_master>
I mean, in order to temporarily work this thing around, I have to use a r-pi as NFS server