From: Christian Lamparter <chunkeey@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, devicetree@vger.kernel.org
Cc: Paul Mackerras <paulus@samba.org>,
Rob Herring <robh+dt@kernel.org>,
Chris Blake <chrisrblake93@gmail.com>
Subject: [PATCH v2 0/4] powerpc: apm82181: adding customer devices
Date: Sat, 22 Aug 2020 21:35:17 +0200 [thread overview]
Message-ID: <cover.1598124791.git.chunkeey@gmail.com> (raw)
Hello,
I've been holding on to these devices dts' for a while now.
But ever since the recent purge of the PPC405, I'm feeling
the urge to move forward.
The devices in question have been running with OpenWrt since
around 2016/2017. Back then it was linux v4.4 and required
many out-of-tree patches (for WIFI, SATA, CRYPTO...), that
since have been integrated. So, there's nothing else in the
way I think.
A patch that adds the Meraki vendor-prefix has been sent
separately, as there's also the Meraki MR32 that I'm working
on as well. Here's the link to the patch:
<https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-August/216949.html>
Now, I've looked around in the arch/powerpc for recent .dts
and device submissions to get an understanding of what is
required.
From the looks of it, it seems like every device gets a
skeleton defconfig and a CONFIG_$DEVICE symbol (Like:
CONFIG_MERAKI_MR24, CONFIG_WD_MYBOOKLIVE).
Will this be the case? Or would it make sense to further
unite the Bluestone, MR24 and MBL under a common CONFIG_APM82181
and integrate the BLUESTONE device's defconfig into it as well?
(I've stumbled across the special machine compatible
handling of ppc in the Documentation/devicetree/usage-model.rst
already.)
Cheers,
Christian
Note:
If someone has a WD MyBook Live (DUO) and is interested in
giving it a spin with 5.8. I've made a:
"build your own Debian System" sort of script that can be
found on github: <https://github.com/chunkeey/mbl-debian>
(the only remaining patch hack is for debian's make-kpkg crossbuild)
Furthermore, the OpenWrt project currently has images for the
following apm82181 devices:
Cisco Meraki MX60(W) - Needs DSA for the AR8327
Netgear WNDAP620/WNDAP660 - (Could be next)
Netgear WNDR4700 - Needs DSA for the AR8327
Note2: I do have a stash of extensive APM82181 related documentation.
Christian Lamparter (4):
powerpc: apm82181: create shared dtsi for APM bluestone
powerpc: apm82181: add WD MyBook Live NAS
powerpc: apm82181: add Meraki MR24 AP
powerpc: apm82181: integrate bluestone.dts
arch/powerpc/boot/dts/apm82181.dtsi | 485 +++++++++++++++++++++
arch/powerpc/boot/dts/bluestone.dts | 456 +++++--------------
arch/powerpc/boot/dts/meraki-mr24.dts | 237 ++++++++++
arch/powerpc/boot/dts/wd-mybooklive.dts | 199 +++++++++
arch/powerpc/platforms/44x/ppc44x_simple.c | 4 +-
5 files changed, 1033 insertions(+), 348 deletions(-)
create mode 100644 arch/powerpc/boot/dts/apm82181.dtsi
create mode 100644 arch/powerpc/boot/dts/meraki-mr24.dts
create mode 100644 arch/powerpc/boot/dts/wd-mybooklive.dts
--
2.28.0
next reply other threads:[~2020-08-22 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 19:35 Christian Lamparter [this message]
2020-08-22 19:35 ` [PATCH v2 1/4] powerpc: apm82181: create shared dtsi for APM bluestone Christian Lamparter
2020-08-22 19:35 ` [PATCH v2 2/4] powerpc: apm82181: add WD MyBook Live NAS Christian Lamparter
2020-08-22 19:35 ` [PATCH v2 3/4] powerpc: apm82181: add Meraki MR24 AP Christian Lamparter
2020-08-22 19:35 ` [PATCH v2 4/4] powerpc: apm82181: integrate bluestone.dts Christian Lamparter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1598124791.git.chunkeey@gmail.com \
--to=chunkeey@gmail.com \
--cc=chrisrblake93@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).