Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2021.10 is OUT / Merge Window is OPEN until 25 October 2021 / Release v2022.01 is scheduled for 10 January 2022 / http://www.denx.de/wiki/U-Boot / Channel archives at https://libera.irclog.whitequark.org/u-boot
zibolo_ has joined #u-boot
sdfgsdfgs has joined #u-boot
jwillikers has quit [Remote host closed the connection]
Guest79 has joined #u-boot
<Guest79> Is there any issue with running a 32-bit U-Boot on a 64-bit (ARMv8) machine to load a 64-bit kernel?
Guest79 has quit [Quit: Client closed]
GNUtoo has quit [Ping timeout: 276 seconds]
GNUtoo has joined #u-boot
rfs613 has joined #u-boot
dsimic has joined #u-boot
<dsimic> I'm working on preparing a patchset that would upstream a few U-Boot patches for the Pinebook Pro that the distributions use
<dsimic> one of the patches turns two status LEDs on very early, using board_early_init_f() in the board-specific code
<dsimic> i.e. in board/pine64/pinebook-pro-rk3399/pinebook-pro-rk3399.c
<dsimic> however, I'm also aware that using CONFIG_LED_STATUS is the preferred way to do that, but it would result in the status LEDs being turned on a bit later
<dsimic> which may confuse the Pinebook Pro users that the laptop isn't turned on after they press the power key, etc.
<dsimic> so, I'd like to check whether a patch for board/pine64/pinebook-pro-rk3399/pinebook-pro-rk3399.c that turns the status LEDs in a non-preferred way would be accepted upstream?
dsimic has quit [Ping timeout: 256 seconds]
agust has joined #u-boot
guillaume_g has joined #u-boot
dsimic has joined #u-boot
ladis has joined #u-boot
tre has joined #u-boot
frieder has joined #u-boot
chrfle has quit [Quit: ZNC - https://znc.in]
chrfle has joined #u-boot
sszy has joined #u-boot
tnovotny has joined #u-boot
dsimic has quit [Quit: Ping timeout (120 seconds)]
dsimic has joined #u-boot
mckoan|away is now known as mckoan
matthias_bgg has joined #u-boot
mmu_man has joined #u-boot
gsz has joined #u-boot
tnovotny has quit [Read error: Connection reset by peer]
tnovotny has joined #u-boot
rtjure has joined #u-boot
mckoan is now known as mckoan|away
akaWolf has joined #u-boot
jwillikers has joined #u-boot
<brujah> mrnuke: yes, sorry, i talk to myself ...
<brujah> i see that a lot of CONFIG_IS_ENABLED has appear in the code around fit support (like CONFIG_IS_ENABLED(FIT_PRINT)), but those config doesn't exist for TPL
torez has joined #u-boot
smartin has joined #u-boot
torez has quit [Ping timeout: 245 seconds]
torez has joined #u-boot
tre has quit [Remote host closed the connection]
<mrnuke> brujah: I don't think TPL is supposed to support FIT, the whole point of TPL being that you don't have enough room for SPL.
<mrnuke> brujah: those CONFIG_IS_ENABLED() in FIT code raise my blood pressure. I want to get rid of them someday
<jimpo> Guest79: I'm no expert, but I haven't gotten that to work
<jimpo> on ARMv8 aarch64 can only be run at higher privilege levels than aarch32
ladis has quit [Ping timeout: 265 seconds]
wyre has joined #u-boot
<brujah> mrnuke: I think that TPL should support FIT (as SPL)
<mrnuke> brujah: What would be the purpose of separating TPL and SPL then?
<brujah> I am not sure, but in my understanding, when the space of the first stage is too small, then you just build a spl with minimum (like ram init) and then jump on tpl, and then jump on tpl
<brujah> I am not sure, but in my understanding, when the space of the first stage is too small, then you just build a spl with minimum (like ram init) and then jump on tpl, and then jump on u-boot
<mrnuke> TPL (tiny) -> SPL (small) -> u-boot (bloat)
<brujah> in my understanding, TPL is launched after SPL
<brujah> SPL -> TPL -> u-boot
<mrnuke> brujah: TPL comes first. It's designed for cases where even SPL is too big
<brujah> slide 5 : Tiny SPL loads moderate-size middle layer called TPL
<brujah> slide 27 : If SPL is too big, TPL loads SPL
<mrnuke> brujah: I would trust the work of marex more
<brujah> mrnuke: i agree
<mrnuke> That means the statement "I If SPL is too big, TPL loads SPL" is more trust-worthy and likely the correct one
<brujah> the name missleads me
<brujah> third is usually after the second
<brujah> so, i won't fight to enable fit support in tpl
<mrnuke> One thing u-boot devs have never been accused of is knowing what the heck they are doing when naming things :)
<brujah> but in the past, spl and tpl were supporting fit
matthias_bgg has quit [Quit: Leaving]
guillaume_g has quit [Quit: Konversation terminated!]
<brujah> in fact, i think that the meaning of TPL has changed ...
<brujah> always trust the code :
[0x4A6F] has quit [Quit: Bridge terminating on SIGTERM]
jordemort has quit [Quit: Bridge terminating on SIGTERM]
cpackham[m] has quit [Quit: Bridge terminating on SIGTERM]
mvaittin has quit [Quit: Bridge terminating on SIGTERM]
LinuxHackerman has quit [Quit: Bridge terminating on SIGTERM]
samueldr has quit [Quit: Bridge terminating on SIGTERM]
kaji has quit [Quit: Bridge terminating on SIGTERM]
edrex[m] has quit [Quit: Bridge terminating on SIGTERM]
kallisti5[m] has quit [Quit: Bridge terminating on SIGTERM]
Dhruvagole[m] has quit [Quit: Bridge terminating on SIGTERM]
DhruvaG2000[m] has quit [Quit: Bridge terminating on SIGTERM]
bih420[m] has quit [Quit: Bridge terminating on SIGTERM]
cpackham[m] has joined #u-boot
redbrain has joined #u-boot
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
mvaittin has joined #u-boot
kallisti5[m] has joined #u-boot
samueldr has joined #u-boot
edrex[m] has joined #u-boot
DhruvaG2000[m] has joined #u-boot
kaji has joined #u-boot
jordemort has joined #u-boot
[0x4A6F] has joined #u-boot
LinuxHackerman has joined #u-boot
Dhruvagole[m] has joined #u-boot
bih420[m] has joined #u-boot
frieder has quit [Remote host closed the connection]
jwillikers has quit [Read error: Connection reset by peer]
jwillikers has joined #u-boot
sszy has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
tnovotny has quit [Quit: Leaving]
vagrantc has joined #u-boot
milkylainen_ has joined #u-boot
jwillikers has quit [Ping timeout: 245 seconds]
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #u-boot
tre has joined #u-boot
ladis has joined #u-boot
smartin has quit [Quit: smartin]
gsz has quit [Quit: leaving]
ladis has quit [Remote host closed the connection]
ladis has joined #u-boot
tre has quit [Remote host closed the connection]
vfazio_ has quit [Ping timeout: 252 seconds]
vfazio has joined #u-boot
redbrain has quit [Ping timeout: 265 seconds]
torez has quit [Remote host closed the connection]
agust has quit [Quit: Leaving.]
ladis has quit [Remote host closed the connection]
ladis has joined #u-boot
mckoan|away has quit [Ping timeout: 265 seconds]
kveremitz has joined #u-boot
vagrantc has quit [Quit: leaving]