From: Grant Grundler <grundler@puffin.external.hp.com>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] iotree thoughts
Date: Fri, 24 Aug 2001 23:59:25 -0600 [thread overview]
Message-ID: <200108250559.XAA24615@puffin.external.hp.com> (raw)
In-Reply-To: Message from Matthew Wilcox <willy@debian.org> of "Wed, 22 Aug 2001 01:50:02 BST." <20010822015002.F21643@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> I looked through the Raven ERS, it wasn't too helpful. I managed to find
> the Dino driver in the HPUX source tree.... it doesn't seem to make the
> call itself, but instead:
[...]
I was confused. The Dino built-in discovery doesn't make PDC calls.
HPUX 11.01 (9905 release?) does make PDC calls in the boot initialization
sequence. IIRC, This associates PCI device numbers with slot numbers
printed on the back of the machine. Useful for defective FRU ("Field
Replacable Unit") isolation/error reporting. AFAIK, This only works
for platforms with bridge-mode Dino - ie B1XX/CXXX workstations.
(Calls are appended for interested folks).
...
> So it seems to me that we shouldn't do bus-walks underneath Dino, but
> rely on PDC telling us about the device if it's attached.
Uhm, "underneath" is ambiguous since both built-ins and PCI devices
are heirarchially below "dino" (iotree view - not HW view).
We need to do PCI bus walks for PCI devices.
I'll assume your statement only refers to Dino built-ins and agree.
FWIW, same is true for LASI devices.
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
/*
* Get physical platform information
*/
status = hversion_pdc_call(
3,(u_int)PDC_ARG2_IS_RADDR, 10, (ulong_t)PDC_PCI,
(ulong_t)PDC_PCI_GET_IFACE_INFO, (ulong_t)&(DINO(this)->ifinfo)
,
(ulong_t)this->base_addr,(ulong_t)0,(ulong_t)0,(ulong_t)0,
(ulong_t)0,(ulong_t)0,(ulong_t)0);
...
/*
* Total number of devices to get "slot info" for - all the slots plus
* all the built-ins
*/
num_devs = DINO(this)->ifinfo.num_slots + DINO(this)->ifinfo.num_built_ins;
...
for (slot_idx = 0; slot_idx < num_devs; slot_idx++) {
ulong_t slot_path[32];
status = hversion_pdc_call(
4, (u_int)PDC_ARG2_IS_RADDR, 32, (ulong_t)PDC_PCI,
(ulong_t)PDC_PCI_GET_SLOT_INFO, (ulong_t) slot_path,
(ulong_t)this->base_addr, (ulong_t)slot_idx,(ulong_t)0,
(ulong_t)0, (ulong_t)0, (ulong_t)0, (ulong_t)0);
...
next prev parent reply other threads:[~2001-08-25 6:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 1:05 [parisc-linux] iotree thoughts Matthew Wilcox
2001-08-09 15:06 ` Grant Grundler
2001-08-10 0:37 ` [parisc-linux] Installation Gururaj Ananthateerta
2001-08-10 2:04 ` Thomas Marteau
2001-08-14 16:02 ` [parisc-linux] iotree thoughts Matthew Wilcox
2001-08-21 5:44 ` Grant Grundler
2001-08-21 7:09 ` Matthew Wilcox
2001-08-21 7:53 ` Grant Grundler
2001-08-21 21:12 ` Helge Deller
2001-08-21 14:12 ` Alan Cox
2001-08-22 0:50 ` Matthew Wilcox
2001-08-25 5:59 ` Grant Grundler [this message]
2001-08-27 19:20 ` Matthew Wilcox
[not found] <200108212111.PAA28876@puffin.external.hp.com>
2001-08-23 6:18 ` Grant Grundler
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=200108250559.XAA24615@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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