From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.22-rc7 3/3] libata: pata_via CX700 quirks
Date: Thu, 05 Jul 2007 21:39:10 +0900 [thread overview]
Message-ID: <468CE66E.1070901@gmail.com> (raw)
In-Reply-To: <20070705133407.21977a92@the-village.bc.nu>
Alan Cox wrote:
> This makes no sense. If the SETXFER failed how did the device get into
> the mode it is in ? How will change down work ? Why does the old IDE
> driver work ?
IDE ignores SETXFER failure and for SATA devices SETXFER doesn't really
mean anything (unless it's bridged). In this case, IDE didn't seem to
be seeing SETXFER failures but the chip being quite weird (SETXFER
failure is associated with the specific device slot not the device
itself. it's probably a bridge problem.) and from the vendor it's from,
I thought whatever works is okay.
> I think this needs a lot more explanation
Feel free to re-open bug 8563. I'd be happy to help. :-)
Thanks.
--
tejun
next prev parent reply other threads:[~2007-07-05 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 4:31 [PATCH 2.6.22-rc7 1/3] libata: clean up horkage handling Tejun Heo
2007-07-05 4:35 ` [PATCH 2.6.22-rc7 2/3] libata: implement HORKAGE_SETXFER Tejun Heo
2007-07-05 4:39 ` [PATCH 2.6.22-rc7 3/3] libata: pata_via CX700 quirks Tejun Heo
2007-07-05 12:34 ` Alan Cox
2007-07-05 12:39 ` Tejun Heo [this message]
2007-07-05 12:27 ` [PATCH 2.6.22-rc7 2/3] libata: implement HORKAGE_SETXFER Alan Cox
2007-07-05 12:22 ` Tejun Heo
2007-07-05 12:38 ` Alan Cox
2007-07-05 12:28 ` [PATCH 2.6.22-rc7 1/3] libata: clean up horkage handling Alan Cox
2007-07-11 1:38 ` Jeff Garzik
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=468CE66E.1070901@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).