linux-kernel - Re: [PATCH 0/2] powerpc: Remove support for ppc405/440 Xilinx platforms

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] [day] [month] [year] [list]

Message-ID: <CAK8P3a0i7virtvTJHb2Ssx5zmJ4joKPEjK6timAXGK7BdymzKw@mail.gmail.com>
Date:   Mon, 30 Mar 2020 10:52:11 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Christian Lamparter <chunkeey@...il.com>
Cc:     linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Enrico Weigelt <info@...ux.net>,
        Mark Brown <broonie@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Christophe Leroy <christophe.leroy@....fr>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Michael Ellerman <mpe@...erman.id.au>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jonathan Corbet <corbet@....net>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Matt Porter <mporter@...nel.crashing.org>,
        Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
        Nicholas Piggin <npiggin@...il.com>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        Paul Mackerras <paulus@...ba.org>,
        Rob Herring <robh+dt@...nel.org>,
        Sasha Levin <sashal@...nel.org>,
        DTML <devicetree@...r.kernel.org>, ewald_comhaire@...mail.com
Subject: Re: [PATCH 0/2] powerpc: Remove support for ppc405/440 Xilinx platforms

On Sat, Mar 28, 2020 at 4:07 PM Christian Lamparter <chunkeey@...il.com> wrote:
>
> (Sorry for the bounces, yes my smarthost mail setup breaks from time to time
> and I had to cut the CC since it complained about the length.)
>
> I guess we should think about upstreaming the MyBook Live DTS. Problem here
> is that we deviated a bit from the canyonlands.dts/bluestone.dts structure
> by having a skeleton apm82181.dtsi with most of the SoC defintition and a
> wd-mybooklive.dts for the device.

I don't see much of a problem with that. If the chips are quite
different, then this
would be the right way to do it, and it matches how most dts files are
structured
on arm and others as well.

It would be nice to move over the the bluestone .dts to the apm82181.dtsi file
when that gets added, if only to ensure they use the same description for each
node, but that shouldn't stop the addition of the new file if that is needed for
distros to make use of a popular device.
I see a couple of additional files in openwrt [1],

[obviously, I'm not actually the one in charge here, the decision is with the
 powerpc maintainers].

        Arnd

[1] https://git.openwrt.org/?p=openwrt/openwrt.git;a=tree;f=target/linux/apm821xx/dts;h=d359ba4ed83547438581dd40105e5100d8240beb;hb=HEAD