From: Uwe Koziolek <uwe.koziolek@gmx.net>
To: Tejun Heo <htejun@gmail.com>
Cc: Jim Paris <jim@jtan.com>,
linux-ide@vger.kernel.org, muthas@mit.edu, fragmede@gmail.com,
David Wang <touch@sis.com>
Subject: Re: sata_sis only recognizing primary drive in 2.6.18
Date: Sat, 21 Oct 2006 23:04:38 +0200 [thread overview]
Message-ID: <453A8B66.8080302@gmx.net> (raw)
In-Reply-To: <45287D85.1050302@gmail.com>
Hi,
I have tested the patch with separate port_info and a patch only adding
the flag ATA_FLAG_SLAVE_POSS for all controllers.
The result is allways the same. The second sata disk is allways
/dev/sdb. libata handles this correctly.
So i am not sure, that the separate port_info is really necessary. My
assumption is a ATA_FLAG_SLAVE_POSS
is sufficient for a correct handling.
If i am wrong, i will send a patch with separate port_info .
regards,
Uwe
Tejun Heo wrote:
> Hi!
>
> Uwe Koziolek wrote:
>> 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.
>
> Can you make separate port_info for controllers which support 4 ports
> and send a properly formatted patch?
>
> Thanks.
>
next prev parent reply other threads:[~2006-10-21 21:04 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
2006-10-06 21:22 ` Jim Paris
2006-10-08 4:24 ` Tejun Heo
2006-10-21 21:04 ` Uwe Koziolek [this message]
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=453A8B66.8080302@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 \
--cc=touch@sis.com \
/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).