From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] iotree thoughts
Date: Mon, 27 Aug 2001 20:20:36 +0100 [thread overview]
Message-ID: <20010827202036.E525@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200108250559.XAA24615@puffin.external.hp.com>; from grundler@puffin.external.hp.com on Fri, Aug 24, 2001 at 11:59:25PM -0600
On Fri, Aug 24, 2001 at 11:59:25PM -0600, Grant Grundler wrote:
> I was confused. The Dino built-in discovery doesn't make PDC calls.
OK, that clears that up :-)
> > 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 mean native buswalks. PCI buswalks are outside the scope of this topic.
> I'll assume your statement only refers to Dino built-ins and agree.
> FWIW, same is true for LASI devices.
Hmm. OK.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-08-27 19:20 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
2001-08-27 19:20 ` Matthew Wilcox [this message]
[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=20010827202036.E525@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=grundler@puffin.external.hp.com \
--cc=parisc-linux@parisc-linux.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