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: Thu, 09 Aug 2001 09:06:43 -0600 [thread overview]
Message-ID: <200108091506.JAA13380@puffin.external.hp.com> (raw)
In-Reply-To: Message from Matthew Wilcox <willy@debian.org> of "Mon, 06 Aug 2001 02:05:17 BST." <20010806020517.A14978@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
>
> This is a summary and a design document for building an iotree in PA/Linux.
> Grant, Ryan, if I mis-remembered / misunderstood something, do shout.
Cool!
...
> In a related matter, the ABW will pick up serial ports (and other things)
> which aren't activated. Grant said there was a PDC call to determine
> whether a device is inactive -- I'm not sure which one that is yet.
Yes. AFAIK, LASI sub-devices are listed by PDC. For Dino HPUX makes
a special hvers PDC call. Need to look at the HPUX code or Raven PDC ERS.
>
> Here's my plan:
>
> * From setup_arch, call PDC to get a list of devices. Put them in a
> table (marked __init, will be freed later).
Why not start building a tree with "place holder" nodes directly?
Do we need the intermediate table because of memory issues?
ie build a "sparse" tree and have Native Bus walk fill in (or update
wrong) info for devices it finds.
> * In the badly-named gsc_init, or perhaps in pcibios_init, start the
> ABW at 0xFFF80000 -- this seems to be the defined location for the
> central bus.
My long term goal is to be able to build a kernel w/o CONFIG_PCI defined.
And renaming gsc_init to native_bus_init() sounds like a good idea.
> * Start creating the tree with devices that we find in the ABW.
> Each device which is a bus adapter / converter will do an ABW for its
> children, and add in any PDC-discovered devices in the table which are
> its immediate children. The add-in is done by copy, not by reference.
> * At some indeterminate time after this, the table of PDC-reported drivers
> gets freed along with all the other __init data & code.
>
> We'll have to be careful with CPU `drivers' since they will have stale
> pointers which must be updated. Perhaps this is where a ->remove method
> would come in handy; or perhaps we just magically make them cope with
> their ->probe function being called a second time on the same device
> (same HPA).
The latter sounds easier but more like a hack...maybe it's ok though.
thanks,
grant
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-08-09 15:08 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 [this message]
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
[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=200108091506.JAA13380@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.