Subject: Re: [RFC] Pushing device/driver binding decisions to userspace
From: Xavier Bestel <xavier.bestel@free.fr>
To: Ben Collins <ben.collins@ubuntu.com>
Cc: Nicholas Miell <nmiell@comcast.net>, linux-kernel@vger.kernel.org
In-Reply-To: <1163401845.5178.335.camel@gullible>
References: <1163374762.5178.285.camel@gullible>
	 <1163378981.2801.3.camel@entropy>  <1163381067.5178.301.camel@gullible>
	 <1163382425.2801.6.camel@entropy>  <1163395364.5178.327.camel@gullible>
	 <1163400313.2801.11.camel@entropy>  <1163401845.5178.335.camel@gullible>
Content-Type: text/plain
Date: Mon, 13 Nov 2006 11:13:52 +0100
Message-Id: <1163412832.24542.3.camel@frg-rhel40-em64t-03>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 774
Lines: 17

On Sun, 2006-11-12 at 23:10 -0800, Ben Collins wrote:
> Also the other case I gave where there is an alsa driver and a media
> driver for the same chipset, is by design. It can't be helped. There
> actually is a case for wanting one driver or the other in the case of
> the exact same hardware, depending on the users desire.

That one looks ugly. Probably the same driver should have a media
interface as well as an alsa interface (like alsa device are also oss
devices, no need to play evil rmmod/insmod tricks anymore).

	Xav

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/