ChanServ changed the topic of #radxa to: http://radxa.com/ - Logs: http://irclog.whitequark.org/radxa
<dnr> naobsd: do you have the mali driver and fix for radxa, so I can use 3d acceleration on my rock pro?
FreezingCold has quit [Ping timeout: 245 seconds]
<dnr> Many thanks for the link naobsd, that's exactly what I was looking for.
hipboi_ has left #radxa ["Leaving"]
hipboi has joined #radxa
hipboi has quit [Remote host closed the connection]
hipboi has joined #radxa
hipboi has quit [Ping timeout: 245 seconds]
jcarlos has quit [Ping timeout: 250 seconds]
jcarlos has joined #radxa
hramrach has quit [Remote host closed the connection]
hramrach has joined #radxa
amx_ has joined #radxa
BorgCuba has joined #radxa
amx_ has quit [Client Quit]
<BorgCuba> what does 'RSAK' and 'QSAK' stand for (bootloader image)
<BorgCuba> ?
<naobsd> maybe for secure boot (not sure, just guessing)
<BorgCuba> maybe
<BorgCuba> well, in the u-boot.map file it says 'RSA_KEY_TAG'
<BorgCuba> but all the key data is zero, so I think it is not used
bengal has joined #radxa
bengal has joined #radxa
bengal has quit [Changing host]
<naobsd> well
<naobsd> here is #radxa
<naobsd> working u-boot is not available for radxa rock
<naobsd> well
<naobsd> secure boot may be able to use with RK bootloader
<naobsd> anyway, there is space, used or not used is not so important ;)
<BorgCuba> yeah, so I try to get u-boot working
<BorgCuba> so far building u-boot and booting it from sdcard does not work
<BorgCuba> but I could verify that my image building method works, so this must be an issue with u-boot code (from neo-tech git)
hramrach has quit [*.net *.split]
<PaowZ_> naobsd: working u-boot is not available ?? why is there a radxa u-boot, then ??
<PaowZ_> I've read a guy was able to boot a linux kernel by chaining Barebox with the genuine RR bootloader.. he said he wasn't "brave" enough to get rid of the original bootloader..
<PaowZ_> on radxa domain, there is a u-boot binary: http://dl.radxa.com/users/tom/ is this u-boot release not operational ?
Turl has quit [*.net *.split]
Turl has joined #radxa
FreezingCold has joined #radxa
irsol has quit [Ping timeout: 245 seconds]
irsol has joined #radxa
irsol has quit [Ping timeout: 250 seconds]
irsol has joined #radxa
hramrach has joined #radxa
c0d3z3r0 has left #radxa [#radxa]
PaowZ_ has quit [Ping timeout: 240 seconds]
paowz has joined #radxa
FreezingCold has quit [Ping timeout: 245 seconds]
FreezingCold has joined #radxa
bengal has quit [Ping timeout: 260 seconds]
<BorgCuba> seem like the pll code (rkclk_pll_clk_set_rate) in arch/arm/cpu/armv7/rk30xx is broken (at least for GPLL and CPLL)
<BorgCuba> when omitting the two lines in rkclk_set_pll (clock.c ) I can see a few messages: "U-Boot 2013.04-rc2-00002-g53fd40e-dirty" ...
<paowz> BorgCuba: you're currently working on u-boot for RR ?
<BorgCuba> well, I try
<paowz> BorgCuba: I'm getting interested into making u-boot functional on this board..
<paowz> Currently, I bricked my RR some days ago.. NAND short-cut trick to recover seems to be efficient as I entered the "maskmode" to download a proper image..
<paowz> btw, do you know where I can find a well-suited image for the RR Pro.. radxa website is a bit in late with such informations (..or I might not have seen the right link.. possible..)
<paowz> BorgCuba: other question, I guess you must be using upgrade_tool to proceed.. what LBA address do you supply when flashing binary ??
<paowz> I have the feeling if you mess with parameters (like flash partitions..) at 0x0, upgrade_tool won't work at all..
<BorgCuba> actually i am using a sdcard
<paowz> ok.. but you must flash u-boot on NAND, right ?
<BorgCuba> no, I am using a sdcard
<BorgCuba> btw, some progress: http://pastebin.com/79ZTzP3S
<BorgCuba> and I have a usb device: 2207:310b
FreezingCold has quit [Ping timeout: 245 seconds]
<paowz> BorgCuba: how do you tell the RR to look for bootloader on sdcard ?
<BorgCuba> I followed this one: http://androtab.info/radxa_rock/sdboot/
<BorgCuba> and I replaced the bootloader inside sdboot_rk3188.img with u-boot
<paowz> ok..
<BorgCuba> are you using linux?
<paowz> I'd like to know what NAND address do we have to flash u-boot.. but as far as I remember, NAND is driven by a proprietary binary module coded by Rockchip..
<paowz> BorgCuba: as a desktop or as target ??
<BorgCuba> yes, I think you are right
<BorgCuba> desktop
<paowz> well.. I'd say both, anyway..
<BorgCuba> because of the 'dd'
<paowz> yes ?
<paowz> dd => write data towards a peripheral
<BorgCuba> I mean I am not sure if this would work under windows
<paowz> that would be more tricky..
<BorgCuba> I think I will now try to replace fastboot with cdc_ether ans see if I can boot a kernel
<BorgCuba> ... tomorrow
<BorgCuba> bye
BorgCuba has quit [Quit: leaving]
FreezingCold has joined #radxa
dnr has quit [Ping timeout: 240 seconds]
<naobsd> BorgCuba: that is the current u-boot state on RK3188, it boots, and not useful except for further development :)
<naobsd> BorgCuba: if you used my sdboot_rk3188.img, probably you need(ed? it seems you already did something) to tweak size of 2nd image(FlashBoot, u-boot, etc)
<naobsd> paowz: images for Rock Pro are available, u-boot for RR is not available, it's written on wiki.
<naobsd> paowb: wiki -> radxa's wiki linked from radxa.com
<naobsd> where to flash bootloader on NAND is very clear, there is no way to specify address for bootloader, it's just written to proper area
<naobsd> upgrade_tool just work even if parameter at 0x0 is missing/broken/etc/etc
<naobsd> if you want to know something, don't assume "it must be..."
<naobsd> many(most?) information about rockchip is missing, we need to assume something at last, but we shouldn't assume w/o logical thinking
<naobsd> I'll replace my sdboot_rk3188.img with new header which supports larger bootloader image such as u-boot
<naobsd> probably I have few more free time from this month...
naobsd has quit [Quit: Page closed]
hramrach has quit [Ping timeout: 264 seconds]
hramrach has joined #radxa