All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks
Date: Mon, 17 May 2010 16:14:45 +0000	[thread overview]
Message-ID: <20100517161445.GC28960@kroah.com> (raw)
In-Reply-To: <20100513134742.GB1768@piware.de>

On Mon, May 17, 2010 at 12:10:06PM +0100, Scott James Remnant wrote:
> On Sun, 2010-05-16 at 09:04 -0700, Greg KH wrote:
> 
> > On Sun, May 16, 2010 at 12:22:47PM +0100, Scott James Remnant wrote:
> > > I consider myself an active member of udev upstream, and I think we've
> > > taken a wrong turn with the design and implementation.
> > 
> > What specifically do you mean by this?
> > 
> > Is the current libudev not a good design for your needs?  What should it
> > be instead?
> > 
> Actually, quite the opposite!  I think that libudev is a great design.
> 
> I think that the wrong turn is that we rely on a massive "cold plug"
> phase during boot, and we rely on probing every single piece of hardware
> during that phase or on later insertion - whether or not anything on the
> system actually cares about the result.

But how would we "know" if we care about a device until we actually
figure out what the device is, and load the driver for it?

This cold-plug phase doesn't seem to take a very large amount of time
these days at all, so I don't see the real savings that would be
possible here.

Or am I missing something?

thanks,

greg k-h

      parent reply	other threads:[~2010-05-17 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 13:47 udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks rules Martin Pitt
2010-05-13 14:06 ` udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks Lennart Poettering
2010-05-16 11:22 ` Scott James Remnant
2010-05-16 16:04 ` Greg KH
2010-05-17 11:10 ` Scott James Remnant
2010-05-17 16:14 ` Greg KH [this message]

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=20100517161445.GC28960@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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 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.