linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tsr <tsr.offentlig@tsr.se>
To: linux-wireless@vger.kernel.org
Subject: Re: Marvell 88w8385 Support
Date: Sat, 17 Jan 2009 23:59:19 +0100	[thread overview]
Message-ID: <497262C7.40105@tsr.se> (raw)
In-Reply-To: <1232127390.22915.9.camel@174-147-64-233.pools.spcsdns.net>

Dan Williams wrote:
> On Wed, 2009-01-14 at 13:57 -0500, Dan Williams wrote:
>> 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.
> 
> As a follow-up... the driver source contained in that tarball compiles
> after a few trivial changes to update net80211 and hardware parts to the
> latest kernel.  However, the firmware does not successfully load.  It
> appears that the firmware load procedure for the MSSII driver is a
> one-stage firmware load that probably depends on a minimal bootloader on
> firmware of the card, or something like that.  In any case, it doesn't
> work.
> 
> I spent some time porting over the firmware loading from mrv8k (which is
> known to work), and got as far as successful boot and main firmware
> load, but I'm not having a ton of success getting the card to actually
> boot the main firmware.  More poking required.  If the MSSII driver can
> actually *drive* 8335 cards, then we can use that as a reference for
> hardware/firmware API when adding support for 8335 to mwl8k.
> 
> Dan
> 

Ok, so both good and bad news I guess (for me the good news is that work
is being done ;)

Is there anything I can do to help, with regards to testing, etc? I'm
extremely unexperienced with kernels, but with some help I will dare to 
compile my own.

/tsr


  parent reply	other threads:[~2009-01-17 22:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 12:09 Marvell 88w8385 Support tsr
2009-01-13 14:52 ` John W. Linville
2009-01-14 16:47   ` Dan Williams
2009-01-14 17:14     ` John Daiker
2009-01-14 18:35       ` tsr
2009-01-14 18:57         ` Dan Williams
2009-01-16 17:36           ` Dan Williams
2009-01-17 16:20             ` tsr
2009-01-19  9:00               ` Holger Schurig
2009-01-17 22:59             ` tsr [this message]
2009-11-04 12:40           ` tsr
2009-11-04 15:29             ` Holger Schurig
2009-11-04 20:34               ` Dan Williams
2009-11-04 22:35                 ` Julian Calaby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=497262C7.40105@tsr.se \
    --to=tsr.offentlig@tsr.se \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).