Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2023.10 is OUT / Merge Window is OPEN, next branch is CLOSED / Release v2024.01 is scheduled for 08 January 2024 / Channel archives at https://libera.irclog.whitequark.org/u-boot
bulverismo has joined #u-boot
bulverismo has quit [Quit: WeeChat 3.8]
mmu_man has quit [Ping timeout: 264 seconds]
mmu_man has joined #u-boot
sakman has joined #u-boot
alpernebbi has quit []
alpernebbi has joined #u-boot
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #u-boot
mmu_man has quit [Ping timeout: 255 seconds]
srk has quit [Remote host closed the connection]
srk has joined #u-boot
xroumegue has quit [Ping timeout: 252 seconds]
xroumegue has joined #u-boot
ikarso has joined #u-boot
wooosaiiii1 has joined #u-boot
wooosaiiii has quit [Ping timeout: 248 seconds]
wooosaiiii1 is now known as wooosaiiii
Stalevar has joined #u-boot
<Stalevar> Is u-boot useful on a regular x86 PC?
<Stalevar> can it be used as grub2 replacement?
monstr has joined #u-boot
sakman has quit [Quit: Leaving]
sakman has joined #u-boot
mckoan|away is now known as mckoan
goliath has joined #u-boot
sszy has joined #u-boot
deathmist has quit [Ping timeout: 272 seconds]
deathmist has joined #u-boot
ldevulder has joined #u-boot
deathmist has quit [Ping timeout: 240 seconds]
deathmist has joined #u-boot
mwalle has joined #u-boot
frieder has joined #u-boot
<mckoan> Stalevar: it's a bit tricky and probably not a good idea
<Stalevar> mckoan, this is booting it on bare metal, I was talking about the case of using proprietary BIOS or UEFI to boot u-boot and then load the kernel
<xypron> Stalevar: There is a small number of boards supported natively by U-Boot. Just run grep -GHrn CONFIG_X86=y configs/.
<Stalevar> So it won't work on generic x86 + BIOS, unlike grub or lilo?
mripard has joined #u-boot
ezulian has joined #u-boot
matthias_bgg has joined #u-boot
ungeskriptet has joined #u-boot
prabhakarlad has joined #u-boot
<marex> Stalevar: you can build u-boot as EFI binary iirc , then it should run on x86 PC with EFI
<marex> xypron: isnt that right ?
<Stalevar> what about i368-bios?
<marex> thats long irrelevant
monstr has quit [Ping timeout: 260 seconds]
f_ has joined #u-boot
f_ has quit [Ping timeout: 255 seconds]
naoki has quit [Quit: naoki]
monstr has joined #u-boot
dsimic has quit [Ping timeout: 272 seconds]
gsz has quit [Quit: leaving]
dsimic has joined #u-boot
persmule has quit [Ping timeout: 252 seconds]
ldevulder has quit [Quit: Leaving]
ldevulder has joined #u-boot
persmule has joined #u-boot
thopiekar has quit [Ping timeout: 246 seconds]
thopiekar has joined #u-boot
deathcamel57 has joined #u-boot
Stat_headcrabed has joined #u-boot
Stat_headcrabed has quit [Client Quit]
thopiekar has quit [Ping timeout: 260 seconds]
thopiekar_ has joined #u-boot
mmu_man has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
Stat_headcrabed has joined #u-boot
Stat_headcrabed has quit [Client Quit]
frieder has quit [Ping timeout: 255 seconds]
frieder has joined #u-boot
goliath has quit [Quit: SIGSEGV]
mmu_man has quit [Ping timeout: 245 seconds]
apteryx has joined #u-boot
<apteryx> hello! does someone use patman with gerrit? the default Gerrit commit-hook doesn't get along well with patman's usage of git trailers
<apteryx> I think because patman actually abuses git trailers, e.g. the Series-changes: n\- some entry\n- another one format
<silurian_invader> why do you want to use patman with gerrit?
<apteryx> I'm experimenting with adding Change-Id: trailers as done by the Gerrit commit hook, for adding traceability to commits posted to a mailing list
<apteryx> I don't actually use Gerrit
<apteryx> just their commit-msg hook
<apteryx> Guix uses Debbugs to track patch submissions (one series per "issue"). The availaibility of a unique Change-Id in each commit would make it possible to automatically close fully merged series
<Tartarus> patchwork and their patch-hashing mechanism has been Good Enough most of the time
<apteryx> I don't think Debbugs does that unfortunately; Change-Id would be tracker-agnostic
<apteryx> would be autoconfigured by the build system, meaning users would have these added without thinking about it
<apteryx> see https://issues.guix.gnu.org/66027 for the Gerrit commit-msg integration details in Guix
f_ has joined #u-boot
<marex> gerrit ... shudder
<xypron> marex: if you already have an EFI firmware there is no real need for U-Boot. But it is usable if you want to boot Linux via the legacy entry point.
<marex> xypron: what about if you want a proper shell ?
mmu_man has joined #u-boot
frieder has quit [Quit: Leaving]
<xypron> marex: use the EFI shell.
<f_> Have U-Boot be on SPI flash :D
<xypron> The EFI shell is packaged in Ubuntu 23.10
<f_> Or have coreboot and U-Boot as a coreboot payload :D
ikarso has joined #u-boot
<marex> xypron: which part of "proper" is not clear ? :)
<marex> xypron: U-Boot is packaged with debian for like a decade ...
qqq has quit [Remote host closed the connection]
mckoan is now known as mckoan|away
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
jclsn has quit [Quit: WeeChat 4.0.5]
jclsn has joined #u-boot
monstr has quit [Remote host closed the connection]
sszy has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
f_ has quit [Ping timeout: 240 seconds]
Leopold has quit [Remote host closed the connection]
Leopold has joined #u-boot
jclsn has quit [Quit: WeeChat 4.0.5]
Gravis has quit [Ping timeout: 246 seconds]
prabhakarlad has quit [Quit: Client closed]
Gravis has joined #u-boot
jclsn has joined #u-boot
Gravis_ has joined #u-boot
Gravis has quit [Ping timeout: 272 seconds]
MWelchUK has quit [Quit: The Lounge - https://thelounge.chat]
BobBeck3 has quit [Quit: The Lounge - https://thelounge.chat]
BobBeck3 has joined #u-boot
BobBeck3 has quit [Client Quit]
BobBeck3 has joined #u-boot
MWelchUK has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
goliath has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
goliath has quit [Quit: SIGSEGV]
<lvrp16> https://github.com/u-boot/u-boot/blob/master/cmd/sf.c#L138 this call can fail and the return of the function will still be 0, had "sf probe" fail but succeed in a script, do I submit a patch to just check the return and bail?
<marex> yeah
<marex> (and maybe write a test ...)
deathmist has quit [Ping timeout: 252 seconds]
deathmist has joined #u-boot
mckoan|away has quit [Ping timeout: 255 seconds]
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
mckoan|away has joined #u-boot