mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrick Mochel <mochel@osdl.org>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Greg KH <greg@kroah.com>, <jgarzik@pobox.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Displaying/modifying PCI device id tables via sysfs
Date: Tue, 4 Mar 2003 08:10:55 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0303040805000.992-100000@localhost.localdomain> (raw)
In-Reply-To: <1046753776.12441.92.camel@iguana>


> then there needs to be a simple way in sysfs to export an attribute
> hierarchy, beneath an object in the kobject hierarchy.  Right now it's
> assumed that each kobject can have multiple attributes, but all are at a
> single level.  Pat, is this hard to do?

It's 1 kobject == 1 sysfs directory. I recommend putting a kobject into 
the ID structure and registering it (by the PCI core) once the driver has 
been registered. Then, create files for each of the static IDs. 

When new IDs are added, I don't see why you need to differentiate between 
them in userspace. Couldn't you have e.g.:

/sys/bus/pci/drivers/3c59x/
`-- id
    |-- 0
    |-- 1
    `-- new_id

Then, when someone writes a new ID, have:

/sys/bus/pci/drivers/3c59x/
`-- id
    |-- 0
    |-- 1
    |-- 2
    `-- new_id

Internally, we of course need to treat them differently, but to the user, 
they're just IDs the driver supports..

	-pat


  reply	other threads:[~2003-03-04 14:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 17:57 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 [this message]
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=Pine.LNX.4.33.0303040805000.992-100000@localhost.localdomain \
    --to=mochel@osdl.org \
    --cc=Matt_Domsch@dell.com \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.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

all inboxes | Powered by JetHome®