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.. Sadly we still have stock! ... From Circuitco before they went out of Business (10 years ago)... https://www.digikey.com/en/products/detail/circuitco-electronics-llc/UEVM4430G-01-00-00/2349866 However there are two versions of the A4, with different memory: ELPIDA and Micron.. ELPIDA works fine (well last i really cared/tested it was u-boot v2019.04).. Where as Micron.. Which has the same bug as PandaBoard ES Rev B3, with a new memory (only one Chip Select vs 2 (or reversed)).. I could get it boot via nuking the CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS define in include/configs/ti_omap4_common.h v2019.04 Things we learned from `that` OEM... When you run out of memory chips, don't randomly swap parts without at least changing the ID... Otherwise customers will be pissed, when old software doesn't work.. Regards, -- Robert Nelson https://rcn-ee.com/
