public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Marvell TopDog Driver Work
Date: Tue, 21 Oct 2008 16:16:43 -0700	[thread overview]
Message-ID: <1224631003.6873.39.camel@the-omnibook> (raw)
In-Reply-To: <1224595093.24581.15.camel@localhost.localdomain>

On Tue, 2008-10-21 at 09:18 -0400, Dan Williams wrote:
> 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:

The only TopDog hardware I have is the aforementioned Orion-based
router, which has OpenWRT in its future. That certainly fits the
strategy, but with somewhat unfortunate timing. I previously had access
to an 8335 card, but don't currently.

> 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

That contrasts slightly with the understanding I had:
1) Use the in-tree libertas library to get b/g going for 8335/8310
parts, using mrv8k/malo as a guide.
2) Start adding in the support for TopDog parts in b/g mode, from
mrvl_cb82.git
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.

I could not agree more.

> Since we have a full TopDog driver implementation,

Do we?

> 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.


  reply	other threads:[~2008-10-21 23:16 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
2008-10-21 23:16                 ` Daniel Gimpelevich [this message]
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=1224631003.6873.39.camel@the-omnibook \
    --to=daniel@gimpelevich.san-francisco.ca.us \
    --cc=dcbw@redhat.com \
    --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