linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Matt Domsch <Matt_Domsch@dell.com>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: Displaying/modifying PCI device id tables via sysfs
Date: Tue, 4 Mar 2003 17:57:00 -0500	[thread overview]
Message-ID: <20030304225659.GB7120@gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303041414270.23375-100000@chaos.physics.uiowa.edu>

On Tue, Mar 04, 2003 at 02:22:13PM -0600, Kai Germaschewski wrote:
> On 3 Mar 2003, Matt Domsch wrote:
> 
> > /sys
> > `-- bus
> >     `-- pci
> >         `-- drivers
> >             `-- 3c59x
> >                 |-- dynamic_id_0  (these are simple DRIVER_ATTRs)
> >                 |-- dynamic_id_1
> >                 |-- dynamic_id_2
> >                 `-- new_id
> > 
> > Where dynamic_id_[012] are new dynamic entries, created by writing
> > values into new_id.  Both file types would be of the format (analogous
> > to pci_show_resources):
> > echo "0x0000 0x0000 0x0000 0x0000 0x0000 0x0000" > new_id
> > with fields being vendor, device, subvendor, subdevice, class,
> > class_mask.
> 
> I dont' think what you actually want is changing the id table - after all, 
> it's only walked when registering the driver (+ hotplug).
> 
> What you really want is a way to call the drivers' probe routine for a 
> device which isn't in its tables.
> 
> So why not simply
> 
> echo "0x0000 0x0000 0x0000 0x0000 0x0000 0x0000" > .../3c59x/probe

I think there is value in decoupling the two operations:

	echo "0x0000 0x0000 0x0000 0x0000 0x0000 0x0000" > .../3c59x/table
	echo 1 > .../3c59x/probe_it

Because you want the id table additions to be persistant in the face of
cardbus unplug/replug, and for the case where cardbus card may not be
present yet, but {will,may} be soon.

	Jeff




  parent reply	other threads:[~2003-03-04 22:46 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
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 [this message]
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=20030304225659.GB7120@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=Matt_Domsch@dell.com \
    --cc=greg@kroah.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --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).