Re: [PATCH 0/6] Re-instate octeon staging drivers

[Chris Packham]

On Wed, 2020-03-04 at 12:50 +0100, Greg KH wrote:
> On Wed, Mar 04, 2020 at 06:25:34PM +0800, YunQiang Su wrote:
> > Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> ä2020å3æ4æåä äå2:39åéï
> > > 
> > > On Wed, Mar 04, 2020 at 09:48:46AM +0800, YunQiang Su wrote:
> > > > Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> ä2020å2æ13æåå äå5:52åéï
> > > > > 
> > > > > On Wed, Feb 05, 2020 at 01:11:10PM +1300, Chris Packham wrote:
> > > > > > This series re-instates the octeon drivers that were recently removed and
> > > > > > addresses the build issues that lead to that decision.
> > > > > > 
> > > > > > I've approached Cavium/Marvell about taking a more active interest in getting
> > > > > > the code out of staging and into their proper location. No reply on that (yet).
> > > > > 
> > > > > Good luck with talking to the companies, hopefully that will work.
> > > > > 
> > > > > Anyway, I've applied this series, thanks for this, let's see what breaks
> > > > > now :)
> > > > 
> > > > Did you meet any problem to merge Chris's patchset?
> > > 
> > > They are all in linux-next, so you can see for yourself :)
> > 
> > Thank you so much. I found it.
> > It is very important for Debian MIPS Ports as we are using some of
> > Octeon machines.
> 
> If it is so important, why is no one working on fixing these drivers up?
> 

I have had a reply from Marvell. They've contracted support for the old
Cavium Octeon designs out to an external company. I'm not sure that
means that we'll see some action on these drivers any time soon but at
least they're doing something.