From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jeff Garzik <jeff@garzik.org>,
Mario Schwalbe <schwalbe@inf.tu-dresden.de>,
linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ide: Fix ata_id_has_dword_io to return DWORD I/O support properly
Date: Fri, 19 Dec 2008 14:34:37 +0300 [thread overview]
Message-ID: <494B86CD.4060305@ru.mvista.com> (raw)
In-Reply-To: <494B8617.3020808@ru.mvista.com>
Hello, I just wrote:
>> I remain unconvinced we should be looking at it anywhere except specific
>> pure ISA cycle pass through hardware and thus it belongs as a helper for
>>
>
> I'm still not getting how drive can support or not support "DWORD
> I/O" -- you certainly can't have 32-bit I/O cycle on ISA (only on
> EISA) and you certainly cannot translate 32-bit cycle to the ATA bus.
> I remember I had some hypotheses before but they turned out to be
> inconsistent.
If only two back-to-back I/O cycles weren't providing enough recovery
time...
MBR, Sergei
next prev parent reply other threads:[~2008-12-19 11:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <494A5BBF.8000807@inf.tu-dresden.de>
2008-12-18 17:08 ` [PATCH] ide: Fix ata_id_has_dword_io to return DWORD I/O support properly Jeff Garzik
2008-12-18 17:24 ` Sergei Shtylyov
2008-12-18 20:42 ` Bartlomiej Zolnierkiewicz
2008-12-18 22:40 ` Alan Cox
2008-12-18 23:13 ` Bartlomiej Zolnierkiewicz
2008-12-19 10:50 ` Alan Cox
2008-12-19 19:30 ` Bartlomiej Zolnierkiewicz
2008-12-20 0:10 ` Alan Cox
2008-12-19 11:31 ` Sergei Shtylyov
2008-12-19 11:34 ` Sergei Shtylyov [this message]
2008-12-18 18:10 ` Alan Cox
2008-12-20 1:58 ` Robert Hancock
2008-12-20 13:25 ` Sergei Shtylyov
2008-12-22 20:16 ` Sergei Shtylyov
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=494B86CD.4060305@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwalbe@inf.tu-dresden.de \
/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).