From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream-fixes] libata: implement libata.force_cbl parameter
Date: Wed, 09 Jan 2008 14:07:10 +0900 [thread overview]
Message-ID: <4784567E.1050600@gmail.com> (raw)
In-Reply-To: <20080109030502.54914b01@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>>> In which case we only need to be able to force UDMA33 or less ?
>> Cable detection goes wrong and 40c is detected as 80c. However, we got
>
> In which case we only (see first question). I don't see why we need to
> force anything but "max speed UDMA 33"
Ah.. yeah, right. I somehow missed the negation in the question.
There's no need to force 80c usually. The parameter might be as well
force_40c and only force 40c limit.
--
tejun
prev parent reply other threads:[~2008-01-09 5:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 13:19 [PATCH #upstream-fixes] libata: implement libata.force_cbl parameter Tejun Heo
2008-01-08 14:40 ` Alan Cox
2008-01-09 1:19 ` Tejun Heo
2008-01-09 1:37 ` Alan Cox
2008-01-09 1:46 ` Tejun Heo
2008-01-09 3:05 ` Alan Cox
2008-01-09 5:07 ` 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=4784567E.1050600@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--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).