ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
heat has quit [Remote host closed the connection]
heat has joined #armlinux
apritzel_ has quit [Ping timeout: 248 seconds]
heat has quit [Read error: Connection reset by peer]
heat has joined #armlinux
mraynal has quit [Quit: WeeChat 3.0]
mraynal has joined #armlinux
heat has quit [Read error: Connection reset by peer]
<wens>
tlwoerner: Allwinner RISC-V stuff is maintained by the same people (though I personally don't have any RISC-V stuff)
<Xogium>
argh allwinner... They really did things the weird way, once again
<Xogium>
u-boot spl -> opensbi -> u-boot -> linux. You can complicate matters even more by doing u-boot spl -> opensbi -> grub2 -> u-boot -> linux
jclsn_ has quit [Quit: WeeChat 3.8]
jclsn has joined #armlinux
frieder has joined #armlinux
cleger has joined #armlinux
heat has quit [Ping timeout: 248 seconds]
apritzel_ has joined #armlinux
apritzel_ has quit [Ping timeout: 248 seconds]
headless has joined #armlinux
mal``` has quit [Quit: Leaving]
mal`` has joined #armlinux
sszy has joined #armlinux
vm has joined #armlinux
apritzel has joined #armlinux
viorel_suman has joined #armlinux
frieder has quit [Remote host closed the connection]
xv8 has quit [Ping timeout: 260 seconds]
xv8 has joined #armlinux
frieder has joined #armlinux
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
headless has quit [Read error: Connection reset by peer]
cbeznea has joined #armlinux
torez has joined #armlinux
<robher>
maz: The GIC ITS binding says #msi-cells is required and must be 1 (going back to the .txt binding). Several platforms omit it, so it defaults to 0. Relax the schema or fix the dts files?
amitk_ has quit [Ping timeout: 248 seconds]
<robmur01>
probably fix the DTs - IIRC the 0-cells case means having to guess at what the DeviceIDs are
<robmur01>
(i.e. it just about works provided the only thing targeting the ITS is a single PCI segment, so is not generally applicable as a reasonable binding)