From: Milton Miller <miltonm@bga•com>
To: Jeremy Kerr <jk@ozlabs•org>
Cc: linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH 3/20] [powerpc] Remove linux,pci-domain properties
Date: Tue, 4 Jul 2006 02:55:50 -0500 [thread overview]
Message-ID: <e53c7a64d7260d56983e22360cb5dd5a@bga.com> (raw)
On Tue Jul 4 16:47:18 EST 2006, Jeremy Kerr wrote:
> The linux,pci-domain property is no longer used by DLPAR/PCI Hotplug
> utilites, or LSVPD. This change removes it.
So if I have some device-tree path and want to find the sysfs node
for it or run something like lspci on it, I have to search all of
sysfs for a matching devspec file? (And this can change each boot.)
Without looking at the mentioned utilities, DLPAR and PCI Hotplug get a
location code, so I'm hoping that the pci slot name is identified by
that. Is lsvpd scanning? Or does it scan sysfs first and
/proc/device-tree secondarly?
milton
next reply other threads:[~2006-07-04 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 7:55 Milton Miller [this message]
2006-07-04 23:22 ` [PATCH 3/20] [powerpc] Remove linux,pci-domain properties Jeremy Kerr
-- strict thread matches above, loose matches on Subject: below --
2006-07-04 6:47 Jeremy Kerr
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=e53c7a64d7260d56983e22360cb5dd5a@bga.com \
--to=miltonm@bga$(echo .)com \
--cc=jk@ozlabs$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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