On Wed, Jan 22, 2025 at 4:18 PM Tom Rini <trini@xxxxxxxxxxxx> wrote: > > On Wed, Jan 22, 2025 at 03:52:47PM -0600, Robert Nelson wrote: > > On Wed, Jan 22, 2025 at 3:10 PM Tom Rini <trini@xxxxxxxxxxxx> wrote: > > > > > > On Wed, Jan 22, 2025 at 02:56:19PM -0600, Robert Nelson wrote: > > > > On Wed, Jan 22, 2025 at 2:46 PM Andreas Kemnade <andreas@xxxxxxxxxxxx> wrote: > > > > > > > > > > Hi, > > > > > > > > > > Am Tue, 21 Jan 2025 18:08:24 -0600 > > > > > schrieb Tom Rini <trini@xxxxxxxxxxxx>: > > > > > > > > > > > > If keeping it is just this binding update, then I'd say we keep it, but > > > > > > > if it gets any more paninful to maintain, I'm also not going to argue > > > > > > > very hard to keep it. > > > > > > > > > > > > I'm not in the position to see if any of the Pandaboards work at this > > > > > > point, so I don't know if they're otherwise functional or a huge pile of > > > > > > problems. > > > > > > > > > > I am still testing stuff with pandaboards. But I do not have the a4 > > > > > one. So yes they are functional. Compared with other devices still in > > > > > use using the same SoC, here you can play around with everything, know > > > > > the device. so it is a reference for keeping the really interesting > > > > > devices working. > > > > > > > > > > Regarding the a4: I think it is better to keep that one in, just that > > > > > nobody gets confused if he/she digs out his panda board for some > > > > > comparison test and uses a wrong board revision. > > > > > > > > Do you want an a4? I could dig one or two out! ;) > > > > > > Unless I'm missing something, the a4 hasn't been bootable by upstream in > > > about 10 years now... There's no top-level compatible, so there's no > > > match in the generic board code. I can't recall if the A4 versions were > > > available to anyone other than maintainers and beagleboard.org folks > > > themselves as part of bring-up/testing. I know I had one and ewasted it > > > a while ago. > > > > PandaBoard EA1->A3 = omap4-panda.dtb > > PandaBoard A4->+ (non ES) = omap4-panda-a4.dtb > > > > A4 was the final production version of the non ES Panda.. > > Oh! My memory sucks here, sorry for the confusion. But it's also still > the case that omap4-panda-a4.dtb hasn't had a top-level compatible > string, so can it even be functionally used? Looking back, I moved from PandaBoard -> WandBoard for BeagleBoard.org's build infacature.. Dual A9/USB vs Quad A9/SATA... yeah.. sata was more stable then USB.. I think it was around v5.4 lts I gave up on Panda's... SO 5.4.x would have been the last time I personally used the panda's on mainline.. Digging more, yay for omappedia! ;) https://omappedia.com/wiki/PandaBoard_Revisions I never personally saw the A5 or A6 rev's in my hand.. What's scary, teh A4's changed the hdmi pins: https://git.ti.com/gitweb?p=ti-linux-kernel/ti-linux-kernel.git;a=blob;f=arch/arm/boot/dts/omap4-panda-a4.dts;h=f1a6476af3716489007c12141d06f208ec2ebc94;hb=refs/heads/ti-linux-4.14.y Yet no gpio id change.. Regards, -- Robert Nelson https://rcn-ee.com/