[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120427095842.GW3157@wantstofly.org>
Date: Fri, 27 Apr 2012 11:58:42 +0200
From: Lennert Buytenhek <buytenh@...tstofly.org>
To: sedat.dilek@...il.com
Cc: "John W. Linville" <linville@...driver.com>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mwl8k: Add 0x2a02 PCI device-id (Marvell 88W8361)
On Fri, Apr 27, 2012 at 11:56:00AM +0200, Sedat Dilek wrote:
> >> >> Are you planning to or even working on support (for) 8361 devices?
> >> >
> >> > I don't have any such plans, and I don't know of anyone who does.
> >>
> >> Does 8361 require firmware support?
> >
> > What do you mean by that?
>
> IIRC ath5k for example needs no external firmware file.
The 8361 requires firmware to be loaded into it before it'll do
anything useful.
> >> Does a firmware file exist (name?)?
> >
> > There's firmware for the 8361 out there, however, that version of
> > the firmware implements a firmware API that is different from the
> > one that mwl8k currently implements.
> >
> > You could add 8361 support to mwl8k, but then you'd have to go over
> > all the firmware command invocations in mwl8k and make sure that they
> > will work on the 8361 firmware that you're trying to support as well.
>
> Without having a 8361 this will be even harder to walk through.
>
> Anyway, thanks for your detailed explanations.
>
> What's the alternative for such affected users?
> Use ndis-wrapper?
I'm not sure. I've never tried to get a 8361 work under Linux.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists