Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Christoph Plattner <christoph.plattner@gmx.at>
Cc: Matthew Wilcox <willy@debian.org>,
	Ryan Bradetich <rbradetich@uswest.net>,
	"parisc-linux@lists.parisc-linux.org"
	<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Problem find devices on the E55 I/O interfaces
Date: Tue, 02 Jul 2002 18:48:54 -0600	[thread overview]
Message-ID: <20020703004854.74746486E@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Christoph Plattner <christoph.plattner@gmx.at> of "Wed, 03 Jul 2002 00:26:53 +0200." <3D2228AD.DC192B3B@gmx.at>

Christoph Plattner wrote:
> So, the devices below may be the HP-PB bus, as you mentioned.
> The resulting question: is this HP-PB bus now transperent ?

The bus converter is "transparent", not the bus.
ie everything we need to know about the secondary bus, we should be able
to read from the bus converter.

> Why are the devices not found ?
> 
> The point confusing me, is that the PDC boot monitor can display the
> hardware paths below the "56", but Linux calling PDC calls cannot see
> those devices, independent, if the device type is really know or only
> found as unknown.

Sounds like the bus walk code is looking at the wrong address
for walking the lower BC port.

I'll point Ryan at the IO ACD (ioacd_v096.pdf only seems to be
available inside HP *sigh*) and he can sort it out.

grant

      parent reply	other threads:[~2002-07-03  0:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 21:51 [parisc-linux] Problem find devices on the E55 I/O interfaces Christoph Plattner
2002-06-26 22:09 ` Grant Grundler
2002-07-02  3:17 ` Ryan Bradetich
2002-07-02 20:42   ` Christoph Plattner
2002-07-02 21:25     ` Grant Grundler
2002-07-02 21:55       ` Matthew Wilcox
2002-07-02 22:26         ` Christoph Plattner
2002-07-02 22:50           ` Matthew Wilcox
2002-07-03  0:48           ` 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=20020703004854.74746486E@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=christoph.plattner@gmx.at \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rbradetich@uswest.net \
    --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