From: Uwe Koziolek <uwe.koziolek@gmx.net>
To: Jim Paris <jim@jtan.com>
Cc: Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org, muthas@mit.edu, fragmede@gmail.com
Subject: Re: sata_sis only recognizing primary drive in 2.6.18
Date: Fri, 06 Oct 2006 12:57:07 +0200 [thread overview]
Message-ID: <45263683.408@gmx.net> (raw)
In-Reply-To: <20061006065816.GA5782@jim.sh>
Hi Jim,
the sata_sis is running without slave support in the versions from
kernel.org. That is ok if you are using
a SiS964 and 965L chip. The SiS 965, SiS180 and SiS966 needs a slave
support.
The attached patch against 2.6.18 should help.
feedback, log and output of lspci -vvxxx are welcome.
regards
Uwe Koziolek
> My friend has a motherboard with a SIS182 chipset (1039:0182), with
> four ports on the motherboard. BIOS sees it as two controllers,
> "IDE2" and "IDE3" with two ports apiece: "IDE2 Primary", "IDE2
> Secondary", etc.
>
> If we plug drives into both the IDE2 Primary and IDE2 Secondary ports,
> BIOS correctly sees and identifies both drives, and they're both
> visible to grub, but sata_sis only sees the primary drive. The second
> drive just never shows up; no errors are reported. This is with
--- a/drivers/scsi/sata_sis.c 2006-09-20 05:42:06.000000000 +0200
+++ b/drivers/scsi/sata_sis.c 2006-10-06 12:43:11.000000000 +0200
@@ -128,7 +128,7 @@
static struct ata_port_info sis_port_info = {
.sht = &sis_sht,
- .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY,
+ .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY | ATA_FLAG_SLAVE_POSS,
.pio_mask = 0x1f,
.mwdma_mask = 0x7,
.udma_mask = 0x7f,
next prev parent reply other threads:[~2006-10-06 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 6:58 sata_sis only recognizing primary drive in 2.6.18 Jim Paris
2006-10-06 10:57 ` Uwe Koziolek [this message]
2006-10-06 21:22 ` Jim Paris
2006-10-08 4:24 ` Tejun Heo
2006-10-21 21:04 ` Uwe Koziolek
2006-10-23 2:14 ` Tejun Heo
2006-10-23 8:45 ` Uwe Koziolek
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=45263683.408@gmx.net \
--to=uwe.koziolek@gmx.net \
--cc=fragmede@gmail.com \
--cc=htejun@gmail.com \
--cc=jim@jtan.com \
--cc=linux-ide@vger.kernel.org \
--cc=muthas@mit.edu \
/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).