From: Jeff Garzik <jgarzik@pobox.com>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>
Cc: Carlos Pardo <Carlos.Pardo@siliconimage.com>
Subject: mod15write
Date: Sat, 03 Dec 2005 14:05:44 -0500 [thread overview]
Message-ID: <4391EC88.9010604@pobox.com> (raw)
IIRC, the specific mod15write problem is that we don't want the final
Data FIS generated by the 3112 to end on a pure 8K or 7.5K boundary
(Carlos, check me here...)
Thus, a potential solution might be to do full speed read commands, and
split write commands into two commands: one write with the majority of
the transfer, and a second write with the remainder.
Jeff
next reply other threads:[~2005-12-03 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 19:05 Jeff Garzik [this message]
2005-12-05 15:04 ` mod15write Tejun Heo
2005-12-05 18:24 ` mod15write 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=4391EC88.9010604@pobox.com \
--to=jgarzik@pobox.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=htejun@gmail.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).