rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
GuestNew has joined #u-boot
GuestNew has quit [Quit: Client closed]
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
mmu_man has quit [Ping timeout: 264 seconds]
<milkylainen>
marex: stm32mp157f-dk2. vanilla 5.19 explodes on poking pll2_r clk when using stm tf-a.
mmu_man has joined #u-boot
<marex>
milkylainen: sigh ... just sigh ...
Skiper has quit [Ping timeout: 268 seconds]
Skiper has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
camus has quit [Ping timeout: 255 seconds]
camus has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
akaWolf has quit [Ping timeout: 255 seconds]
akaWolf has joined #u-boot
prabhakarlad has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
vagrantc has joined #u-boot
rvalue has quit [Ping timeout: 268 seconds]
rvalue has joined #u-boot
Skiper has quit [Read error: Connection reset by peer]
Skiper has joined #u-boot
Skiper has quit [Read error: Connection reset by peer]
Skiper has joined #u-boot
Skiper has quit [Ping timeout: 244 seconds]
Skiper has joined #u-boot
<vagrantc>
any guesses on if u-boot generally would be safe to build with CFLAGS += -O2 -fstack-protector-strong -Wformat -Werror=format-security and CPPFLAGS += -D_FORTIFY_SOURCE=2 ...
<vagrantc>
i could disable the check, but figured it might be worth fixing them too :)
<vagrantc>
and what variables to stick those into ... building tools is one thing, but building the various parts of u-boot.img and SPL and TPL and whatnot ... i'm a bit cautious on
persmule has quit [Remote host closed the connection]
<apritzel__>
Tartarus: btw: go ahead with the smc91111 removal. I got it mostly converted, but am struggling to test it (either way), and it is disabled for the FVP model anyway now (in favour of virtio)
<Tartarus>
OK
<apritzel__>
the other user is integrator, which is not OF_CONTROL anyway, so it wouldn't work for that board anyway
<apritzel__>
should I manage to get it to work still, I will send a partial revert, or just re-add the driver (that deserves heavy cleanup in any case)
<hramrach>
kernel does support he fortify flags but that does not mean everything does
apritzel__ has quit [Ping timeout: 268 seconds]
<hramrach>
and at least for kernel they are not set by passing from the environment but by kconfig, anyway
<hramrach>
I think th reasonable thing to do is to figure out how to filter out this error about missing fortify flags
<hramrach>
there is no point in them unles u-boot implements handling the errors, and can be tested to work with the flags enbled
<vagrantc>
it doesn't FORCE anything, it's more a recommendation
<milkylainen>
Hmm. What would be the typical effect if an scmi call went awry inside secure world somewhere sp_min/tee? From the linux perspective? Execution freeze?
<milkylainen>
Single/multicore?
<milkylainen>
Dunno who would be able to answer such a question. :) I thought u-boot might be as good as any.
<marex>
milkylainen: define awry
<marex>
if it's catastrophic failure, it could look like a hang to Linux
<marex>
like if you do for (;;) in the SMC call, it would be stuck there forever
lucascastro has quit [Remote host closed the connection]
<milkylainen>
marex: I dunno. Typical fubars. ;;, segv (mmu?). etc.
<milkylainen>
Trying to figure out how to debug an stm32mp157f-dk2 which goes dead inside userspace without as much as a hint from the kernel.
<milkylainen>
Suspecting tf-a here. :P
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
<milkylainen>
The same userspace works just fine when I switch to vanilla tf-a.
mmu_man has quit [Ping timeout: 268 seconds]
mmu_man has joined #u-boot
<hramrach>
and you have the tf-a sauce?
<hramrach>
how does userspace even enter tf-a?
<marex>
hramrach: by doing smc call
<marex>
hramrach: that might have to be done via kernel though
<hramrach>
and then kernel can log it
<marex>
hramrach: like, you call something which uses RPM to enable clock, which does SMC into ATF ... and that's it
<broonie>
Userspace can't directly talk to TF-A , calls need to be issued from EL1/2.
* hramrach
wonders what has package management to do with clocks
<marex>
hramrach: for starters, to access storage you need clock ?
<hramrach>
well, I would asume you would need to access same storage way before to do anything, like starting whatever process calls rpm
<marex>
rpm = runtime PM
<marex>
different thing
<hramrach>
yes, that would explain touching clocks
<hramrach>
rpm can be also revolutions per minute. frpm would be a very scary unit
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
___nick___ has quit [Ping timeout: 268 seconds]
<hanetzer>
so, question. I have a device capable of emmc boot, but it requires that u-boot (or whatever the earliest boot firmware may be) be placed *exactly* at the start of the emmc, so I can't use a traditional mbr/gpt partitioning setup. How would I go about partitioning said emmc in a way u-boot can recognize it for suchstuff as fatls/extls/etc ?
Xeroine has quit [Ping timeout: 268 seconds]
<hanetzer>
in linux-land its no problem as I can give it blkdevparts= on the command line
<cambrian_invader>
I think there are two options here; first, you can write your bootloaders so it has a hole for the partition table
<cambrian_invader>
second, you can try booting off the emmc boot0/1 hardware partition, and partition user hardware partition as usual
sbach has quit [Read error: Connection reset by peer]
<hanetzer>
I'm not certain it'll take u-boot from the boot0/1 parts (I assume that's mmcblkNboot0/1 in linux-land?)
<cambrian_invader>
yeah
<cambrian_invader>
that's probably the ideal way if you can do it
<hanetzer>
so, like this code:mbr:gpt:more code:- ?
sbach has joined #u-boot
<hanetzer>
since the mbr is 512b - the actual mbr?
<cambrian_invader>
well, the mbr is only like 64 bytes or something
<hanetzer>
yeah, at the end of that 512b
<cambrian_invader>
and GPT allows you to offset the partition table from the header
<cambrian_invader>
although the tooling support for that is not great
<hanetzer>
are there any examples in u-boot of this 'spread out' way of doing it?
<hanetzer>
eg, the hole
<hanetzer>
atm I can't do too much that's dangerous since I'm waiting on some adapter pcbs to arrive (nonstandard pinout and pitch for the jtag header)
<cambrian_invader>
maybe for x86?
mmu_man has quit [Ping timeout: 268 seconds]
mmu_man has joined #u-boot
gsz has quit [Ping timeout: 268 seconds]
<hanetzer>
so, another question. similar socs from this manuf. allowed me to read/extract the on-chip bootrom from u-boot with simple stuff like md & tftp; this one, reading the address space it *should* be in returns all zeros. any idea of what's causing that/how one would get around it?
persmule has quit [Remote host closed the connection]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
persmule has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
GNUtoo has joined #u-boot
persmule has quit [Remote host closed the connection]