From: Dan Williams <dcbw@redhat.com>
To: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Marvell TopDog Driver Work
Date: Tue, 21 Oct 2008 09:18:13 -0400 [thread overview]
Message-ID: <1224595093.24581.15.camel@localhost.localdomain> (raw)
In-Reply-To: <1224533105.6873.22.camel@the-omnibook>
On Mon, 2008-10-20 at 13:05 -0700, Daniel Gimpelevich wrote:
> On Mon, 2008-10-20 at 12:45 -0700, Luis R. Rodriguez wrote:
> > On Mon, Oct 20, 2008 at 11:03 AM, Daniel Gimpelevich
> > <daniel@gimpelevich.san-francisco.ca.us> wrote:
> >
> > > The "Duh..." was a response to the "Not that I have heard of. Don't
> > > know." statement, which was pretty ironic.
> >
> > Well your question was "Has anyone stepped up to help in the port of
> > this to mac80211" and I thought you already knew I had that tree.
>
> I did not ask that, because I saw the tree, and that the initial import
> was from the marvell.git tree. The OP might not have realized that the
> code was TopDog-related even if he did see it. Since there is no working
> mac80211 code for TopDog, any existing hardware-specific code for it may
> prove to be a useful reference during the porting process. Anybody
> investigating the possibility of stepping up to help in the port needs
> to know what is already available and what is not.
Definitely, I've looked at marvell.git (topdog) and Luis's code, and
earlier Marvell GPL code quite extensively. The firmware interface is
quite similar between the TopDog (802.11n) parts and the b/g parts, as
are the TX and RX descriptors. From my research, I didn't think it
would be that hard to support both parts in the same driver.
My strategy would be this, assuming you have TopDog hardware. If you do
not, I can ship you a CardBus TopDog card:
1) Use marvell.git and Luis' attempt to get minimal b/g support working
for the TopDog parts
2) Start adding in the support for 8335/8310 parts using mrv8k (and
possibly BSD's malo(4)) as a guide
3) Add the 802.11n bits of TopDog stuff
The _most_ important thing is first to get a stable b/g driver, then add
the candy later. Since we have a full TopDog driver implementation,
that might be the best thing to get working first. mrv8k was never able
to get very far for me when I was poking at it, I couldn't even get
reliable scan results.
> I don't think there is any question of *whether* TopDog support is
> possible in mrv8k, only when, and "right now" does not yet appear to be
> the answer. I really hope to be proven wrong on that, though.
Oh, it's certainly possible in mrv8k. But obviously you just want to
get something up and running first, then add the tasty bits like N
support later.
Dan
next prev parent reply other threads:[~2008-10-21 13:19 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
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 [this message]
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=1224595093.24581.15.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=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).