From: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
To: linux-wireless@vger.kernel.org
Subject: Re: Marvell TopDog Driver Work
Date: Mon, 20 Oct 2008 17:01:37 +0000 (UTC) [thread overview]
Message-ID: <gdidhg$hdq$3@ger.gmane.org> (raw)
In-Reply-To: 1218830917.14841.20.camel@localhost.localdomain
On Fri, 15 Aug 2008 16:08:37 -0400, Dan Williams wrote:
> On Fri, 2008-08-15 at 12:58 -0700, Luis R. Rodriguez wrote:
>> On Fri, Aug 15, 2008 at 12:40:27PM -0700, Pat Erley wrote:
>> > Has anyone stepped up to help in the port of this to mac80211? I
>> > just picked up a wrvs4400n router that uses it and have been worki=
ng
>> > on getting 2.6.XX to work with it.
>>=20
>> Not that I have heard of. Don't know.
>=20
> There's code out there for the TopDog parts (Linville's marvell.git o=
n
> kernel.org), and I even have one or two of them lying around. The
> firmware interface isn't that different from the 8335 (mrv8k) and thu=
s
> the two product lines can probably share the same driver.
>=20
> Lennert and Nick (from Marvell) are supposed to be working on a mac80=
211
> driver for the 88w8687 part, which is probably just about the same
> firmware interface as TopDog (aside from the N-specific bits, and
> different TX & RX descriptors I'm sure). I'd prefer to either start
> fixing up mrv8k and then merge into whatever Lennert comes up with, o=
r
> see what they come up with and use that as a base for adding support =
for
> older TopDog and 8310/8335 hardware.
>=20
> mrv8k was always a bit rocky and never reliably got scan results on t=
he
> 8335 cardbus hardware I had, even though the descriptor setup and the
> mac80211 bits looked right. There's some pre/post scan commands that=
we
> need to hook into mac80211 which I posted patches for first, but
> Johannes requested we not commit those until we really knew whether
> pre/post scan were required.
>=20
> Dan
Duh...
http://git.kernel.org/?p=3Dlinux/kernel/git/mcgrof/mrvl_cb82.git;a=3Dsu=
mmary
Also, I have a router with an 8361 chip and Linux Inside=E2=84=A2 for w=
hich I=20
have made a GPL Source Request. I was told that the sources will be=20
available two weeks from now. I don't expect the wi-fi driver to be in=20
source form in that release, but you never know in advance what they'll=
=20
stuff in there.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-10-20 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48A5DBAB.9080405@erley.org>
2008-08-15 19:58 ` Marvell TopDog Driver Work Luis R. Rodriguez
2008-08-15 20:08 ` Dan Williams
2008-10-20 17:01 ` Daniel Gimpelevich [this message]
2008-10-20 17:36 ` Dan Williams
2008-10-20 18:03 ` Daniel Gimpelevich
2008-10-20 19:45 ` Luis R. Rodriguez
2008-10-20 20:05 ` Daniel Gimpelevich
2008-10-21 13:18 ` Dan Williams
2008-10-21 23:16 ` Daniel Gimpelevich
2008-10-21 23:26 ` Daniel Gimpelevich
2008-10-22 14:28 ` Dan Williams
2008-10-22 5:55 ` John Daiker
2008-10-20 17:42 ` Luis R. Rodriguez
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='gdidhg$hdq$3@ger.gmane.org' \
--to=daniel@gimpelevich.san-francisco.ca.us \
--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).