From: John M Collins <jmc@xisl.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Query about SIS963 Bridges
Date: Mon, 24 Mar 2003 06:54:40 +0000 [thread overview]
Message-ID: <3E7EABB0.9010505@xisl.com> (raw)
In-Reply-To: 1048467041.10727.100.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
>On Sun, 2003-03-23 at 23:31, John M Collins wrote:
>
>
>>I've just got a new machine (2.5 GHz pentium lots of RAM and disk space)
>>which has one of these SIS963 Southbridge creatures and I get the
>>message on booting a 2.4.19ish sort of kernel.
>>
>>
>
>The SiS963 is currently a winputer.
>
>
>
>>Alas it's very clear that it isn't transparent and I can't get to half
>>of the PCI stuff - worst of all the built-in Ethernet and any Ethernet
>>card I plug in. It would seem that it isn't too transparent as the
>>reported IRQ and IOMEM assignments for the devices are all scrambled.
>>
>>
>
>One possibility is the system expects ACPI to untangle that mess and set
>up the bridge. You could certainly stuff realistic looking ranges into
>it, set IO/MEM and master and see what happens then
>
>What would be a useful starting point would be to see what
>lspci -vxx and lspci -vxx -H1 think
>
>
>
Here are the relevant bits out of "lspci -vxx"
00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device
0648 (rev 02)
Subsystem: Asustek Computer, Inc.: Unknown device 8086
Flags: bus master, medium devsel, latency 32
Memory at d0000000 (32-bit, non-prefetchable) [size=256M]
Capabilities: [c0] AGP version 3.0
00: 39 10 48 06 07 00 10 22 02 00 00 06 00 20 80 00
10: 00 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 86 80
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
(prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: cf000000-cfffffff
Prefetchable memory behind bridge: eff00000-febfffff
00: 39 10 01 00 07 00 00 00 00 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 e0 d0 00 20
20: 00 cf f0 cf f0 ef b0 fe 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 00
00:02.0 ISA bridge: Silicon Integrated Systems [SiS]: Unknown device
0963 (rev 04)
Flags: bus master, medium devsel, latency 0
00: 39 10 63 09 0f 00 00 02 04 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
and "lspci -vxx -H1"
00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device
0648 (rev 02)
Subsystem: Asustek Computer, Inc.: Unknown device 8086
Flags: bus master, medium devsel, latency 32
Memory at d0000000 (32-bit, non-prefetchable) {Only difference here}
Capabilities: [c0] AGP version 3.0
00: 39 10 48 06 07 00 10 22 02 00 00 06 00 20 80 00
10: 00 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 86 80
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
(prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: cf000000-cfffffff
Prefetchable memory behind bridge: eff00000-febfffff
00: 39 10 01 00 07 00 00 00 00 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 e0 d0 00 20
20: 00 cf f0 cf f0 ef b0 fe 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 00
00:02.0 ISA bridge: Silicon Integrated Systems [SiS]: Unknown device
0963 (rev 04)
Flags: bus master, medium devsel, latency 0
00: 39 10 63 09 0f 00 00 02 04 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(There's no difference in the output for the SIS963)
I'll have a look at APCI later today.
--
John Collins Xi Software Ltd www.xisl.com
next prev parent reply other threads:[~2003-03-24 6:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 23:31 Query about SIS963 Bridges John M Collins
2003-03-24 0:50 ` Alan Cox
2003-03-24 6:54 ` John M Collins [this message]
2003-03-24 14:09 ` Alan Cox
2003-03-24 13:20 ` John M Collins
2003-03-24 13:49 ` John M Collins
2003-03-30 22:00 ` John M Collins
2003-03-31 23:23 ` jmduthie
2003-04-01 14:44 ` Alan Cox
2003-04-02 3:18 ` John Wendel
2003-04-02 10:51 ` Alan Cox
2003-04-02 6:00 ` john
[not found] <20030323234008$0084@gated-at.bofh.it>
2003-03-24 0:55 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-04-01 1:38 Hemmann, Volker Armin
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=3E7EABB0.9010505@xisl.com \
--to=jmc@xisl.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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.