03:06 <set_> Is there no RT kernel for Buster 4.19.x?

03:10 <set_> Excuse me, I am barfing here.

03:10 <set_> Why would there be no RT Kernel for Buster 4.19.x?

03:12 <set_> Not enough room? Too much new stuff? Spring cleaning?

03:19 <set_> No reason to answer. I will some other route.

03:24 <set_> try, sorry. I will try some other route.

20:54 <set_> Hey guys. Warm. The BBBlue just might take me. I was close to understanding and then flailing happened. It is like a glimpse into things... Warm.

20:55 <set_> Anyway, I saw the new blog post on Twitter. Aw! That is how I feel but that is what I get.

20:56 <set_> Trying to control flight. It is not for me. I am withered and that darn flail of a forgotten memory...Anyway.

20:56 <set_> How are you?

21:04 <set_> Has it been six years or seven? Who is counting? Anyway, off to break. I need a win. NO more losing. I will win!

23:15 <KP19> I've been working writing my own overlays and I have come across an oddity in the am33xx.dtsi file in the definition of the uarts. For example, for uart2: serial@48024000 { ti,hwmods = "uart3"; }; Notice the hwmod string is not correct. It is like this for all of the uart definitions. Anyone else notice this? And does it matter?

23:18 <KP19> On a different note, if my employer allows it, where can I contribute my overlays to the community? I have developed a fairly complete set of overlays for the PocketBeagle.

23:48 <zmatt> KevinP: yeah there's some annoying off-by-ones in the DT here and there between numberings of peripherals in different places

23:50 <zmatt> KevinP: a more egregious one is that the mmc0 device has label &mmc1 and hwmods="mmc1"

23:51 <KevinP> I hadn't caught that one. Might explain an issue we have been having on one of our projects.

23:51 <KevinP> zmatt; I hadn't caught that one. Might explain an issue we have been having on one of our projects.

23:52 <zmatt> typically the origin of this is that TI uses 1-based peripheral numbering for some SoCs (notably the OMAPs and their descendents) while the linux kernel obviously uses 0-based numbering.... on the am335x however it's a bit more puzzling to me since TI used 0-based numbering for its peripherals in the first place so I don't really understand where the 1-based stuff came from

23:53 <zmatt> some of it has been fixed in the early days (e.g. uart0 used to have label &uart1 in kernel 3.8 iirc) but for some reason the mmc labels haven't been

23:54 <KevinP> running 4.19, so the uarts are still not fixed.

23:56 <zmatt> ??

23:56 <zmatt> the uart labels &uart0 etc have been fixed for a very long time

23:57 <zmatt> the hwmods are still off-by-one but that doesn't really affect anyone since that's internal to am33xx.dtsi

23:57 <zmatt> (and hwmods is gone entirely in 5.x anyway)

23:57 <KevinP> I see what you mean. it the hwmods that are off.

23:57 <KevinP> it is ...

23:59 <KevinP> good to know they are gone in 5.x