From: Pavel Roskin <proski@gnu.org>
To: Fred Odendaal <freshshelf@rogers.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: at76_usb driver for WUSB11 v.26 wireless adapter doesn't work for kernels newer than 2.6.24.3-12.fc8
Date: Mon, 12 May 2008 07:11:05 -0400 [thread overview]
Message-ID: <1210590665.11848.15.camel@dv> (raw)
In-Reply-To: <4820FFCD.7060905@rogers.com>
On Tue, 2008-05-06 at 21:03 -0400, Fred Odendaal wrote:
> There is a bug report for this here:
> https://bugzilla.redhat.com/show_bug.cgi?id=438606
>
> Essentially, this driver used to work, but no longer does. The driver
> doesn't seem to be able to communicate signal level and link quality.
>
> If someone needs me to test a fix for this, or to try test loads I'm
> willing to help.
It's a known problem. There are some patches by Milan Plzik in
at76c503a-develop@lists.berlios.de that may help, but they need to be
reviewed and tested.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-05-12 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 1:03 at76_usb driver for WUSB11 v.26 wireless adapter doesn't work for kernels newer than 2.6.24.3-12.fc8 Fred Odendaal
2008-05-12 11:11 ` Pavel Roskin [this message]
2008-05-14 3:31 ` Fred Odendaal
2008-05-14 3:51 ` Pavel Roskin
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=1210590665.11848.15.camel@dv \
--to=proski@gnu.org \
--cc=freshshelf@rogers.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;
as well as URLs for NNTP newsgroup(s).