linux-kernel - Re: [RFC} arm architecture board/feature deprecation timeline

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <a0ecae5c-e72f-4d19-98df-1ab848f36d4b@app.fastmail.com>
Date: Mon, 19 Aug 2024 16:34:10 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Andrew Lunn" <andrew@...n.ch>
Cc: "Jeremy J. Peper" <jeremy@...emypeper.com>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 "Russell King" <linux@...linux.org.uk>,
 "Linus Walleij" <linus.walleij@...aro.org>,
 "Richard Earnshaw" <richard.earnshaw@....com>,
 "Richard Sandiford" <richard.sandiford@....com>,
 "Ramana Radhakrishnan" <ramanara@...dia.com>,
 "Nicolas Pitre" <nico@...xnic.net>,
 "Krzysztof Kozlowski" <krzk@...nel.org>,
 "Mark Brown" <broonie@...nel.org>,
 "Kristoffer Ericson" <kristoffer.ericson@...il.com>,
 "Robert Jarzmik" <robert.jarzmik@...e.fr>,
 "Aaro Koskinen" <aaro.koskinen@....fi>,
 "Janusz Krzysztofik" <jmkrzyszt@...il.com>,
 "Tony Lindgren" <tony@...mide.com>,
 Linux-OMAP <linux-omap@...r.kernel.org>,
 "Nikita Shubin" <nikita.shubin@...uefel.me>,
 linux-samsung-soc@...r.kernel.org,
 "Sebastian Hesselbarth" <sebastian.hesselbarth@...il.com>,
 "Gregory Clement" <gregory.clement@...tlin.com>,
 debian-arm@...ts.debian.org,
 "Dmitry Torokhov" <dmitry.torokhov@...il.com>,
 "Alexandre Torgue" <alexandre.torgue@...s.st.com>
Subject: Re: [RFC} arm architecture board/feature deprecation timeline

On Mon, Aug 19, 2024, at 16:23, Andrew Lunn wrote:
> On Mon, Aug 19, 2024 at 04:12:10PM +0200, Arnd Bergmann wrote:
>
> It is a long time since i looked at Orion, so i could be wrong....
>
> As far as i remember, it has a PCI controller and a PCIe
> controller. They are slightly different. The PCIe part is i think
> simpler to support, it follows the standards better. I _think_ the PCI
> controller uses a GPIO for interrupt support, which causes a mess.
>
> If only PCIe is needed, it should not be too hard to make work. I
> would try to avoid the PCI controller is possible.

This machine uses both PCIe (for ethernet) and PCI (for SATA).

The PCIe driver is arch/arm/plat-orion/pcie.c and is shared
with mach-dove and mach-mv78xx0, previously also with kirkwood
and presumably armadaxp, which now use the more modern
drivers/pci/controller/pci-mvebu.c.

I just looked at the other dts files for orion5x and see
that they still use the old pci/pcie driver without an
entry in the dts files.

This is clearly not where we want to be in the long run,
but doing the same thing for the terastation_pro2
is at least not going to make it worse.

       Arnd