From: Pavel Roskin <proski@gnu.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: bcm43xx-dev@lists.berlios.de,
Larry Finger <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>,
Michael Buesch <mb@bu3sch.de>
Subject: Re: RFT bcm43xx: Really _GOOD_ news
Date: Tue, 06 Feb 2007 17:29:13 -0500 [thread overview]
Message-ID: <1170800953.2613.17.camel@dv> (raw)
In-Reply-To: <200702061637.31756.gene.heskett@verizon.net>
On Tue, 2007-02-06 at 16:37 -0500, Gene Heskett wrote:
> That's great Larry. Now how long does it take to get this into a
> distro's
> update kernel queue? Or do I have to build a kernel for my lappy,
> currently on FC5?
Gene, I think it would be better for all of us if we don't bother Larry
with such questions and let him discover the secrets of the 802.11g
rates :)
I think that patch has a good chance to get into Fedora 7 from the
beginning. We may see it in Fedora Core 6 if it goes to Linux 2.6.20
and this patch goes to the 2.6.20.x branch before that.
I think the best we can do now would be to test the driver and report
the results. This would speed up the process of getting the patch to
the kernel. Yes, that means recompiling the kernel.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-02-06 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 20:34 RFT bcm43xx: Really _GOOD_ news Larry Finger
2007-02-06 21:37 ` Gene Heskett
2007-02-06 22:29 ` Pavel Roskin [this message]
2007-02-06 23:48 ` Gene Heskett
2007-02-07 4:40 ` Larry Finger
2007-02-07 8:03 ` Gene Heskett
2007-02-07 8:17 ` Pavel Roskin
2007-02-07 15:21 ` Daniel Gryniewicz
2007-02-07 15:42 ` Larry Finger
2007-02-06 22:18 ` Pavel Roskin
2007-02-06 22:27 ` Rafael J. Wysocki
2007-02-07 1:08 ` Larry Finger
2007-02-08 18:20 ` Jory A. Pratt
2007-02-09 0:05 ` John W. Linville
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=1170800953.2613.17.camel@dv \
--to=proski@gnu.org \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=gene.heskett@verizon.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.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;
as well as URLs for NNTP newsgroup(s).