On Tue, 2008-07-15 at 13:58 -0400, Dan Williams wrote:
quoted text
> On Tue, 2008-07-15 at 13:31 -0400, Nicolas Pitre wrote:
> > On Tue, 15 Jul 2008, Dan Williams wrote:
> > 
> > > On Thu, 2008-07-10 at 18:15 +0200, Michael Buesch wrote:
> > > > On Thursday 10 July 2008 18:12:32 Stefanik Gábor wrote:
> > > > > Some other topics which might be of interest/good to include:
> > > > > - New chipsets needing drivers (SiS 16x, Marvell, etc.)
> > > > 
> > > > I have no idea what to discuss about non-existing drivers, really.
> > > > Something like: "Do we need that driver? Everyone votes YES and is happy"?
> > > 
> > > Maybe during the week we could organize some hackfests to work on the
> > > Marvell/SiS/etc mac80211 drivers?  Everyone bring their favorite
> > > non-working Marvell 88w83xx card and we make mrv8k our bitch or
> > > something like that.
> > 
> > FYI...
> > 
> > Lennert Buytenhek and I are writing a GPL driver for mv8300 class of 
> > Marvell WIFI chips right now, present and future versions. This is 
> > Marvell work as we work for Marvell.  I have access to firmware sources, 
> > etc. but obviously cannot share them.
> > 
> > We both will be in Ottawa next week.
> 
> Great!  Lets definitely sit down and talk then.  There is already some
> GPL-ed source code for 83xx chips out there but it always used net80211,
> not mac80211.  So the mrv8k effort is meant to write a mac80211 driver
> for 8310/8335/etc and perhaps TopDog chips too since they don't seem
> that much different from a driver perspective.
> 
> Some of the issues with the current Marvell 83xx GPL drivers that have
> gotten out are (a) code style, (b) lots of commented out stuff that's
> never used, (c) OS abstraction that's unnecessary on Linux, (d) doesn't
> use mac80211, and (e) uses private ioctls.  So hopefully you're writing
> a new 83xx driver from scratch :)
> 
> We cleaned up a lot of stuff for the OLPC 8388 libertas driver, but
> unfortunately we never were able to get the Marvell 8388 team onboard,
> and so they just went off and kept working on their driver and didn't
> really move the upstream libertas driver forward at all.

Forgot to finish this last bit...

So hopefully that won't happen here, since this would be pretty much the
same situation up to this point.  Ideally you can get the internal
Marvell developers onboard so we're all working on essentially the same
bits, exactly like Intel has done.  Yeah, they develop on private trees
internally but at the end of the day, their base code is the same
upstream base code everyone else uses.

Dan

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/