Message-ID: <4AF1763C.4010901@tsr.se>
Date: Wed, 04 Nov 2009 13:40:28 +0100
From: tsr <tsr.offentlig@tsr.se>
MIME-Version: 1.0
To: Dan Williams <dcbw@redhat.com>
CC: linux-wireless@vger.kernel.org, mangoo@wpkg.org
Subject: Re: Marvell 88w8385 Support
References: <496C8468.4060101@tsr.se>  <20090113145213.GA3623@tuxdriver.com>	 <1231951654.14909.22.camel@localhost.localdomain>	 <496E1D6A.10505@gmail.com>  <496E3075.6090901@tsr.se> <1231959472.14909.73.camel@localhost.localdomain>
In-Reply-To: <1231959472.14909.73.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-wireless-owner@vger.kernel.org

Hi,

So, once again, I try to get my FSG-3 up and running with Debian and I
wonder how thing went with this.

>From what I can tell there was a patch (referenced here:
http://marc.info/?l=linux-wireless&m=123782768023390&w=2) to fix this
but I also get indications that this is not the case since there is both
a USB and miniPCI version of the 88w8385.


You write something
(http://marc.info/?l=linux-wireless&m=124334594302472&w=2) that is
cryptic to me.

Also searching the kernel gittree I found
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/wireless/libertas/if_spi.c;h=06a46d7b3d6c2460aecd793d2827033c7c0348f6;hb=cadeba315cc91ae1b57632e61b0cec3a4ed7088d
which seems to include a driver for the miniPCI libertas 88w8385.

Could you please enlighten me?

Also CC:ing Tomasz Chmielewski since he expressed interest in this too.

Hopefully,
Tomas

Dan Williams escribi?:
> On Wed, 2009-01-14 at 19:35 +0100, tsr wrote:
>> John Daiker wrote:
>>> On 01/14/2009 08:47 AM, Dan Williams wrote:
>>>> On Tue, 2009-01-13 at 09:52 -0500, John W. Linville wrote:
>>>>   
>>>>> On Tue, Jan 13, 2009 at 01:09:12PM +0100, tsr wrote:
>>>>>     
>>>>>> Hi,
>>>>>>
>>>>>> I have a FSG-3 that includes a Marvell 88w8385 card. I wonder if there
>>>>>> is support for it in recent kernels. According to
>>>>>> http://marc.info/?l=linux-wireless&m=123178916308198&w=2 (search for
>>>>>> 8385) there seems to be support but I don't want to start messing 
>>>>>> around
>>>>>> with kernels and stuff without being sure.
>>>>>>        
>>>>> That driver is for SDIO hardware.  It looks like your FSG-3 has
>>>>> mini-PCI?  Either way, we don't have a driver merged yet that would
>>>>> cover your hardware.
>>>>>      
>>>> Looks like it's a CB35, which is actually an 88w8335 MiniPCI card.
>>>> Would be supported by the mwl8k driver ideally.  I've started on trying
>>>> to add support to mwl8k for the 8335 parts, but we'll need to split the
>>>> driver so that we can create IO hooks for the different parts.  It'll be
>>>> a bit, but we'll get there.
>>>>
>>>> Dan
>>>>    
>>> Very interested in the progress of 8335 support at some point.  My 
>>> Netgear wg311v3 is sitting on my desk... waiting for some Linux bits to 
>>> get it running!
>>>
>>> I can assist in testing whenever bits become available ( officially or 
>>> unofficially, hint, hint! :-P )
>>>
>>> Thanks for the hard work, and keep them bits a comin'
>>>
>>> JD
>>>
>> Thanks for the info, I've found something that is said to be a working 
>> drivers for 'my' card in this package: 
>> http://www.seagate.com/staticfiles/maxtor/en_us/downloads/MSSII_3.1.2.src.tgz
>>
>> The kernel source says it's some kind of 2.6 kernel, grepping for it I 
>> found the highest number to be 2.6.14 so maybe it is possible to use 
>> something from it.
>>
>> AFAIK it's also GPL.
> 
> Wow, that is the right driver...  haven't seen a driver for the 8335
> before, but there it is, and it's GPL too.  Got the firmware too, which
> I also haven't seen separately.
> 
> The path forward with this is to port the support for the hardware over
> to mwl8k since the firmware interface is almost the same.
> 
> That said, the only reason I chose that as the path forward was that we
> couldn't make any progress with the standalone driver, and figured that
> Marvell's driver would actually work where mrv8k didn't.  I still think
> it makes sense to use the same driver core for both but if that turns
> out to be too hard, we can just do a mac80211 port for this.
> 
> Dan
> 
>