**** BEGIN LOGGING AT Tue Jan 03 02:59:57 2023
Jan 03 03:06:00 <set_> Is there no RT kernel for Buster 4.19.x?
Jan 03 03:10:12 <set_> Excuse me, I am barfing here.
Jan 03 03:10:41 <set_> Why would there be no RT Kernel for Buster 4.19.x?
Jan 03 03:12:41 <set_> Not enough room? Too much new stuff? Spring cleaning?
Jan 03 03:19:46 <set_> No reason to answer. I will some other route.
Jan 03 03:24:25 <set_> try, sorry. I will try some other route.
Jan 03 20:54:58 <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.
Jan 03 20:55:31 <set_> Anyway, I saw the new blog post on Twitter. Aw! That is how I feel but that is what I get.
Jan 03 20:56:56 <set_> Trying to control flight. It is not for me. I am withered and that darn flail of a forgotten memory...Anyway.
Jan 03 20:56:58 <set_> How are you?
Jan 03 21:04:46 <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!
Jan 03 23:15:18 <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?
Jan 03 23:18:50 <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.
Jan 03 23:48:07 <zmatt> KevinP: yeah there's some annoying off-by-ones in the DT here and there between numberings of peripherals in different places
Jan 03 23:50:13 <zmatt> KevinP: a more egregious one is that the mmc0 device has label &mmc1 and hwmods="mmc1"
Jan 03 23:51:16 <KevinP> I hadn't caught that one. Might explain an issue we have been having on one of our projects.
Jan 03 23:51:32 <KevinP> zmatt; I hadn't caught that one. Might explain an issue we have been having on one of our projects.
Jan 03 23:52:18 <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
Jan 03 23:53:28 <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
Jan 03 23:54:21 <KevinP> running 4.19, so the uarts are still not fixed.
Jan 03 23:56:20 <zmatt> ??
Jan 03 23:56:34 <zmatt> the uart labels &uart0 etc have been fixed for a very long time
Jan 03 23:56:59 <zmatt> the hwmods are still off-by-one but that doesn't really affect anyone since that's internal to am33xx.dtsi
Jan 03 23:57:25 <zmatt> (and hwmods is gone entirely in 5.x anyway)
Jan 03 23:57:42 <KevinP> I see what you mean. it the hwmods that are off.
Jan 03 23:57:50 <KevinP> it is ...
Jan 03 23:59:14 <KevinP> good to know they are gone in 5.x
Jan 04 00:00:04 <KevinP> zmatt, thank you for the information.
Jan 04 00:15:53 <KevinP> zmatt: is this what you where referring to:
Jan 04 00:15:53 <KevinP> &mmc1 {
Jan 04 00:15:54 <KevinP>         status = "okay";
Jan 04 00:15:54 <KevinP>         vmmc-supply = <&vmmcsd_fixed>;
Jan 04 00:15:55 <KevinP>         bus-width = <4>;
Jan 04 00:15:55 <KevinP>         pinctrl-names = "default";
Jan 04 00:15:56 <KevinP>         pinctrl-0 = <&mmc0_pins>;
Jan 04 00:15:56 <KevinP>         cd-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
Jan 04 00:15:57 <KevinP> };
Jan 04 01:21:07 <zmatt> please don't paste multi-line stuff into chat, it's spammy
Jan 04 01:22:33 <zmatt> I don't really understand why you pasted the entire definition of this node, I'm just referring to the fact that it's labeled mmc1 rather than mmc0 (and similarly mmc1 is labeled mmc2, etc)
Jan 04 01:23:12 <zmatt> or rather you pasted some dts file's additional properties for this node, which is even more mysterious
Jan 04 01:24:04 <zmatt> so, no, I'm not referring to anything in what you pasted other than the label of the node
Jan 04 02:06:07 <set_> @zmatt: How did you know about the 4A continuous from the PWR pins on the Servo Headers on the BBBlue?
Jan 04 02:07:50 <set_> Does it have to do w/ the regulator, extra circuitry, and/or both regulator and circuitry?
Jan 04 02:26:11 <set_> I see it says it...4A.
Jan 04 02:30:32 <set_> peak is 6A at typical while 5A is the normal peak current.
Jan 04 02:31:33 <set_> So, no flatlines. Got it.
Jan 04 02:33:42 <set_> So, you guys were going for effeciency?
Jan 04 02:36:09 <set_> I will call the docs. at 4A and see if anyone gestures towards BS. Factors!
**** ENDING LOGGING AT Wed Jan 04 02:59:57 2023