linux-kernel - Re: [PATCH] ARM: dts: omap4-panda-a4: Add missing model and compatible properties

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250122234119.0913cb4f@akair>
Date: Wed, 22 Jan 2025 23:41:19 +0100
From: Andreas Kemnade <andreas@...nade.info>
To: Tom Rini <trini@...sulko.com>
Cc: Robert Nelson <robertcnelson@...il.com>, Kevin Hilman
 <khilman@...nel.org>, linux-kernel@...r.kernel.org, Nishanth Menon
 <nm@...com>, Tony Lindgren <tony@...mide.com>, Rob Herring
 <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, linux-omap@...r.kernel.org,
 devicetree@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: omap4-panda-a4: Add missing model and
 compatible properties

Am Wed, 22 Jan 2025 16:18:43 -0600
schrieb Tom Rini <trini@...sulko.com>:

> 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@...sulko.com> 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@...nade.info> wrote:  
> > > > >
> > > > > Hi,
> > > > >
> > > > > Am Tue, 21 Jan 2025 18:08:24 -0600
> > > > > schrieb Tom Rini <trini@...sulko.com>:
> > > > >  
> > > > > > > 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?
> 
maybe people just revert to omap4-panda.dtb, it should not hurt having
internal and external pullups. I have the A2.

Regards,
Andreas