From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org, marvell8385-devel@linuxtogo.org,
frankh@marvell.com, rchokshi@marvell.com
Subject: Re: How to start with a Marvell driver (non-USB, non-OLPC)
Date: Fri, 9 Feb 2007 15:24:52 +0100 [thread overview]
Message-ID: <200702091524.52389.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1171025367.2902.22.camel@localhost.localdomain>
> > I think the biggest problem here is the firmware. The OLPC
> > people have a special firmware for their USB dongle, which
> > is not used in other chips, so a driver that has been
> > heavily adapted to this firmware isn't easy to mangle to a
> > different firmware.
>
> No, it really hasn't. The mesh-specific bits are a separate
> code path, and we routinely run non-mesh firmware using this
> driver. If there are places that are missing run-time
> firmware version checks, then we need to fix those places.
In the libertas mailing list someone published the "WLAN Firmware
Spec v5.1" spec, so I guess that you're now using this firmware.
But the Windows driver that I got hold on (to extract the
firmware) all had a 5.0 in their driver name, so I guess they
have a v5.0 firmware.
But I guess this can be handled with if (fw_version >=
FW_VERSION_5_1) or something like this.
> Again, why don't we work together? We are _not_ intentionally
> screwing over anybody else, and if there are pieces that you
> need, why don't we put those pieces back in?
Based on the things you said, I see no reason NOT to work
together.
> We are _not_ intentionally screwing over anybody else, and if
> there are pieces that you need, why don't we put those pieces
> back in?
I did not say this. I just saw in GIT that you remove misc things
or discussed the removed of things (e.g. CIS related code), so I
guessed that you only go into the USB dongle direction. But
maybe you weren't aware that other WLAN devices with similar
chips, but different host interface are available.
> The original libertas hardware abstraction bits really sucked.
Did they release them as GPL as well? Or do you refer to the
copyrighted driver that is downloadable from some vendors?
I'm already in libertas-dev, so when I have time to look at the
driver, I'll post some patches there. Rigth now I don't have
much, e.g. I just put the infrastructure in place so that the
PCMCIA subsystem detects the card and loads my driver.
next prev parent reply other threads:[~2007-02-09 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 7:58 How to start with a Marvell driver (non-USB, non-OLPC) Holger Schurig
2007-02-09 12:35 ` John W. Linville
2007-02-09 12:49 ` Dan Williams
2007-02-09 14:24 ` Holger Schurig [this message]
2007-02-09 15:49 ` Dan Williams
2007-02-15 8:40 ` Holger Schurig
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=200702091524.52389.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=dcbw@redhat.com \
--cc=frankh@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marvell8385-devel@linuxtogo.org \
--cc=rchokshi@marvell.com \
/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.