[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201011121126.08630.florian@openwrt.org>
Date: Fri, 12 Nov 2010 11:26:08 +0100
From: Florian Fainelli <florian@...nwrt.org>
To: Roland Dreier <rdreier@...co.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Greg KH <greg@...ah.com>,
Arnaud Lacombe <lacombar@...il.com>,
Anca Emanuel <anca.emanuel@...il.com>,
Elvis Dowson <elvis.dowson@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Forked android kernel development from linux kernel mainline
On Friday 12 November 2010 04:15:56 Roland Dreier wrote:
> > > > Isn't the openwrt stuff just drivers and some arch specific code?
> > > > Nothing that is core infrastructure, and nothing preventing them
> > > > from submitting the drivers and arch code if they want to, right?
> > >
> > > Actually openwrt has some core infrastructure for managing (ethernet)
> > > switches as extra-fancy multiport PHYs. That means that all the
> > > drivers in openwrt for the typical 5-8 port switches in home routers
> > > don't really apply to mainline.
> >
> > Why not? Those switches _ARE_ extra-fancy multiport PHYs. And AFAICT
> > we have no support for this stuff in mainline at all.
> >
> > So where is the problem ?
>
> There's no real problem. I was just pointing out that the openwrt
> switch stuff actually does have some core infrastructure that mainline
> is missing. ie openwrt is not just drivers and arch code.
>
> But yes I agree mainline should really do a better job of supporting
> ethernet switches, and clearly openwrt has the most real-world
> experience with implementing that.
We are in the process of cleaning up that code and hope to submit for review
within the next few weeks.
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists