From: Ivo van Doorn <ivdoorn@gmail.com>
To: rt2400-devel@lists.sourceforge.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: [rt2x00] rt2800 progress update
Date: Mon, 18 Aug 2008 16:53:26 +0200 [thread overview]
Message-ID: <200808181653.27080.IvDoorn@gmail.com> (raw)
In-Reply-To: <200808181526.16974.IvDoorn@gmail.com>
On Monday 18 August 2008, Ivo van Doorn wrote:
> Hi,
>
> Just a small information mail regarding the current status of the rt2800 drivers,
> The initial schedule was that last week or at the latest this week, the initial
> version of the rt2800 drivers would be released.
>
> But as you might have noticed, this has not happened, which means the project
> is behind schedule. The current status is that rt2800usb is capable of
> receiving frames (only when using the legacy driver first), and rt2800pci isn't
> capable of anything yet.
>
> I am currently putting all focus on rt2800usb because the queue management
> is the easiest for that driver, and having that driver working will help in debugging
> rt2800pci later.
>
> The fact that rt2800usb is capable of receiving frames after the legacy driver
> has been loaded first, means that I am missing one or two instructions which
> must be send to the hardware before it will kick in. Unfortunately I have made
> little progress in tracking that required instruction. :(
Well found it. Apparently the frames are only received when the BSSID is
written to the device. I currently get only 1 scan result now (the BSSID written
to the register), but in monitor mode I can see 2 AP's and a bunch of data going
through the air.
Well this is at least a start in the right direction, hopefully TX will work soon
as well.
Ivo
prev parent reply other threads:[~2008-08-18 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 13:26 [rt2x00] rt2800 progress update Ivo van Doorn
2008-08-18 14:53 ` Ivo van Doorn [this message]
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=200808181653.27080.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.