From: Dan Williams <dcbw@redhat.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: Re: Netgear WG311v3 - Marvell 88w8355 "Libertas"
Date: Mon, 03 Mar 2008 10:28:37 -0500 [thread overview]
Message-ID: <1204558117.3155.1.camel@localhost.localdomain> (raw)
In-Reply-To: <646765f40803022006h39ec0c43uf9af99924dedc29@mail.gmail.com>
On Mon, 2008-03-03 at 15:06 +1100, Julian Calaby wrote:
> On Mon, Mar 3, 2008 at 11:55 AM, Dan Williams <dcbw@redhat.com> wrote:
> >
> > On Mon, 2008-03-03 at 09:01 +1100, Julian Calaby wrote:
> > > Well, that explains why the "Libertas" parts supported by the current
> > > kernel require firmware and why the ndiswrapper driver I'm using
> > > doesn't.
> >
> > The 8335 still requires firmware. Lots of the windows drivers embed the
> > firmware into the .sys or .dll files, whereas on Linux embedding
> > firmware into the driver is quite frowned upon.
>
> Yeah, I discovered that the mrv8k driver still requires firmware,
> despite there being no actual file in the windows driver that I can
> point to as being the firmware image.
It's likely embedded into the sys file, try:
http://www.saillard.org/linux/mrv8k/files/mrv8k_extract_fw.c
to extract the firmware from a supported driver file. At least one
versoin of WG311v3 driver seems to be supported there ("NETGEAR
WG311v3", "3.1.1.7") for extracting the firmware from.
Dan
next prev parent reply other threads:[~2008-03-03 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 11:19 Netgear WG311v3 - Marvell 88w8355 "Libertas" Julian Calaby
2008-03-02 15:33 ` Dan Williams
2008-03-02 22:01 ` Julian Calaby
2008-03-03 0:55 ` Dan Williams
2008-03-03 4:06 ` Julian Calaby
2008-03-03 15:28 ` Dan Williams [this message]
2008-03-03 21:32 ` 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=1204558117.3155.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=julian.calaby@gmail.com \
--cc=libertas-dev@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.