zar has quit [Quit: No Ping reply in 180 seconds.]
zar has joined #u-boot
sng has quit [Remote host closed the connection]
goliath has joined #u-boot
matthias_bgg has quit [Read error: Connection reset by peer]
matthias_bgg has joined #u-boot
sng has joined #u-boot
jpanisbl has joined #u-boot
SlimeyX has quit [Ping timeout: 240 seconds]
SlimeyX has joined #u-boot
<marex>
Tartarus: no 2023.07.03 today ? :)
matthewcroughan- has joined #u-boot
jaganteki has quit [Quit: Client closed]
<matthewcroughan->
I'm just getting into device tree, and I'm wondering why there are dts files in the U-Boot sources that exactly perfectly match the ones in the Linux source tree, can anyone explain this matching?
<jpanisbl>
That should be the case for all device trees, in theory. :)
<matthewcroughan->
But why is it this way? What's with the duplication?
<jpanisbl>
Device trees '<board>.dts' must be copied rom linux, then eventually overlayed with '<board>-u-boot.dts' files (note 'u-boot' suffix).
<matthewcroughan->
If U-Boot boots with a minimal dts, then Linux provides a big dts, does the minimal dts get overriden by the big dts?
<matthewcroughan->
Is the Linux dts supposed to be a duplicate of the u-boot dts, but with additional information added?
<jpanisbl>
As far as I know, it's the contrary: u-boot dts is supposed to be a duplicate of linux dts, with additional information (that's why some overlaying '<board>-u-boot.dts' are used)
<matthewcroughan->
In my case, I'm trying to add WiFi to a board that I'm trying to get working with a distribution other than Armbian
<matthewcroughan->
uses the same wifi chip, the same bus layout (I'm pretty sure, but not 100% sure)
<matthewcroughan->
Having never written a device tree before, I'm left wondering where I'm supposed to contribute this change. Why should I put it in Linux if I could just add a few lines to the u-boot dts?
<matthewcroughan->
This is not something I've been able to figure out with available documentation.
vvn has quit [Ping timeout: 250 seconds]
vvn has joined #u-boot
<jpanisbl>
Do you need to upstream your change ?
vvn has quit [Ping timeout: 246 seconds]
Adrian___ has joined #u-boot
<marex>
matthewcroughan-: these ? arch/arm/boot/dts/allwinner/sun8i-t113s-mangopi-mq-r-t113.dts
<marex>
I dont know, might be a different board altogether
Adrian has quit [Ping timeout: 245 seconds]
mncheck has joined #u-boot
<matthewcroughan->
Yeah I think it is a different board
<matthewcroughan->
Mine is the mq-quad
<matthewcroughan->
<jpanisbl> "Do you need to upstream your..." <- If I manage to figure it out, I'm wondering where I would upstream it to.
<matthewcroughan->
Am I supposed to copy the dts from u-boot into Linux, and add the WiFI there? Or am I supposed to add the WiFi in U-Boot's tree? It seems confusing.
<marex>
matthewcroughan-: u-boot most likely loads a separate dtb for your board from storage and passes that to linux, so that one is the one you need to patch
mmu_man has joined #u-boot
<marex>
not the uboot dt
<matthewcroughan->
Linux does not have a device tree for this board at all.
<matthewcroughan->
So what do I do then?
<matthewcroughan->
That's why I'm asking, do I copy the device tree from U-Boot into Linux?
alpernebbi has quit [Read error: Connection reset by peer]
jaganteki has joined #u-boot
alpernebbi has joined #u-boot
alpernebbi has quit [Client Quit]
mmu_man has quit [Ping timeout: 240 seconds]
naoki has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
<matthewcroughan->
I've asked someone else, apparently this is in fact the procedure?
<matthewcroughan->
If Linux doesn't have a device tree, but U-Boot does. I'm supposed to copy-paste the device tree from U-Boot into Linux, except add my additions, then make a PR to Linux with this mostly copy-pasted dts.
<matthewcroughan->
This seems architecturally wrong and brittle. What happens if Linux/U-Boot DTS' differ slightly?
naoki has quit [Quit: naoki]
alpernebbi has joined #u-boot
mmu_man has joined #u-boot
<marex>
matthewcroughan-: upstream the DT into linux, then sync the DT back to uboot, that's the procedure
ladis has joined #u-boot
mmu_man has quit [Ping timeout: 245 seconds]
ikarso has joined #u-boot
sng has quit [Remote host closed the connection]
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 240 seconds]
torez has joined #u-boot
davlefou has quit [Ping timeout: 264 seconds]
<sjg1>
matthewcroughan-: The U-Boot additions should be in the Linux tree. If you have trouble with that, PLMK
<matthewcroughan->
What revision of the upstream Linux tree contains the DTS?
<matthewcroughan->
I've just made the wifi work by adding an override of mmc1
<sjg1>
matthewcroughan-: No sorry that is someone else
davlefou has joined #u-boot
vagrantc has joined #u-boot
goliath has quit [Quit: SIGSEGV]
Adrian___ has quit [Ping timeout: 245 seconds]
<matthewcroughan->
sjg1: GPIO seems not to work on the board with just the dts provided by uboot here, I get `Unknown error 517` from libgpiod, looking into it a bit more now
mckoan is now known as mckoan|away
monstr has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
sng has quit [Read error: Connection reset by peer]
ikarso has joined #u-boot
dormito has quit [Ping timeout: 245 seconds]
dormito has joined #u-boot
sng has joined #u-boot
sng has quit [Ping timeout: 245 seconds]
goliath has quit [Quit: SIGSEGV]
jclsn has quit [Ping timeout: 246 seconds]
mmu_man has joined #u-boot
vagrantc has quit [Quit: leaving]
sng has joined #u-boot
sng has quit [Ping timeout: 240 seconds]
sng has joined #u-boot
sng has quit [Ping timeout: 250 seconds]
ladis has quit [Quit: Leaving]
stipa_ has joined #u-boot
stipa has quit [Read error: Connection reset by peer]
stipa_ is now known as stipa
SlimeyX has quit [Remote host closed the connection]
<sjg1>
matthewcroughan-: Oh dear!
<sjg1>
matthewcroughan-: Could be something missing from dts, but possibly not related to U-Boot
<sjg1>
-EPROBE_DEFER perhaps means that the GPIO is in use by the kernel?
ikarso has quit [Quit: Connection closed for inactivity]
mmu_man has quit [Ping timeout: 240 seconds]
<sjg1>
Tartarus: Re the breaking change in buildman, would it be to terrible to change the meaning of -R? I don't particularly want to keep two flags around
paulbarker has quit [Quit: Connection closed for inactivity]
<matthewcroughan->
False alarm, GPIO works fine, trying to enable Bluetooth now but uart1 not defined completely in the generic h616 include
wooosaiiii has quit [Ping timeout: 245 seconds]
__ad has joined #u-boot
vfazio_ has joined #u-boot
mmind00_ has joined #u-boot
mwalle_ has joined #u-boot
LordKalma2 has joined #u-boot
Manouchehri____ has joined #u-boot
xypron_ has joined #u-boot
Rahix_ has joined #u-boot
<Tartarus>
sjg1: I wonder if anyone other than us uses that flag, what are you using it for. even?
prabhakar has quit [*.net *.split]
Manouchehri__ has quit [*.net *.split]
vfazio has quit [*.net *.split]
mmind00 has quit [*.net *.split]
Rahix has quit [*.net *.split]
xypron has quit [*.net *.split]
LordKalma has quit [*.net *.split]
flokli has quit [*.net *.split]
ad__ has quit [*.net *.split]
mwalle has quit [*.net *.split]
LordKalma2 is now known as LordKalma
flokli has joined #u-boot
jasonk_ has quit [Quit: Connection closed for inactivity]
aisha[m] has joined #u-boot
<aisha[m]>
hey all, while trying to build u-boot i'm getting an error saying atf-bl31 not found
<aisha[m]>
could anyone point to where I can get this?