NishanthMenon changed the topic of #linux-ti to: Linux development for TI SoCs | Logs: https://libera.irclog.whitequark.org/linux-ti/| paste logs in https://pastebin.ubuntu.com/ | Let it rock! Vendor SDK/kernel: Also see e2e.ti.com
vstehle has quit [Ping timeout: 268 seconds]
vstehle has joined #linux-ti
rob_w has joined #linux-ti
florian has joined #linux-ti
Pali has joined #linux-ti
rob_w has quit [Quit: Leaving]
florian has quit [Read error: Connection reset by peer]
florian has joined #linux-ti
LokeshVutla has quit [Remote host closed the connection]
LokeshVutla has joined #linux-ti
florian has quit [Ping timeout: 268 seconds]
florian has joined #linux-ti
florian has quit [Ping timeout: 268 seconds]
praneeth has joined #linux-ti
florian has joined #linux-ti
<ecdhe> kristo: I just realized I've been testing the 5.10 device tree against the 4.19->5.13 kernels. I need to see if the am3517-evm device tree that shipped with v4.19 still causes the issue with kernel v4.19 for instance. Will get through these tests and see if there is any working reference among them!
<NishanthMenon> ecdhe, that would probably end up as a problem -> we migrated much of hardware description over the years to device tree with 5.14 being the final point in transition, each intermediate kernel has some level of split.. so you'd want to keep the dts and kernel revs in sync
<NishanthMenon> ecdhe, this basically has been the multi-year hwmod to devicetree conversion effort we've been doing..
florian has quit [Ping timeout: 268 seconds]
praneeth has quit [Quit: Client closed]
Pali has quit [Ping timeout: 265 seconds]