From: Wes Newell <w.newell@verizon.net>
To: "linux.ide" <linux-ide@vger.kernel.org>
Subject: Pata support for SIS180
Date: Sat, 11 Jun 2005 08:35:45 -0500 [thread overview]
Message-ID: <42AAE8B1.8080607@verizon.net> (raw)
Can anyone tell me if/how one could add device support for the sis180
chipset pata ports to the sis5513 module? I've tried adding this as
others have said it works for the 965 southbridge,
if ((trueid == 0x5518) || (trueid == 0x0180)) {
but it stll doesn't see a real sis180 on a Jetway S755MAX MB.
Here's the device info.
00:0c.0 RAID bus controller: Silicon Integrated Systems [SiS] RAID bus
controller 180 SATA/PATA [SiS] (prog-if 85)
Subsystem: Silicon Integrated Systems [SiS] RAID bus controller
180 SATA/PATA [SiS]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin A routed to IRQ 19
Region 0: I/O ports at dc00 [size=8]
Region 1: I/O ports at e000 [size=4]
Region 2: I/O ports at e400 [size=8]
Region 3: I/O ports at e800 [size=4]
Region 4: I/O ports at ec00 [size=16]
Region 5: I/O ports at <unassigned>
Expansion ROM at <unassigned> [disabled] [size=64K]
00:0c.0 RAID bus controller: Silicon Integrated Systems [SiS] RAID bus
controller 180 SATA/PATA [SiS]
00: 39 10 80 01 07 04 20 02 00 85 04 01 00 80 00 00
10: 01 dc 00 00 01 e0 00 00 01 e4 00 00 01 e8 00 00
20: 01 ec 00 00 01 00 00 00 00 00 00 00 39 10 80 01
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00
40: 56 23 06 04 56 23 06 04 00 00 00 00 00 00 00 00
50: 82 20 82 00 2a 96 00 03 00 00 00 00 00 00 00 00
60: ff aa 00 00 d9 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: bd 33 72 40 bd 33 72 40 00 00 00 00 00 00 00 00
90: 34 00 00 03 6f 05 00 00 cc 04 0c 10 c0 05 c0 05
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 01 00 18 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 01 00 18 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
My server http://wesnewell.no-ip.com/cpu.php
Verizon server http://mysite.verizon.net/res0exft/cpu.htm
next reply other threads:[~2005-06-11 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 13:35 Wes Newell [this message]
2005-06-12 20:31 ` Pata support for SIS180 Uwe Koziolek
2005-06-12 21:50 ` Wes Newell
2005-06-13 3:34 ` Jeff Garzik
2005-06-13 6:34 ` Wes Newell
2005-06-13 17:19 ` Wes Newell
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=42AAE8B1.8080607@verizon.net \
--to=w.newell@verizon.net \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).