linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <greg@kroah.com>
Cc: Matt Domsch <Matt_Domsch@Dell.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	mochel@osdl.org
Subject: Re: Displaying/modifying PCI device id tables via sysfs
Date: 03 Mar 2003 20:02:54 +0000	[thread overview]
Message-ID: <1046721774.7314.6.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030303182553.GG16741@kroah.com>

On Mon, 2003-03-03 at 18:25, Greg KH wrote:
> > 2) Add new IDs at runtime and have the drivers probe for the new IDs.
> 
> Ick, no.  If a driver really wants to have a user provide new ids on the
> fly, they usually provide a module paramater to do this.  A number of
> the USB drivers do this already (and to be honest, they have caused
> nothing but trouble, as users use that option for new devices, that the
> driver can't control at all due to protocol or register location
> changes.)
> 
> In short, it's not a good idea to allow users to change these values on
> the fly, the driver author usually knows best here :)

I would strongly disagree with that statement. The majority of users run
kernels a little behind the times, and in may cases adding the PCI id is
just fine. It doens't want to be casual and uncontrolled but it does want
to be possible


  reply	other threads:[~2003-03-03 18:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 17:57 Displaying/modifying PCI device id tables via sysfs Matt Domsch
2003-03-03 18:25 ` Greg KH
2003-03-03 20:02   ` Alan Cox [this message]
2003-03-03 20:56   ` Matt Domsch
2003-03-04  0:31     ` Greg KH
2003-03-04  4:56       ` Matt Domsch
2003-03-04 14:10         ` Patrick Mochel
2003-03-04 20:22         ` Kai Germaschewski
2003-03-04 22:39           ` Alan Cox
2003-03-04 22:57           ` Jeff Garzik
2003-03-04  0:34     ` Jeff Garzik
2003-05-23  0:53   ` Rusty Russell
2003-05-24  0:37     ` Greg KH
2003-05-25  4:57       ` Rusty Russell
2003-05-23  2:27 Matt_Domsch

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=1046721774.7314.6.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Matt_Domsch@Dell.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.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;
as well as URLs for NNTP newsgroup(s).