All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: David Brownell <david-b@pacbell.net>,
	rusty@rustcorp.com.au, kaos <kaos@ocs.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5.47bk2 + current modutils == broken hotplug
Date: Wed, 13 Nov 2002 13:07:11 -0800	[thread overview]
Message-ID: <20021113210711.GA7810@kroah.com> (raw)
In-Reply-To: <3DD2BD4C.7060502@pobox.com>

On Wed, Nov 13, 2002 at 03:59:56PM -0500, Jeff Garzik wrote:
> 
> (tangent warning!)
> Another long term idea I would eventually like to realize is the removal 
> of device ids from the C source code.  I don't care where they go -- 
> drivers/net/pci_ids [per directory ids?], drivers/net/3c59x.meta, 
> whereever.  Anywhere but the C source code.  It's quite silly to require 
> a driver rebuild just to add a single PCI id, and further, embedding 
> metadata in C source is rarely a good idea in the long term.  [reference 
> some of Linus's counter-arguments when it was mentioned that Donald 
> Becker's method of including Config.{in,help} data in C source might be 
> useful]

True, this would be nice, but how would the driver know to bind to a new
device, if it isn't rebuilt, and doesn't know about the new id that was
just added?  In the current scheme of driver matching to devices, I
don't see how this could be done.

Not to say I would not want to see this changed to allow this to happen,
I'm very tired of telling USB Palm users to get a new kernel version
just because a single device id was added which their new device has.

thanks,

greg k-h

  reply	other threads:[~2002-11-13 21:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 20:11 2.5.47bk2 + current modutils == broken hotplug David Brownell
2002-11-13 20:17 ` Greg KH
2002-11-13 20:40   ` David Brownell
2002-11-13 20:59 ` Jeff Garzik
2002-11-13 21:07   ` Greg KH [this message]
2002-11-13 22:45   ` David Brownell
2002-11-13 21:24 ` Jeff Garzik
2002-11-13 23:00   ` David Brownell
2002-11-14  3:46 ` Rusty Russell
2002-11-14  8:02   ` David Brownell
2002-11-14 10:01     ` Rusty Russell
2002-11-14 16:19       ` David Brownell
2002-11-14 17:42         ` Rusty Russell
2002-11-14 10:41   ` Gerd Knorr

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=20021113210711.GA7810@kroah.com \
    --to=greg@kroah.com \
    --cc=david-b@pacbell.net \
    --cc=jgarzik@pobox.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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.