ikarso has quit [Quit: Connection closed for inactivity]
ldevulder_ has joined #u-boot
ldevulder has quit [Ping timeout: 264 seconds]
mmu_man has quit [Ping timeout: 256 seconds]
jclsn has quit [Ping timeout: 268 seconds]
jclsn has joined #u-boot
alpernebbi has quit [Ping timeout: 260 seconds]
alpernebbi has joined #u-boot
naoki has joined #u-boot
tgamblin has quit [Ping timeout: 252 seconds]
joeskb7 has quit [Quit: Lost terminal]
slobodan__ has joined #u-boot
mwalle has quit [Quit: WeeChat 3.8]
alperak has joined #u-boot
gsz has joined #u-boot
slobodan__ has quit [Ping timeout: 260 seconds]
<tlwoerner>
qschulz: with this new(-ish) rockchip u-boot feature of knowing the boot device, is there a way to know that device within u-boot?
<tlwoerner>
i.e. if i were writing a u-boot script and wanted to know the boot mmc device number, is there a way to know that dynamically? programmatically?
ladis has joined #u-boot
monstr has joined #u-boot
warpme has joined #u-boot
slobodan has joined #u-boot
slobodan_ has joined #u-boot
goliath has joined #u-boot
slobodan has quit [Ping timeout: 255 seconds]
Stat_headcrabed has joined #u-boot
enok has joined #u-boot
ikarso has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<__ad>
hi gm/gn, so trying to unmount rootfs on power downm in a own init i did, to have system clean. Tried remount ro, does not work. So, is the pivot_root() likely the way to do this ?
warpme has joined #u-boot
Leopold has quit [Remote host closed the connection]
jfsimon1981_b has quit [Ping timeout: 268 seconds]
jclsn has quit [Quit: WeeChat 4.2.2]
jclsn has joined #u-boot
frieder has joined #u-boot
ungeskriptet9 has joined #u-boot
ungeskriptet has quit [Ping timeout: 256 seconds]
ungeskriptet9 is now known as ungeskriptet
jfsimon1981 has joined #u-boot
jeeebz has quit [Quit: Ciao !]
jybz has joined #u-boot
mwalle has joined #u-boot
mripard has quit [Ping timeout: 268 seconds]
tnovotny has joined #u-boot
zibolo has joined #u-boot
<qschulz>
Kwiboo: dang it, I wanted to say SPL_MAX_SIZE and not SPL_PAD_TO, the latter has nothing to do with the SRAM size (well, except that we want it to be bigger than the size of the SRAM :) )
<qschulz>
sjg1: but what I pointed at seems to indicate tf-a needs 12+KB instead?
<qschulz>
tlwoerner: what exactly do you want to do with it? Also which device are we talking about? The one that was used to load TPL+SPL or the one that was used to load U-Boot proper?
mripard has joined #u-boot
sigmaris has quit [Ping timeout: 240 seconds]
ladis has quit [Remote host closed the connection]
ladis has joined #u-boot
enok has quit [Ping timeout: 260 seconds]
sigmaris has joined #u-boot
<__ad>
sry for my above msg, wrong paanel
mckoan|away is now known as mckoan
sigmaris_ has joined #u-boot
sigmaris has quit [Ping timeout: 256 seconds]
sigmaris_ is now known as sigmaris
ladis has quit [Remote host closed the connection]
ladis has joined #u-boot
sszy has joined #u-boot
Stat_headcrabed has quit [Quit: Connection closed for inactivity]
naoki has quit [Quit: naoki]
enok has joined #u-boot
ldevulder_ is now known as ldevulder
enok has quit [Ping timeout: 268 seconds]
ladis has quit [Quit: Leaving]
naoki has joined #u-boot
sszy has quit [Read error: Connection reset by peer]
naoki has quit [Quit: naoki]
sszy has joined #u-boot
mmu_man has joined #u-boot
dsimic has quit [Ping timeout: 268 seconds]
dsimic has joined #u-boot
naoki has joined #u-boot
enok has joined #u-boot
naoki has quit [Quit: naoki]
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #u-boot
jfsimon1981 is now known as jfsimon
tgamblin has joined #u-boot
rvalue has quit [Ping timeout: 240 seconds]
<tlwoerner>
qschulz: in a U-Boot script, i want to know from which mmc device to load the fitimage
<tlwoerner>
wouldn't the device that was used to load TPL+SPL be the same as the devie that was used to load U-Boot proper?
<tlwoerner>
if i have to choose, then i would guess U-Boot proper (?)
<tlwoerner>
on any given rockchip device the device that was used to load U-Boot proper could be either mmc0 or mmc1, is there a way to find out while in U-Boot (i.e. a script)
enok has quit [Ping timeout: 268 seconds]
enok has joined #u-boot
<marex>
tlwoerner: probably setenv some variable in board file or arch file to indicate which boot device was used
<marex>
tlwoerner: I think stm32 does something like that already, you might want to grep around what they are doing
Stat_headcrabed has joined #u-boot
slobodan__ has joined #u-boot
enok has quit [Ping timeout: 256 seconds]
<tlwoerner>
marex: right, i could hard-code which device based on which MACHINE, write the script with a variable place-holder, then run sed over it at build time to generate a working, board-specific U-Boot script
slobodan_ has quit [Ping timeout: 255 seconds]
<tlwoerner>
but that would require the user to tell me from which device they will be booting (SDcard or eMMC)
slobodan_ has joined #u-boot
<tlwoerner>
and that's prone to error and much less elegant than finding out the boot device and using that to load the fitimage
slobodan__ has quit [Ping timeout: 268 seconds]
<tlwoerner>
right now if i do an `env save` U-Boot knows to which device to save the environment, depending on whether i booted from the SDcard or the eMMC
<tlwoerner>
how do i find that out in a script (or on the cmdline)
<marex>
Tartarus: its on my list of things to review
<Tartarus>
OK, thanks, just wanted to make sure it didn't slip past you
ldevulder has quit [Quit: Leaving]
<quinq>
marex, regarding serial output, everything works now. I must confess at some point I stopped programming the new image and changes were not taken into acconut.
<sjg1>
Tartarus: no, it seems OK to me. It is quite hard sometimes to avoid multiple banners
<pivi>
marex: I poked a colleague about your imx8m binman signing patch. He had a look, he has some feedback. Let's see if he can write an email now ...
<Tartarus>
Yeah. I forget if i included in the patch that I got as far as "spl3" and then went no, this is getting too silly, and went to rework things
mmu_man has quit [Ping timeout: 272 seconds]
jfsimon has quit [Remote host closed the connection]
joeskb7 has joined #u-boot
jfsimon has joined #u-boot
MrCryo has quit [Remote host closed the connection]
enok has joined #u-boot
mmu_man has joined #u-boot
jfsimon has quit [Remote host closed the connection]
jfsimon has joined #u-boot
gsz has quit [Quit: leaving]
tgamblin has quit [Ping timeout: 255 seconds]
tgamblin has joined #u-boot
jfsimon has quit [Remote host closed the connection]
enok has quit [Ping timeout: 255 seconds]
jfsimon1981 has joined #u-boot
<pivi>
marex: maybe one important detail, the feedback is generally positive
mighty-bob has quit [Ping timeout: 264 seconds]
<marex>
quinq: oh well, oops
<marex>
quinq: good thing it works now
<marex>
pivi: woohoo
<quinq>
^^
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
___nick___ has quit [Ping timeout: 255 seconds]
slobodan__ has quit [Ping timeout: 255 seconds]
qqq has quit [Remote host closed the connection]
<tlwoerner>
qschulz: marex: there's a chicken-and-egg problem there
<tlwoerner>
in order to read the u-boot,spl-boot-order device tree node i have to load the fit image into memory to be able to run the `fdt` commands on it
<tlwoerner>
but in order to load the fit image into memory, i have to know the mmc device from which to load it
<tlwoerner>
if it doesn't already exist, in order to make this elegant we would need a way to know (in the U-Boot script environment) the boot device (e.g. mmc0? mmc1? ...)
<tlwoerner>
qschulz: or are you saying that the first value in ${boot_targets} is the one from which U-Boot proper was booted?
<tlwoerner>
(or is that only specific to theobroma devices?)
alperak has quit [Quit: Connection closed for inactivity]