persmule has quit [Remote host closed the connection]
clarity has quit [Ping timeout: 255 seconds]
clarity has joined #u-boot
clarity has quit [Ping timeout: 260 seconds]
clarity has joined #u-boot
mmu_man has joined #u-boot
slobodan has joined #u-boot
xroumegue has quit [Ping timeout: 250 seconds]
xroumegue has joined #u-boot
d-s-e has quit [Ping timeout: 255 seconds]
naoki has quit [Quit: naoki]
Guest4494 has joined #u-boot
ldevulder has joined #u-boot
d-s-e has joined #u-boot
monstr has joined #u-boot
d-s-e has quit [Ping timeout: 246 seconds]
<kabel>
I want to put a constant structure at a specific place in a binary via linker script. Normally I can just tell that a specific section should be at the address, for example:
<Tartarus>
apalos: You only need it when EFI is starting something not created by U-Boot. If there's some paths other than bootefi, OK, tweak it there too
<Tartarus>
kabel: I think the embedded env stuff (a) still works and (b) is examples of how to do that trick?
d-s-e has joined #u-boot
<apalos>
Tartarus: ok, i can try having a look, but that wont be too soon
<apalos>
But do we want to pull this in for 2023.04 (since it fixes CONFIG_LTO)?
<Tartarus>
No, it can wait, no one is doing LTO+EFI+armv7
<Tartarus>
Or it'd have been found before my "Hey, what if we LTO all of ARM?"
<sylensky[m]>
hello did someone tried to read/write a u-boot environment from/to fat filesystem on a usb drive? Or is generally only mmc supported as fat device?
<Tartarus>
Should work
<sylensky[m]>
atleast not on my device. could that be a image generation issue? for reference iam using a usb to sata adapter with an ssd
<Tartarus>
There could be a bug in many places
<Tartarus>
But it should be resolvable
<sylensky[m]>
i did some research already and it seems it fails upon fat cluster reading:
<sylensky[m]>
Unable to read "uboot-env.txt" from usb0:2...```
<Tartarus>
Yeah, without knowing the platform, I'd suspect an issue with USB support, or perhaps a quirk of that device, if you have some other device you can try, or some other platform you can try insted
<sylensky[m]>
ah sorry i forgot to mention its a rpi4 with the devicetree of the latest raspberry firmware tags
<marex>
what is the problem again ?
<marex>
ENV_IS_IN_FAT should work
<marex>
u-boot version ?
<marex>
logs ? pastebin please
Guest4494 has quit [Quit: Client closed]
<Tartarus>
sjg1_: Any chance you'll have time to look at clang 15 (or 16) and sandbox failures?
<marex>
hmmm, what is it with these links in each and every message ?
thopiekar has joined #u-boot
<marex>
its like the message gets trimmed to some prefix and then ... boot web browser and see link
<marex>
sylensky[m]: basically, try mainline u-boot, if it does work, then you might be missing a patch
<vagrantc>
marex: the combination of matrix quoting what is being replied to, helpfully truncating the message to a "reasonable" size, and posting a very helpful link to the rest of the content...
<marex>
vagrantc: so to read a text message, I need to boot what is basically an OS for each message :facepalm:
<marex>
I feel like I must be gettning too old, what has the world come to
<vagrantc>
and maybe editing a reponse, but since there is no way to edit in irc, it just reposts the updated message
<vagrantc>
maybe it is not that you are getting old, but other people are getting too young?
<vagrantc>
the short of it comes down to bridging between two protocols with vastly different capabilities is bound to be ugly from one direction or another
<marex>
yeah, I guess
guillaume_g has quit [Quit: Konversation terminated!]
vagrantc has quit [Quit: leaving]
ikarso has joined #u-boot
prabhakarlad has joined #u-boot
persmule has quit [Ping timeout: 255 seconds]
persmule has joined #u-boot
goliath has quit [Quit: SIGSEGV]
mmu_man has quit [Ping timeout: 248 seconds]
<sylensky[m]>
But thanks for the hint anyway.
<sylensky[m]>
<marex> "its like the message gets..." <- Iam not sure what you refer to but it seems to ne matrix client related. Maybe i shouldnt have put paragraph over paragraph in here.
<Tartarus>
Yeah, most of us are on the IRC side and the gateway cuts out after a bit