On Sun, Sep 06, 2020 at 12:06:10AM +0200, Christian Lamparter wrote: > 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://lore.kernel.org/linuxppc-dev/20200822154045.16036-1-chunkeey@xxxxxxxxx/> > > 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.) I haven't found any traces of this to be applied. What is the status of this patch series? And what is the general state of affairs for the PPC44x? -- With Best Regards, Andy Shevchenko
