From: Benjamin Herrenschmidt <bh40@calva.net>
To: "Timothy A. Seufert" <tas@mindspring.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: PCI I/O address problems on B&W G3
Date: Thu, 24 Feb 2000 12:12:10 +0100 [thread overview]
Message-ID: <20000224121210.030675@mailhost.mipsys.com> (raw)
In-Reply-To: <v04220801b4daa2e26f84@[10.0.0.42]>
On Thu, Feb 24, 2000, Timothy A. Seufert <tas@mindspring.com> wrote:
>01:04.0 SCSI storage controller: Adaptec 7899A (rev 01)
> Subsystem: Adaptec: Unknown device f620
> Flags: bus master, 66Mhz, medium devsel, latency 16, IRQ 25
> BIST result: 00
> I/O ports at fe000000
> Memory at 80883000 (64-bit, non-prefetchable)
> Expansion ROM at 80900000 [disabled]
> Capabilities: [dc] Power Management version 2
>
>01:04.1 SCSI storage controller: Adaptec 7899A (rev 01)
> Subsystem: Adaptec: Unknown device f620
> Flags: bus master, 66Mhz, medium devsel, latency 16
> BIST result: 00
> I/O ports at fe000000
> Memory at 80882000 (64-bit, non-prefetchable)
> Expansion ROM at 808e0000 [disabled]
> Capabilities: [dc] Power Management version 2
Hum... Both cards are behind the PCI<->PCI bridges, and so they should
both have io addresses in the range fe001000 -> fe001fff
The fact that they are at fe000000 seems to indicate that the io base
address is 0 (and so was apparently _not_ assigned at all). Could you
break into OF, dev to those devices, and send me the output of
.properties ? (I need the content of the "reg" and "assigned addresses"
properties). I want to see what OF did with the cards exactly.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-24 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-24 9:43 PCI I/O address problems on B&W G3 Timothy A. Seufert
2000-02-24 11:12 ` Benjamin Herrenschmidt [this message]
2000-02-24 22:13 ` Timothy A. Seufert
2000-03-02 14:22 ` Need reports about PCI I/O conflicts Benjamin Herrenschmidt
2000-03-02 14:41 ` Gabriel Paubert
2000-03-03 5:13 ` Doug Ledford
2000-03-03 10:55 ` Benjamin Herrenschmidt
2000-03-17 7:01 ` Doug Ledford
2000-03-03 8:39 ` Timothy A. Seufert
2000-03-03 8:57 ` Doug Ledford
2000-03-03 10:01 ` Michel Lanners
2000-03-03 11:09 ` Benjamin Herrenschmidt
2000-03-04 10:16 ` PCI I/O address problems on B&W G3 Michel Lanners
2000-03-04 12:15 ` Timothy A. Seufert
2000-03-05 21:34 ` Geert Uytterhoeven
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=20000224121210.030675@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tas@mindspring.com \
/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.