From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: netdev@vger.kernel.org, Bcm43xx-dev@lists.berlios.de,
Daniel Drake <dsd@gentoo.org>
Subject: Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)
Date: Sun, 24 Sep 2006 18:47:35 +1000 [thread overview]
Message-ID: <1159087655.5924.28.camel@localhost.localdomain> (raw)
In-Reply-To: <200609241043.49772.mb@bu3sch.de>
On Sun, 2006-09-24 at 10:43 +0200, Michael Buesch wrote:
> On Sunday 24 September 2006 10:12, Benjamin Herrenschmidt wrote:
> > > > So what are the chances of getting this dscape stack merged, let's
> > > > say... for 2.6.19 ? Or we'll get yet another full release with barely
> > > > working wireless ?
> > >
> > > I don't think it's possible to happen for 2.6.19.
> > > Ealiest 2.6.20 but likely one or two releases later (me thinks).
> >
> > Which means we'll still have nothing near decent wireless for what ... 6
> > monthes min ?
>
> Well. Works For Me (tm).
> If there is some bug for you in current mainline, it needs to
> be fixed. But I can't fix something I am not able to reproduce and
> don't know what happens.
Well, there is definitely an issue with softmac going nuts, possibly
related to the chip stopping to transmit, I'm not certain at this point.
It -seems- to be better with Larry's latest patch (the big one) so we'll
see. Then, there is a problem when that happens an d your rmmod,
something kicks in after the driver is gone and crashes the kernel... If
I ever get into the situation where I suspect the rmmod will trigger
that again, I'll try to get into a text VT first so I can capture an
oops...
Ben.
next prev parent reply other threads:[~2006-09-24 8:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 2:43 bcm43xx driver unstable behaviour (and linux wireless is junk btw) Benjamin Herrenschmidt
[not found] ` <1159065798.5924.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24 3:45 ` Daniel Drake
[not found] ` <4515FF5D.4080602-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2006-09-24 6:18 ` Benjamin Herrenschmidt
[not found] ` <1159078683.5924.16.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24 8:05 ` Michael Buesch
[not found] ` <200609241005.02024.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-09-24 8:12 ` Benjamin Herrenschmidt
2006-09-24 8:43 ` Michael Buesch
2006-09-24 8:47 ` Benjamin Herrenschmidt [this message]
2006-09-24 15:34 ` Daniel Drake
2006-09-24 16:38 ` Michael Buesch
2006-09-25 9:02 ` Johannes Berg
2006-09-25 9:58 ` Benjamin Herrenschmidt
2006-09-25 10:00 ` Johannes Berg
2006-09-24 3:50 ` Dan Williams
[not found] ` <1159069857.2748.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24 6:13 ` Benjamin Herrenschmidt
2006-09-24 16:02 ` Dan Williams
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=1159087655.5924.28.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=dsd@gentoo.org \
--cc=mb@bu3sch.de \
--cc=netdev@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).