From: Michael Buesch <mb@bu3sch.de>
To: "Ahmed Ammar" <b33fc0d3@gmail.com>
Cc: "Ivo Van Doorn" <ivdoorn@gmail.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
"Adam Baker" <linux@baker-net.org.uk>
Subject: Re: b43 (H/W 4306 Rev. 03)
Date: Tue, 4 Mar 2008 18:08:45 +0100 [thread overview]
Message-ID: <200803041808.45710.mb@bu3sch.de> (raw)
In-Reply-To: <84ac67910803040855x74d75412x424e220d61d459cb@mail.gmail.com>
On Tuesday 04 March 2008 17:55:07 Ahmed Ammar wrote:
> > Yes, rt61pci is known to be buggy in monitor mode, there seem
> > to be some inconsistencies regarding frame filtering inside the device
> > which causes rt61pci to incorrectly filter some frames out.
> >
> > It is an issue being looked into, and I believe Adam Baker already has
> > some patches he will send in for rt2x00 soon (First some other TX/RX
> > bugs needed to be fixed).
> >
>
> Ok, well on that note I have updated my sources with latest
> wireless-testing.git and rt2x00.git (as of today). I think I have a
> better dump. But very few packets fom b43 are ever seen (I can only
> guess the tx code for my revision is borked?). b43legacy seems to show
> full output, but i might be wrong. Attached.
I don't know what you are doing, but we certainly don't support
hacking b43 to work on legacy devices or hacking b43legacy
to work on new devices, which it seems you did, right?
If you have some actual problem with some unmodified driver
version, please show us the problem and we will address it.
--
Greetings Michael.
next prev parent reply other threads:[~2008-03-04 17:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 12:44 b43 (H/W 4306 Rev. 03) Ahmed Ammar
2008-02-21 16:31 ` John W. Linville
2008-02-21 18:08 ` Ahmed Ammar
[not found] ` <84ac67910802211007n55569d6j92dee1da198e9b1d@mail.gmail.com>
[not found] ` <20080221182615.GK3094@tuxdriver.com>
2008-02-21 20:04 ` Ahmed Ammar
2008-02-21 20:18 ` John W. Linville
2008-02-21 20:56 ` Ahmed Ammar
2008-02-22 15:14 ` Johannes Berg
2008-02-22 17:25 ` Ahmed Ammar
2008-02-23 6:18 ` Michael Buesch
2008-02-23 7:40 ` Ahmed Ammar
2008-02-23 12:18 ` Ahmed Ammar
2008-02-23 12:38 ` Johannes Berg
[not found] ` <84ac67910802230523u14646c4dg97f9ce40c21b9c26@mail.gmail.com>
[not found] ` <1203773250.13162.23.camel@johannes.berg>
[not found] ` <84ac67910802230559g73dafb0focbf62f4b9a6b3158@mail.gmail.com>
[not found] ` <1203776102.13162.27.camel@johannes.berg>
[not found] ` <84ac67910802230628q217542e4gc76bed8076af118f@mail.gmail.com>
[not found] ` <1203777414.13162.29.camel@johannes.berg>
[not found] ` <84ac67910802230925xb7750e8j561efaf951c50321@mail.gmail.com>
[not found] ` <1203794030.13162.39.camel@johannes.berg>
[not found] ` <84ac67910802231156t29724612me8adb74d05bfede8@mail.gmail.com>
2008-02-24 12:03 ` Ahmed Ammar
2008-02-24 12:36 ` Michael Buesch
2008-02-24 15:59 ` Ahmed Ammar
[not found] ` <1203933155.13162.56.camel@johannes.berg>
2008-02-25 12:07 ` Ahmed Ammar
2008-02-25 22:27 ` Ivo Van Doorn
2008-03-04 16:55 ` Ahmed Ammar
2008-03-04 17:08 ` Michael Buesch [this message]
2008-03-04 17:49 ` Ahmed Ammar
2008-03-04 18:15 ` Michael Buesch
2008-03-04 19:04 ` Ahmed Ammar
2008-03-04 19:08 ` Johannes Berg
2008-03-04 19:10 ` Michael Buesch
2008-03-04 19:17 ` Ahmed Ammar
2008-03-04 19:24 ` Michael Buesch
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=200803041808.45710.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=b33fc0d3@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@baker-net.org.uk \
--cc=linville@tuxdriver.com \
/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).