From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Handle SATA bridges better
Date: Mon, 21 May 2007 18:12:26 +0200 [thread overview]
Message-ID: <4651C4EA.8070604@gmail.com> (raw)
In-Reply-To: <20070521171410.6920bd3b@the-village.bc.nu>
Alan Cox wrote:
>> I think host side detection should work as long as the bridge properly
>> releases CBLID after IDENTIFY. Drive side detection seems hopeless
>> unless the bridge modifies IDENTIFY data accordingly. Maybe the best we
>> can do here is allowing user to select transfer mode. :-(
>
> There are far too many systems with this kind of bridge to just dump it
> on the user. I'll have a think about doing it only if the controller
> hasn't decided the cable is 40 wire. That might work.
Okay.
>>>> Another problem is that there are still codes which interpret ap->cbl ==
>>>> ATA_CBL_SATA as SATA host port. They need to be fixed first before
>>>> using ap->cbl for the actual cable type.
>>> I thought we had those all sorted now. A grep shows there is nobody doing
>>> conditional checking off the ap->cbl cable in drivers/ata any more. They
>>> did in the past - which is this patch got held up - but no longer that I
>>> can see.
>> Hmm... I was looking at sata_scr_valid(). I think this needs to be
>> converted to ATA_FLAG_SATA test too.
>
> Possibly but PATA controllers don't have ->scr_read so its ok as is.
I'll submit a patch just in case. I think we used to do depend on that
for PATA/SATA combined controllers before new init model.
Thanks.
--
tejun
prev parent reply other threads:[~2007-05-21 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 14:13 [PATCH] libata: Handle SATA bridges better Alan Cox
2007-05-21 14:22 ` Tejun Heo
2007-05-21 14:47 ` Alan Cox
2007-05-21 14:52 ` Tejun Heo
2007-05-21 16:14 ` Alan Cox
2007-05-21 16:12 ` Tejun Heo [this message]
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=4651C4EA.8070604@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--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).