Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] RFC: I/O tree design
Date: Mon, 05 Feb 2001 10:22:11 -0800	[thread overview]
Message-ID: <200102051822.KAA02233@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Sat, 03 Feb 2001 00:17:52 PST." <3A7BB0A0.D478911A@uswest.net>

Ryan Bradetich wrote:
> Here is my proposal for phase 2 of the I/O tree for parisc-linux.

Overall, this sounds ok to me.
Just a nit WRT to terminology.

...
> This proposal also calls for a special "root" node at
> index 0 of the device array.  The root node is the starting
> point of the I/O tree and does not have a parent, nor any
> siblings.  The root node has a single child pointer which
> points to the head of the sibling list for the system
> bus.

I would call the "root" node the "parent psuedo-bus adapter"
(or something like that) of the central bus. It's special because
it generally won't represent a physical PA I/O device. But it does
contain a "lower port address" - the fixed PA IO address your
previous bus-walk patch started with.

The idea here is you can pass "hp_device *" to your PA bus walk code
and not have seperate code for central bus or GSC bus. The bus walk
code could use the "lower port address" as a new starting point to
poke around.


thanks,
grant

Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253

      parent reply	other threads:[~2001-02-05 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-03  7:17 [parisc-linux] RFC: I/O tree design Ryan Bradetich
2001-02-03 17:57 ` Matthew Wilcox
2001-02-05  4:04   ` Ryan Bradetich
2001-02-05 18:34   ` Grant Grundler
2001-02-06  6:02     ` Matthew Wilcox
2001-02-06  7:10       ` Grant Grundler
2001-02-06  8:07         ` Grant Grundler
2001-02-05 18:22 ` Grant Grundler [this message]

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=200102051822.KAA02233@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=rbradetich@uswest.net \
    /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