[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071215214300.GC3096@tuxdriver.com>
Date: Sat, 15 Dec 2007 16:43:00 -0500
From: "John W. Linville" <linville@...driver.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Michael Buesch <mb@...sch.de>, Daniel Walker <dwalker@...sta.com>,
akpm@...ux-foundation.org, stefano.brivio@...imi.it,
Ray Lee <ray-lk@...rabbit.org>, matthias.kaehlcke@...il.com,
linux-kernel@...r.kernel.org, mbuesch@...enet.de, linux@...mer.net,
kjwinchester@...il.com, jonathan@...masters.org,
Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
bcm43xx-dev@...ts.berlios.de
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore
to mutex
On Sat, Dec 15, 2007 at 02:25:50AM +0100, Rafael J. Wysocki wrote:
> On Friday, 14 of December 2007, Michael Buesch wrote:
> > Either distributions have to install it automatically or people simply have
> > to read one or two lines of documentation. That's just what I wanted to say.
>
> It's not that simple. For example, regression testing will be a major PITA
> if one needs to switch back and forth from the new driver to the old one in the
> process.
Not really true -- a single system can easily have firmware installed
for b43, b43legacy, and bcm43xx at the same time and switch back and
forth between them.
Given a functioning udev configuration, the persistent naming even
works so that your device stays as 'eth1' when switching to and
fro bcm43xx. I really think everyone is overstating the problem.
John
--
John W. Linville
linville@...driver.com
--
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