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: Wed, 22 Aug 2001 01:50:02 +0100 [thread overview]
Message-ID: <20010822015002.F21643@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200108210544.XAA20603@puffin.external.hp.com>; from grundler@puffin.external.hp.com on Mon, Aug 20, 2001 at 11:44:20PM -0600
On Mon, Aug 20, 2001 at 11:44:20PM -0600, Grant Grundler wrote:
> Matthew Wilcox wrote:
> > On Thu, Aug 09, 2001 at 09:06:43AM -0600, Grant Grundler wrote:
> > > 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.
> >
> > If you could dig those out for me, that'd be great. I'm not familiar with
> > the layout of the HPUX source tree yet.
>
> That sounds too much like work. ;^)
> Raven PDC ERS is available from HP's firmware team website. (internal only).
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:
/*
* Loop thru the fixed_mod_table looking for a fixed module
* that is a child of Dino. Start at whatever index we just
* figured out from the hardware path of the last module found.
*/
for(; idx < nfixed_modules; idx++) {
entry = &fixed_mod_table[idx];
if (is_child_of(entry, parent_path))
{
#ifdef RDB
/*
* Ignore the serial port if RDB is using it.
*/
if ((entry != NULL) && (!(IS_RDB_DEVICE(entry->reg_set))))
#endif
return entry;
}
/* else not a child of dino - loop again */
}
/*
* If we exit the loop without returning anything, we must not
* have found the rs232 entry in the FMT. The rs232 is not to
* be used in this system, so return NULL
*/
return NULL;
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.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-08-22 0:50 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 [this message]
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=20010822015002.F21643@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 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.