qschulz has quit [Read error: Connection reset by peer]
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
kevery has joined #linux-rockchip
qschulz has joined #linux-rockchip
stikonas has quit [Quit: Konversation terminated!]
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
System_Error has quit [Ping timeout: 260 seconds]
System_Error has joined #linux-rockchip
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
warpme has joined #linux-rockchip
Livio has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
Net147 has quit [Quit: Quit]
Net147 has joined #linux-rockchip
Net147 has quit [Changing host]
Net147 has joined #linux-rockchip
Livio has quit [Ping timeout: 260 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
raster has joined #linux-rockchip
warpme has joined #linux-rockchip
<Kwiboo>
qschulz: no, I do not have any chromebook bob or kevin, after looking a little bit more I think u-boot.elf can be chainloaded, or you can replace and run bare-metal SPL+U-Boot proper from SPI flash
<Kwiboo>
so for bare-metal case it could probably be replaced with TPL+SPL, but not sure it is worth trying to change that to TPL+SPL
naoki has quit [Quit: naoki]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 has quit [Ping timeout: 252 seconds]
erg has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
dsimic has quit [Ping timeout: 255 seconds]
dsimic has joined #linux-rockchip
psydroid has joined #linux-rockchip
FergusL has quit [Changing host]
FergusL has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
erg has quit [Read error: Connection reset by peer]
erg has joined #linux-rockchip
<qschulz>
Kwiboo: I'm trying out your patches on Puma RK3399 right now
<qschulz>
and SPL_FIT_SIGNATURE
<qschulz>
it still fits below 192KiB limit we ahave for TPL+SPL on that board
<qschulz>
but we're near it (180KiB)
<qschulz>
(gcc 13.2.1 on fedora 39)
<qschulz>
anyway, that's not why I'm pinging here, the boot time is worse by about 400-500ms
<qschulz>
most of it in board_init_r
erg has quit [Ping timeout: 252 seconds]
erg has joined #linux-rockchip
<sre>
macromorgan: when you send the patch(es), please add a 'Fixes: 11cb8da0189b ("power: supply: Add charger driver for Rockchip RK817")'
<Kwiboo>
qschulz: hum, I did notice a small increase in boot time, but I do not think it was that much when I tested, fdt_parent_offset() is one of the function that slows down boot time a lot
<qschulz>
Kwiboo: how do you keep track of the time increase?
<qschulz>
do you use bootstage as well?
<Kwiboo>
will shortly push a branch with some work-in-progress patches that should speed up boot times a lot, next series after
<qschulz>
Kwiboo: I always found Puma to be quite slow to boot up so I'm not **too** worried right now
<qschulz>
I brought this up because I remember you were really into making Rockchip devices boot faster
<qschulz>
and that seemed to go the wrong direction for that series :)
<qschulz>
I'll provide numbers soon
<Kwiboo>
yes, I have also used bootstage to measure time, at one time I think it took around 4s without bootdelay to get to cli on my rock pi 4, and after some optimization it was down to ~500-700ms from cold start
<Kwiboo>
video/display support without hdmi connected will cust 4x 300ms timeout
<qschulz>
Kwiboo: tbf, we're not helping ourselves as well, our boards have their baudrate set to 115200 :)
<Kwiboo>
qschulz: thanks, I think I noticed round 100-200ms extra time with rk3399 series if I remember correctly, will testa again on my rock-pi-4 later
<Kwiboo>
I tried to avoid as many fdt_parent_offset as possible, and change some DM use to get well known reg addresses, because resolving a known contant using syscon could take 50-100ms in pre-reloc stage
<Kwiboo>
and similar serial_init in pre-reloc will take around 200-300ms, some of that was just to get the 24mhz clock rate because it needed to resolve cru driver, changing to use freq from DT saved some boot time
<Kwiboo>
but all this needs to be measured and properly motivated in a future series :-)
<qschulz>
Kwiboo: yeah, some of those changes will be a hard sell ;)
Livio has joined #linux-rockchip
crabbedhaloablut has quit []
crabbedhaloablut has joined #linux-rockchip
wens has quit [Quit: leaving]
vagrantc has joined #linux-rockchip
wens has joined #linux-rockchip
erg has quit [Read error: Connection reset by peer]
erg has joined #linux-rockchip
erg has quit [Ping timeout: 255 seconds]
erg has joined #linux-rockchip
Livio has quit [Ping timeout: 272 seconds]
erg has quit [Ping timeout: 272 seconds]
erg has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
erg has quit [Ping timeout: 268 seconds]
stikonas has joined #linux-rockchip
ldevulder has quit [Quit: Leaving]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<diederik>
hmm ... can I put a working u-boot (back) on it via serial console?
<macromorgan>
no, honestly what would be useful is an output from the atags command on the BSP kernel... I heard 8GB boards were problematic I just didn't have one to test with
Livio has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
stikonas has quit [Remote host closed the connection]