From: Michael Buesch <mb@bu3sch.de>
To: doug@nostar.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: Problems with b43 using BCM4306 r3
Date: Wed, 12 Dec 2007 01:22:31 +0100 [thread overview]
Message-ID: <200712120122.32119.mb@bu3sch.de> (raw)
In-Reply-To: <50633.68.40.216.125.1197418099.squirrel@webmail.nostar.net>
On Wednesday 12 December 2007 01:08:19 doug@nostar.net wrote:
> The problems only exist on the planet CCRMA
>
> http://ccrma.stanford.edu/planetccrma/software/
>
> low-lat patched kernel that I was using. I'm now running a stock Fedora
> 8 2.6.23.8-63.fc8 kernel and there dont appear to be anymore wifi
> problems. My reasons for using the ccrma kernel werent low latency
> performance so much as a working firewire stack (fedora 7 and above uses
> a new, broken stack) but I found another method.
Ah, well. The driver is not supposed to work with this kind of stuff.
--
Greetings Michael.
prev parent reply other threads:[~2007-12-12 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 20:33 Problems with b43 using BCM4306 r3 Doug McLain
2007-12-10 21:58 ` Michael Buesch
2007-12-12 0:08 ` doug
2007-12-12 0:22 ` Michael Buesch [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=200712120122.32119.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=doug@nostar.net \
--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).