On Fri, Apr 27, 2012 at 11:58 AM, Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx> wrote: > 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. Just found on [1] this same wrong patch in [2] :-). Dunno if [3] worked and from where they have stolen fw-files. - Sedat - [1] https://dev.openwrt.org/ticket/7209 [2] https://dev.openwrt.org/attachment/ticket/7209/mwl8k_fix_pci_id.patch [3] https://dev.openwrt.org/attachment/ticket/7209/mwl8k_8361p.patch -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
