[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070304164525.349f9589.akpm@linux-foundation.org>
Date: Sun, 4 Mar 2007 16:45:25 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Matt Mackall <mpm@...enic.com>, Adrian Bunk <bunk@...sta.de>
Cc: Johannes Berg <johannes@...solutions.net>,
Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, yi.zhu@...el.com, jketreno@...ux.intel.com,
linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: Recent wireless breakage (ipw2200, iwconfig, NetworkManager)
On Sun, 4 Mar 2007 18:25:50 -0600 Matt Mackall <mpm@...enic.com> wrote:
> On Mon, Mar 05, 2007 at 12:39:24AM +0100, Johannes Berg wrote:
> > [adding linux-wireless to CC]
> >
> > On Sun, 2007-03-04 at 16:08 -0600, Matt Mackall wrote:
> > > Recent kernels are having troubles with wireless for me. Two seemingly
> > > related problems:
> >
> > I don't think they are related actually.
> >
> > > a) NetworkManager seems oblivious to the existence of my IPW2200
> >
> > This is due to the recent sysfs restructuring I think. IIRC the fix is
> > to upgrade hal to a current git version.
>
> If that's the cause, the fix is to back out whatever was done to break
> userspace. Breaking userspace is not ok. Upgrading from 2.6.x to
> 2.6.x+1 should not entail replacing substantial parts of userspace,
> especially with NOT-EVEN-FRAKKING-RELEASED-YET CODE.
yep. Adrian, I think we should track this as a blocking regression, at
least until we've fully understood the implications and had the usual
arguments.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists