From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jens Axboe <axboe@suse.de>, Gary Poppitz <poppitzg@iomega.com>,
linux-ide@vger.kernel.org
Subject: Re: Issues with SIS 964 chipset on SATA
Date: Thu, 17 Feb 2005 13:36:41 -0500 [thread overview]
Message-ID: <4214E439.6040201@pobox.com> (raw)
In-Reply-To: <42149B6F.1000502@rtr.ca>
Mark Lord wrote:
> Jens Axboe wrote:
>
>>
>>> It looks like I will need to do a workaround for all SATA ATAPI
>>> devices: if the transfer is not a multiple of 4 bytes, pad it with an
>>> DMA 1-3 byte DMA segment.
>
>
> Yup, that requirement has existed on most of the hardware
> I've done drivers for, both SATA and a lot of PATA chips too.
PATA too? Interesting...
Jeff
next prev parent reply other threads:[~2005-02-17 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 19:02 Issues with SIS 964 chipset on SATA Gary Poppitz
2005-02-07 21:44 ` Jeff Garzik
2005-02-17 8:26 ` Jeff Garzik
2005-02-17 8:38 ` Jens Axboe
2005-02-17 13:26 ` Mark Lord
2005-02-17 18:36 ` Jeff Garzik [this message]
2005-02-17 18:38 ` Jeff Garzik
2005-02-17 8:37 ` ATAPI issues (was Re: Issues with SIS 964 chipset on SATA) 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=4214E439.6040201@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=poppitzg@iomega.com \
/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).