Return-path: Received: from fw.wantstofly.org ([80.101.37.227]:64126 "EHLO mail.wantstofly.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751292Ab2D0J6p (ORCPT ); Fri, 27 Apr 2012 05:58:45 -0400 Date: Fri, 27 Apr 2012 11:58:42 +0200 From: Lennert Buytenhek To: sedat.dilek@gmail.com Cc: "John W. Linville" , linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mwl8k: Add 0x2a02 PCI device-id (Marvell 88W8361) Message-ID: <20120427095842.GW3157@wantstofly.org> (sfid-20120427_115904_407031_C73EDCF7) References: <1335517711-6522-1-git-send-email-sedat.dilek@gmail.com> <20120427091405.GS3157@wantstofly.org> <20120427094007.GU3157@wantstofly.org> <20120427094637.GV3157@wantstofly.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: 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.