khilman has quit [Read error: Connection reset by peer]
praneeth has quit [Read error: Connection reset by peer]
jamestperk has joined #linux-ti
praneeth has joined #linux-ti
khilman has joined #linux-ti
kishon has joined #linux-ti
ikarso has joined #linux-ti
rob_w has joined #linux-ti
rogerq has joined #linux-ti
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #linux-ti
rogerq has quit [*.net *.split]
rob_w has quit [*.net *.split]
troth has quit [*.net *.split]
tmlind has quit [*.net *.split]
tmlind has joined #linux-ti
troth has joined #linux-ti
rogerq has joined #linux-ti
rob_w has joined #linux-ti
rogerq has quit [Ping timeout: 252 seconds]
rogerq has joined #linux-ti
rogerq has quit [Ping timeout: 252 seconds]
rogerq has joined #linux-ti
florian has joined #linux-ti
ikarso has quit [Quit: Connection closed for inactivity]
rogerq_ has joined #linux-ti
rogerq has quit [Read error: Connection reset by peer]
florian has quit [Quit: Ex-Chat]
rogerq_ has quit [Ping timeout: 245 seconds]
florian has joined #linux-ti
HcE has joined #linux-ti
rob_w has quit [Remote host closed the connection]
amjad has joined #linux-ti
<amjad>
Regarding AM335X EVM , mainline u-boot, I'm trying to apply an overlay dtbo to support PRUSS mode. The overlay shouldn't be apply for CPSW mode. But since for mainline we use sysboot command with extlinux/extlinux.conf located in boot medium, the overlay should be declared in extlinux.conf with "FDTOVERLAYS ../am335x-icev2-prueth.dtbo", but there
<amjad>
isn't a clean way not load this overlay for CPSW mode. Therefore, I'm thinking of having two different extlinux.conf files, one with the overlay directive, the other without, and we choose the approriate file at run-time. Other solution is to have only one extlinux.conf file with the overlay directive, but we unset fdtoverlay_addr_r in u-boot env
<amjad>
for CPSW mode so that sysboot skips loading the overlay, this will show an ugly unharmful error message but the boot continues
<amjad>
What do you think of these two solutions ? is there any other mechanism you use to achieve the same end for mainline u-boot ?
amjad has quit [Ping timeout: 256 seconds]
amjad has joined #linux-ti
Pali has joined #linux-ti
rogerq has joined #linux-ti
amjad has quit [Quit: Client closed]
amjad has joined #linux-ti
Tartarus has joined #linux-ti
<khilman>
07:53 <amjad> Regarding AM335X EVM , mainline u-boot, I'm trying to apply an overlay dtbo to support PRUSS mode. The overlay shouldn't be apply for CPSW mode. But since for mainline we use sysboot command with extlinux/extlinux.conf located in boot medium, the overlay should be declared in extlinux.conf with "FDTOVERLAYS ../am335x-icev2-prueth.dtbo", but there
<khilman>
07:56 <amjad> What do you think of these two solutions ? is there any other mechanism you use to achieve the same end for mainline u-boot ?
<khilman>
07:53 <amjad> isn't a clean way not load this overlay for CPSW mode. Therefore, I'm thinking of having two different extlinux.conf files, one with the overlay directive, the other without, and we choose the approriate file at run-time. Other solution is to have only one extlinux.conf file with the overlay directive, but we unset fdtoverlay_addr_r in u-boot env
<khilman>
07:53 <amjad> for CPSW mode so that sysboot skips loading the overlay, this will show an ugly unharmful error message but the boot continues
<khilman>
Tartarus: repeating Amjad's question for you. ^^^
<Tartarus>
Overlays and generic distro boot do indeed make for fun times.
<Tartarus>
Now, extlinux.conf pops up a menu, so why not just 1 extlinux.conf with one entry for PRUSS and another for CPSW?
<amjad>
Wouldn't we need to prompt the user to choose between the two ? In our use-case, we we would like to automatically choose the right entry based on an env variable (that is set based on the physical jumper configuration on the board)
<Tartarus>
Yes, that would require user-intervention.
<Tartarus>
So, hm
rogerq has quit [Remote host closed the connection]
<Tartarus>
I assume you're trying to not change bootcmd ?
<amjad>
Well I think we can, our current bootcmd is: run findfdt; run init_console; run finduuid; run distro_bootcmd
<amjad>
we mainly rely on the generic distro_bootcmd
<amjad>
One thing that could make life easier is to add a new option to sysboot, to enable/disabled overlay application
<amjad>
at runtime
<Tartarus>
I'm not sure I like that
<Tartarus>
Since the regular way to handle this would be to just select the right entry
<Tartarus>
Well, lemme finish thinking out loud here :)
<Tartarus>
You're trying to go for non-interactive selection of the right boot
<Tartarus>
And there's not a way to change the default entry, it's always #1, yes?
<Tartarus>
Some code change such that sysboot/etc checks a variable to know what the default entry should be, would be useful and I don't think violate the spec
<Tartarus>
(but please check)
<Tartarus>
Then you could just set the env var as you need it, based on the jumper, to entry #1/#2, whichever is PRUSS/CPSW in your setup
<amjad>
This would be great actually, I'll double-check the sysboot code to make sure it can accomodate that change without breaking anything
<amjad>
Thanks :)
<Tartarus>
Welcome
<Tartarus>
Tag me here or #u-boot if you have any other problems, there's other folks in #u-boot too of course :)
amjad has quit [Quit: Client closed]
rogerq has joined #linux-ti
florian has quit [Ping timeout: 260 seconds]
florian has joined #linux-ti
rogerq has quit [Remote host closed the connection]
rogerq has joined #linux-ti
florian has quit [Ping timeout: 252 seconds]
rob_w has joined #linux-ti
amjad has joined #linux-ti
amjad has quit [Client Quit]
florian has joined #linux-ti
rogerq has quit [Remote host closed the connection]
florian has quit [Ping timeout: 260 seconds]
florian has joined #linux-ti
florian has quit [Ping timeout: 252 seconds]
rob_w has quit [Read error: Connection reset by peer]