<paulbarker>
Also, should we drop files from arch/arm/dts which are no longer used to avoid confusion?
<LeSpocky>
IIRC it's dependening on CONFIG_OF_UPSTREAM
<LeSpocky>
that means upstream dts is only used for some boards, not for all
<paulbarker>
LeSpocky: I mean drop files from arch/arm/dts for boards which are using dts/upstream (with CONFIG_OF_UPSTREAM=y)
<frieder>
paulbarker: if the patches are in Linus' tree but not yet in U-Boots dts/upstream, you should probably wait for the next sync.
<frieder>
paulbarker: Or apply the changes in the *-u-boot.dts as temporary workaround.
<frieder>
paulbarker: And if any files in arch/arm/dts are unused they probably should be dropped. At least I've seen patches on the list doing just that.
mmu_man has quit [Ping timeout: 252 seconds]
guest57 has quit [Ping timeout: 256 seconds]
<paulbarker>
frieder: I was hoping to get changes in before the end of the merge window, I may have to wait until after the 2024.01 release for the next dts/upstream sync
<Kwiboo>
paulbarker: look like those commits are part of a tag in the devicetree-rebasing tree so you can use: tools/update-subtree.sh pick dts <commit-id> to cherry-pick those commits
<paulbarker>
Kwiboo: I've already done that locally for testing. My question is about getting changes in to u-boot
<Kwiboo>
send them as regular u-boot patches, that is what I have done for getting new boards in before next sync
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 265 seconds]
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 255 seconds]
mmu_man has joined #u-boot
abws has quit [Quit: abws]
abws has joined #u-boot
abws has quit [Ping timeout: 265 seconds]
<calebccff>
paulbarker: you could probably add a u-boot overlay dtsi, especially if it's for a patch already pending on the Linux side. See e.g. arch/arm/dts/qcs6490-rb3gen2-u-boot.dtsi for example. u-boot includes it automatically based on the filename
alan_o has quit [Remote host closed the connection]
alan_o has joined #u-boot
devarsh has joined #u-boot
Guest46 has joined #u-boot
Guest98 has joined #u-boot
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Stat_headcrabbed has joined #u-boot
qqe has quit [Quit: leaving]
qqe has joined #u-boot
mckoan is now known as mckoan|away
<paulbarker>
marex: the dts changes are in Linux already, I was just unclear on how to bring them over to u-boot now that we're using the dts/upstream tree. I understand now though, so will send the patches once I'm done with testing and internal review
persmule has quit [Remote host closed the connection]
Guest46 has quit [Quit: Client closed]
Clamor has joined #u-boot
Peng_Fan has quit [Quit: Connection closed for inactivity]
fatal has quit [Remote host closed the connection]
fatal has joined #u-boot
Clamor has quit [Quit: Quit]
monstr has quit [Remote host closed the connection]
joeskb7 has quit [Quit: Lost terminal]
joeskb7 has joined #u-boot
rockosov has joined #u-boot
qqe has quit [Ping timeout: 252 seconds]
qqe has joined #u-boot
naoki has quit [Quit: naoki]
<xypron>
Tartarus: Concerning doc/board/: It seems we have some chapters for SoC vendors like Allwinner and Sophgo. And we have some chapters for board vendors like BeagleBoard.org. Do we want that? Especially considering that most index.rst files have no content but the TOC.
<Tartarus>
Well, I think toradex might be a good example of the hard case to consider
<Tartarus>
They make SoMs/carrier for multiple vendors worth of SoCs
<Tartarus>
And being able to organize their content, with a starting point of "user will know they have a Toradex ..." and look there, rather than SoC directory being I think the likely case
<Tartarus>
After that then yes, how should cross-references work?
<Tartarus>
Do we just re-organize the index.rst files that are more than a ToC too, to have build instructions split out a bit more?
<Tartarus>
I am open to ideas
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]