All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Daniel Drake <dsd-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)
Date: Sun, 24 Sep 2006 16:18:03 +1000	[thread overview]
Message-ID: <1159078683.5924.16.camel@localhost.localdomain> (raw)
In-Reply-To: <4515FF5D.4080602-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>

On Sat, 2006-09-23 at 23:45 -0400, Daniel Drake wrote:
> Benjamin Herrenschmidt wrote:
> > Oh and I don't care about "it works in dscape stack" sort of crap I regulary get. I want something that
> > works with upstream kernels. That isn't that much to ask... or is it ?
> 
> wpa_supplicant triggers races in softmac relatively easily, which are 
> hard to fix properly. At least for me, motivation to work on this stuff 
> is low given the potentially impending merge of devicescape, and every 
> time I do spend some time investigating I just get even more frustrated 
> at how difficult WE is to implement *properly* for "non-hardmac" 
> drivers. We really have a need for a configuration system designed 
> around 802.11.
> 
> I agree, the stuff in mainline should be fixed, but at least personally 
> I am finding it harder and harder to justify working on softmac.

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 ?

Cheers,
Ben.

  parent reply	other threads:[~2006-09-24  6:18 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 [this message]
     [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
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=1159078683.5924.16.camel@localhost.localdomain \
    --to=benh-xvmvhmargas8u2djnn8i7kb+6bgklq7r@public.gmane.org \
    --cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=dsd-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.