From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
To: linux-mips@linux-mips.org
Subject: Using PCI bridges on sgi-ip32 [was: Re: Tests of 2.6.23-rc8 on SGI O2]
Date: Sun, 30 Sep 2007 10:34:36 +0200 [thread overview]
Message-ID: <1191141276.7160.44.camel@scarafaggio> (raw)
In-Reply-To: <1190973427.11251.17.camel@scarafaggio>
Il giorno ven, 28/09/2007 alle 11.57 +0200, Giuseppe Sacco ha scritto:
[...]
> About the first problem, once the machine booted, the lspci command stil
> does not list the available devices on the board. The only listed device
> is the PCI bridge.
>
> The relevant parts in syslog are these lines
>
> [...]
> Sep 29 00:42:49 sgi kernel: SCSI subsystem initialized
> Sep 29 00:42:49 sgi kernel: PCI: Bridge: 0000:00:03.0
> Sep 29 00:42:49 sgi kernel: IO window: disabled.
> Sep 29 00:42:49 sgi kernel: MEM window: disabled.
> Sep 29 00:42:49 sgi kernel: PREFETCH window: disabled.
> Sep 29 00:42:49 sgi kernel: PCI: Setting latency timer of device 0000:00:03.0 to 64
> Sep 29 00:42:49 sgi kernel: Time: MIPS clocksource has been installed.
> Sep 29 00:42:49 sgi kernel: NET: Registered protocol family 2
> [...]
The same board on i386, is recognised this way:
Sep 29 10:15:44 casa kernel: PCI: Bridge: 0000:00:09.0
Sep 29 10:15:44 casa kernel: IO window: d000-dfff
Sep 29 10:15:44 casa kernel: MEM window: fb700000-fbcfffff
Sep 29 10:15:44 casa kernel: PREFETCH window: disabled.
Sep 29 10:15:44 casa kernel: PCI: Setting latency timer of device 0000:00:01.0 to 6
And then, lspci, display all devices:
00:09.0 0604: 9710:9250 (rev 01)
00:09.0 PCI bridge: NetMos Technology Unknown device 9250 (rev 01)
01:08.0 0c03: 1033:0035 (rev 43)
01:08.0 USB Controller: NEC Corporation USB (rev 43)
01:08.1 0c03: 1033:0035 (rev 43)
01:08.1 USB Controller: NEC Corporation USB (rev 43)
01:08.2 0c03: 1033:00e0 (rev 04)
01:08.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
01:09.0 0c00: 11c1:5811 (rev 61)
01:09.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 61)
01:0a.0 0200: 10ec:8169 (rev 10)
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10
So, should I debug the PCI controller for ip32 (MACE)? What could be the
problem here? Should I report this kind of problem to a different
mailing list?
Thanks,
Giuseppe
next prev parent reply other threads:[~2007-09-30 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 9:57 Tests of 2.6.23-rc8 on SGI O2 Giuseppe Sacco
2007-09-28 10:33 ` Kaj-Michael Lang
2007-09-28 10:33 ` Kaj-Michael Lang
2007-09-30 8:34 ` Giuseppe Sacco [this message]
2007-10-01 15:05 ` Using PCI bridges on sgi-ip32 [was: Re: Tests of 2.6.23-rc8 on SGI O2] Maciej W. Rozycki
2007-10-02 1:01 ` Using PCI bridges on sgi-ip32: CONFIG_PCI_DEBUG Giuseppe Sacco
2007-10-02 11:39 ` Maciej W. Rozycki
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=1191141276.7160.44.camel@scarafaggio \
--to=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-mips@linux-mips.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