From: Dave Boutcher <sleddog@us.ibm.com>
To: Greg KH <greg@kroah.com>, Ryan Arnold <rsa@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, boutcher@us.ibm.com,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: new driver (hvcs) review request and sysfs questions
Date: Tue, 24 Feb 2004 21:12:09 -0600 [thread overview]
Message-ID: <opr3woijnwl6e53g@us.ibm.com> (raw)
In-Reply-To: <20040225012845.GA3909@kroah.com>
On Tue, 24 Feb 2004 17:28:45 -0800, Greg KH <greg@kroah.com> wrote:
> On Tue, Feb 24, 2004 at 06:00:26PM -0600, Ryan Arnold wrote:
>> An example of the vio bus's "devices" sysfs directory is shown below.
>>
>> Pow5:/sys/bus/vio/devices # ls
>> . l-lan@3000000c l-lan@30000010 vty-server@30000004
>> .. l-lan@3000000d rtc@4001 vty@30000000
>> IBM,sp@4000 l-lan@3000000e v-scsi@30000002
>> l-lan@3000000b l-lan@3000000f vty-server@30000003
>
> At first glance, why are you using text strings as part of your bus ids?
> Bus ids must be unique, so it looks like you can do this by just using
> the number after the '@' character, right?
That naming convention (e.g. l-lan@3000000c) is what is defined in the
IEEE Standard for Boot (Initialization Configuration) Firmware spec, and
what gets presented by Open Firmware. It is what has been used in things
like /proc/device-tree on the Power platforms forever, and thus was
carried over into the sysfs definitions.
It is also true that it is unlike the representation of most other things
in sysfs, so perhaps this is the time to change before it gets too baked
into things.
Dave B
next prev parent reply other threads:[~2004-02-25 3:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 0:00 new driver (hvcs) review request and sysfs questions Ryan Arnold
2004-02-25 1:28 ` Greg KH
2004-02-25 3:12 ` Dave Boutcher [this message]
2004-02-25 4:22 ` Greg KH
2004-02-25 11:34 ` Benjamin Herrenschmidt
2004-02-25 15:46 ` device/kobject naming Hollis Blanchard
2004-02-26 0:18 ` Greg KH
2004-02-26 21:31 ` Hollis Blanchard
2004-02-25 16:22 ` new driver (hvcs) review request and sysfs questions Dave Hansen
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=opr3woijnwl6e53g@us.ibm.com \
--to=sleddog@us.ibm.com \
--cc=boutcher@us.ibm.com \
--cc=greg@kroah.com \
--cc=hollisb@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rsa@us.ibm.com \
/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