mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	David.Woodhouse@intel.com, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	Lennert Buytenhek <buytenh@wantstofly.org>,
	Holger Schurig <holgerschurig@googlemail.com>,
	Markus Becker <mab@comnets.uni-bremen.de>,
	andreamrl@tiscali.it, Denis Kirjanov <kirjanov@gmail.com>,
	dwmw2@infradead.org
Subject: Re: Re-distributable 88w8335 Firmware?
Date: Wed, 08 Dec 2010 18:13:33 -0600	[thread overview]
Message-ID: <1291853616.16839.10.camel@dcbw.foobar.com> (raw)
In-Reply-To: <AANLkTiks65oAvVEu0Df4yeHNJm=cVnSfFeo=enxt-gpn@mail.gmail.com>

On Wed, 2010-11-24 at 16:26 +1100, Julian Calaby wrote:
> On Wed, Nov 24, 2010 at 16:10, Dan Williams <dcbw@redhat.com> wrote:
> > On Wed, 2010-11-24 at 15:48 +1100, Julian Calaby wrote:
> >> On Wed, Nov 24, 2010 at 15:13, Dan Williams <dcbw@redhat.com> wrote:
> >> > Malo supports the PCMCIA/CF variant of the 8385; not a PCI variant
> >> > AFAICT.  I know of no PCI variant for the 8385, just CF, SDIO, and GSPI.
> >> > But I find it curious that malo supports 8335+8385, given that the
> >> > firmware interface of the 8385 and the 8335 are so different.  Unless
> >> > they have special firmware, the 8385 is a fullmac device, while the 8335
> >> > is a softmac device.  Enough differences exist that I'd expect them to
> >> > be driven by separate drivers, otherwise the code would be quite ugly.
> >> > Which is why we didn't try to shoehorn the 8335 or TopDog stuff into
> >> > libertas.
> >>
> >> You clearly know a hell of a lot more about the ins and outs of Marvel
> >> chipsets that I do. =)
> >
> > Eh, *some* of the chipsets :)  Others (Lennert) know a lot more about
> > later versions than I do.  But I never know everything or even enough of
> > anything :)
> 
> I know exactly how you feel. =)
> 
> >> I stand corrected.
> >>
> >> So, to amend my previous request: We're after firmware for the softmac
> >> 88w8335 chipset *only*.
> >>
> >> Though it may be nicer if Marvell were to bless Malo's firmware
> >> package (linked above) as this contains firmware for the PCI 88w8335,
> >> USB 88w8338 and a file which claims to be for the PCMCIA/CF 88w8385.
> >
> > Yeah, though honestly I'd rather have the duplex firmware from MSSII for
> > the 8335, since it can do AP mode too.  That does leave the 8338 (USB?)
> 
> Me too - and it'd mean that we don't have to do AP-mode firmware
> loading tricks like in mw8k. But if we can't get that then some
> firmware is better than none.
> 
> > of course but we can probably get clarification on that too.  As with
> > the 8335, I only have access to a 8335 Windows driver, but if we had a
> > firmware extractor tool, I believe the Marvell Extranet firmware license
> > covers embedded firmware from Windows .sys files too.
> 
> I think I may have a simple firmware extractor at home that I pulled
> from *somewhere* when I was working on this last time. We can see if
> it does anything with those files. I believe I have at least two
> different Windows drivers at home - IIRC, one of them is *just* the
> files needed for this extractor.

I've converted the cb35 duplex firmware to binary and uploaded it to
linux-firmware after receiving permission from Marvell to do so.  Now
lets get a driver :)

Dan



  reply	other threads:[~2010-12-09  0:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-20  0:29 Julian Calaby
2010-11-24  3:31 ` Dan Williams
2010-11-24  3:55   ` Julian Calaby
2010-11-24  4:13     ` Dan Williams
2010-11-24  4:48       ` Julian Calaby
2010-11-24  5:10         ` Dan Williams
2010-11-24  5:26           ` Julian Calaby
2010-12-09  0:13             ` Dan Williams [this message]
2010-12-09  0:36               ` 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=1291853616.16839.10.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=David.Woodhouse@intel.com \
    --cc=andreamrl@tiscali.it \
    --cc=buytenh@wantstofly.org \
    --cc=dwmw2@infradead.org \
    --cc=greg@kroah.com \
    --cc=holgerschurig@googlemail.com \
    --cc=julian.calaby@gmail.com \
    --cc=kirjanov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mab@comnets.uni-bremen.de \
    /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

all inboxes | Powered by JetHome®