Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Markus Becker <mab@comnets.uni-bremen.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mrv8k: now gets scan results
Date: Wed, 21 May 2008 12:48:08 -0400	[thread overview]
Message-ID: <1211388488.4232.5.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0805211711450.3750@bugs.comnets.uni-bremen.de>

On Wed, 2008-05-21 at 17:20 +0200, Markus Becker wrote:
> On Wed, 21 May 2008, Dan Williams wrote:
> 
> > On Wed, 2008-05-21 at 09:08 +0200, Markus Becker wrote:
> >> Hi Dan,
> >>
> >> I just tested it and my Option Fusion+ HSDPA card does not scan:
> >>
> >> May 21 08:52:17 shelbyville kernel: Command timeout
> >> May 21 08:52:17 shelbyville kernel: Could not set channel
> >> May 21 08:52:17 shelbyville kernel: ~Failed to set channel
> >> May 21 08:52:17 shelbyville kernel: wlan1: failed to set freq to 2417 MHz for scan
> >
> > Interesting; it does take the firmware upload though, right?  What
> > firmware version gets reported by the driver when it loads?  I'll have
> > to try again with my Netgear PCI card which was a lot more unhappy with
> > the driver than my 3Com CardBus one.
> 
> The firmware loads fine for me, see below:
> May 21 08:50:40 shelbyville kernel: 0000:16:00.0 (mrv8k): successfully uploaded firmware
> May 21 08:50:40 shelbyville kernel: 0000:16:00.0 (mrv8k): MAC address 00:0c:e3:xx:xx:xx
> May 21 08:50:40 shelbyville kernel: 0000:16:00.0 (mrv8k): HW ver. 3, FW ver. 0x3020007, 2 antennas, regulatory domain EU

Yay, this means the regulatory domain codes are what I expected them to
be :)  Also, is this an 8335, or an 8310?

Dan

> >
> > I spent some time checking through marvell.git from Linville's repo on
> > kernel.org too, and it looks like we may be able to pull a lot of
> > constants and commands from that.  The RX and TX descriptors are
> > somewhat different, but I've generally found that Marvell's drivers and
> > firmware share a lot of API/ABI (would be stupid to break stuff all the
> > time anyway, even in closed source).  We may be able to use mrv8k for
> > the TopDog 802.11n PCI and USB parts as well since they are so similar
> > from a programming perspective.
> >
> > Dan
> >
> >> May 21 08:52:19 shelbyville kernel: Command timeout
> >> May 21 08:52:19 shelbyville kernel: Could not set channel
> >> May 21 08:52:19 shelbyville kernel: ~Failed to set channel
> >> May 21 08:52:19 shelbyville kernel: wlan1: failed to set freq to 2422 MHz for scan
> >> [...]
> >>
> >> I also got some lockups, however I have no infrastructure setup to debug
> >> those.
> >>
> >> Thanks for all your efforts,
> >> Markus
> >>
> >> On Tue, 20 May 2008, Dan Williams wrote:
> >>
> >>> Hi,
> >>>
> >>> I've gotten mrv8k to the point where I can get scan results with it on
> >>> my 3COM 3CRGPC10075 CardBus card.  Data RX still doesn't work for some
> >>> reason and WEP associations still fail with a mac80211 timeout.  Enough
> >>> for today though.  All changes pushed to mrv8k.git on infradead.
> >>>
> >>> Dan
> >>>
> >>>
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2008-05-21 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 19:33 mrv8k: now gets scan results Dan Williams
2008-05-21  7:08 ` Markus Becker
2008-05-21 14:20   ` Dan Williams
2008-05-21 15:20     ` Markus Becker
2008-05-21 16:48       ` Dan Williams [this message]
2008-05-22  7:01         ` Markus Becker

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=1211388488.4232.5.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mab@comnets.uni-bremen.de \
    /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