public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ben Collins <ben.collins@ubuntu.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Pushing device/driver binding decisions to userspace
Date: Mon, 13 Nov 2006 13:51:26 -0500	[thread overview]
Message-ID: <1163443887.5313.27.camel@mindpipe> (raw)
In-Reply-To: <1163404727.15249.99.camel@laptopd505.fenrus.org>

On Mon, 2006-11-13 at 08:58 +0100, Arjan van de Ven wrote:
> Now; there is a second issue. If the choice for one or the other is
> consistent, we should consider fixing the kernel drivers to just not
> advertise the b0rked one.. (this assumes that both drivers are in the
> kernel and both are open source) 

Unfortunately it becomes political quickly.  For example the old OSS
i810_audio driver is still in the kernel even though the ALSA driver
supports more hardware and provides more functionality because some
people consider the ALSA driver bloated.

Lee


  reply	other threads:[~2006-11-13 18:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-12 23:39 [RFC] Pushing device/driver binding decisions to userspace Ben Collins
2006-11-13  0:49 ` Nicholas Miell
2006-11-13  1:24   ` Ben Collins
2006-11-13  1:47     ` Nicholas Miell
2006-11-13  5:22       ` Ben Collins
2006-11-13  6:45         ` Nicholas Miell
2006-11-13  7:10           ` Ben Collins
2006-11-13  9:45             ` Martin Mares
2006-11-13 10:13             ` Xavier Bestel
2006-11-23 10:29         ` Greg KH
2006-11-23 11:40           ` Kay Sievers
2006-11-24  3:59             ` Greg KH
2006-11-13  7:58 ` Arjan van de Ven
2006-11-13 18:51   ` Lee Revell [this message]
2006-11-13 20:18     ` Arjan van de Ven
2006-11-13 22:16       ` Jim Crilly
2006-11-13 22:59         ` Lee Revell
2006-11-13 23:22           ` Jim Crilly
2006-11-13 23:45             ` Lee Revell
2006-11-14  1:14               ` Jim Crilly
2006-11-14  7:32         ` Arjan van de Ven
2006-11-14 17:11           ` Jim Crilly

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=1163443887.5313.27.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=arjan@infradead.org \
    --cc=ben.collins@ubuntu.com \
    --cc=linux-kernel@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