From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Hemminger <shemminger@linux-foundation.org>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: wireless chipsets not supported by current wireless tree
Date: Mon, 19 Mar 2007 10:27:01 -0400 [thread overview]
Message-ID: <1174314421.10751.8.camel@localhost.localdomain> (raw)
In-Reply-To: <200703190847.31321.hs4233@mail.mn-solutions.de>
On Mon, 2007-03-19 at 08:47 +0100, Holger Schurig wrote:
> > Is there a chance of or anyone already working on Marvell
> > (non-OLPC) support, e.g., for one of these?
> >
> > 00:09.0 Ethernet controller: Marvell Technology Group Ltd.
> > 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
That chip has some significant differences to the 838x line that the
OLPC and others are using. I'm not sure we can support that chipset in
the same driver, unless its firmware interface is quite similar.
> Yes, there is someone working there. A bunch of my patches to
> shape the OLPC driver in a way libertas_lib.ko, libertas_usb.ko,
small note: I'd rather have the bus-independent part be called
"libertas.ko" rather than _lib.
> libertas_cs.ko got already applied. I made some experiments with
> firmware download, David Anders wrote a fwcutter and so on.
>
> I once created a project
> http://projects.linuxtogo.org/projects/marvell8385/, but most of
> the discussion happend now in the OLPC Marvell mailing list.
> From time to time we're also on #libertas on *.freenode.net.
The list and channel aren't supposed to be OLPC specific, really, hence
the generic "libertas-dev" name and such. Since you're around, it's no
longer only OLPC people happening to work on the driver, and that's the
way it should be.
> Nothing works yet, and I got (and will get) distracted because my
> company switched to SAP Business One and I'm mostly busy
> extracting data out of our old system and putting that into
> SAPB1 :-( Maybe I have again time this week.
Great. Let's make the driver Not Suck :)
Dan
next prev parent reply other threads:[~2007-03-19 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 5:44 wireless chipsets not supported by current wireless tree Stephen Hemminger
2007-03-17 5:57 ` Randy Dunlap
2007-03-17 6:02 ` Michael Wu
2007-03-19 7:47 ` Holger Schurig
2007-03-19 14:27 ` Dan Williams [this message]
2007-03-21 4:07 ` Pavel Roskin
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=1174314421.10751.8.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rdunlap@xenotime.net \
--cc=shemminger@linux-foundation.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).