From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <liml@rtr.ca>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Daniel J Blueman <daniel.blueman@gmail.com>,
Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ICH Intel PATA short cable override...
Date: Sun, 16 Sep 2007 03:58:07 -0400 [thread overview]
Message-ID: <46ECE20F.5020609@pobox.com> (raw)
In-Reply-To: <46E53554.1090604@rtr.ca>
Mark Lord wrote:
> Jeff Garzik wrote:
>> Mark Lord wrote:
>>> Ditto for selecting transfer modes.
>>
>>
>> Waiting on one thing AFAICS:
>>
>> ability to drain/idle all ports +
>> issue a command on one port +
>> resume normal parallel port operation
>>
>> SET FEATURES - XFER MODE is special in that it requires all sorts of
>> additional controller handling and careful cross-port synchronization.
>
> Absolutely.
>
> Also note that I'm *not* advocating HDIO_SET_PIO_MODE (and kin) here,
> but rather perhaps a sysfs option per-drive. It is needed, especially for
> custom/embedded systems, and I suppose we will get there eventually. :)
(did I reply to this already? I forget)
We don't need any sysfs options. Just normal SG_IO sending a SET
FEATURES - XFER MODE command to the desired device.
Currently, that [sub-]command is intentionally filtered out because of
the problems that would ensue.
Once the above EH mods are in place, we simply remove that filter, and
The Right Thing(tm) happens when you submit an ATA command via normal
methods. No need for new sysfs hooks or new ioctls or anything.
Jeff
prev parent reply other threads:[~2007-09-16 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 12:37 ICH Intel PATA short cable override Daniel J Blueman
2007-09-05 6:12 ` Andrey Panin
2007-09-06 0:42 ` Alan Cox
2007-09-06 2:20 ` Mark Lord
2007-09-06 7:59 ` Daniel J Blueman
2007-09-07 23:19 ` Jeff Garzik
2007-09-10 12:15 ` Mark Lord
2007-09-16 7:58 ` Jeff Garzik [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=46ECE20F.5020609@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daniel.blueman@gmail.com \
--cc=htejun@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).