From: "Tobias Müller" <Tobias_Mueller@twam.info>
To: linux-ide@vger.kernel.org
Subject: Re: 40-wire cable detected when directly connected
Date: Sat, 12 Jan 2008 17:22:49 +0100 [thread overview]
Message-ID: <4788E959.1030103@twam.info> (raw)
In-Reply-To: <200801121709.26920.bzolnier@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2305 bytes --]
Hi
Bartlomiej Zolnierkiewicz schrieb:
> As a workaround you can try using IDE subsystem siimage driver and pass
> "idex=ata66" option or modify Tejun's patch to also override device side
> cable detection by replacing ATA_CBL_PATA80 with ATA_CBL_PATA40_SHORT.
I'll try this.
> Could you send the output of 'lspci -vvv -xxx' command?
03:04.0 RAID bus controller: Silicon Image, Inc. PCI0680 Ultra ATA-133
Host Controller (rev 02)
Subsystem: Silicon Image, Inc. Winic W-680 (Silicon Image 680
based)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 4 bytes
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at df00 [size=8]
Region 1: I/O ports at de00 [size=4]
Region 2: I/O ports at dd00 [size=8]
Region 3: I/O ports at dc00 [size=4]
Region 4: I/O ports at db00 [size=16]
Region 5: Memory at fdcff000 (32-bit, non-prefetchable) [size=256]
[virtual] Expansion ROM at fdb00000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Kernel driver in use: pata_sil680
00: 95 10 80 06 07 00 90 02 02 00 04 01 01 40 00 00
10: 01 df 00 00 01 de 00 00 01 dd 00 00 01 dc 00 00
20: 01 db 00 00 00 f0 cf fd 00 00 00 00 95 10 80 36
30: 00 00 00 00 60 00 00 00 00 00 00 00 0f 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 01 00 22 06 00 40 00 64 00 00 00 00 00 00 00 00
70: 08 00 00 00 00 60 1f 7c 08 00 00 00 00 30 1f 7c
80: 03 00 00 00 02 00 00 00 00 00 11 00 09 19 22 51
90: 00 fe 00 0d ff ff ff 3b 00 00 00 19 00 00 00 00
a0: 01 62 c1 10 c1 10 8a 32 c1 10 92 43 07 40 09 40
b0: 01 62 c1 10 c1 10 8a 32 c1 10 92 43 00 40 09 40
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 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
Regards
Tobias
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3389 bytes --]
next prev parent reply other threads:[~2008-01-12 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 17:24 40-wire cable detected when directly connected Tobias Müller
2008-01-11 3:53 ` Tejun Heo
2008-01-11 11:47 ` Tobias Müller
2008-01-12 3:26 ` Tejun Heo
2008-01-12 13:40 ` Tobias Müller
2008-01-13 6:06 ` Tejun Heo
2008-01-12 14:38 ` Bartlomiej Zolnierkiewicz
2008-01-12 14:29 ` Tobias Müller
2008-01-12 16:09 ` Bartlomiej Zolnierkiewicz
2008-01-12 16:14 ` Bartlomiej Zolnierkiewicz
2008-01-12 16:22 ` Tobias Müller [this message]
2008-01-12 17:23 ` Tobias Müller
2008-01-11 13:56 ` Alan Cox
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=4788E959.1030103@twam.info \
--to=tobias_mueller@twam.info \
--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).