linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Gary Poppitz <poppitzg@iomega.com>, linux-ide@vger.kernel.org
Subject: Re: Issues with SIS 964 chipset on SATA
Date: Thu, 17 Feb 2005 09:38:30 +0100	[thread overview]
Message-ID: <20050217083825.GA8695@suse.de> (raw)
In-Reply-To: <4214551C.8030109@pobox.com>

On Thu, Feb 17 2005, Jeff Garzik wrote:
> Gary Poppitz wrote:
> >We tracked down a problem with the 964 chipset with a 0x180 ID code that 
> >may save someone on the list some time.
> >
> >The chip will only transfer multiples of 4 bytes. Anything else will 
> >cause it to hang.
> 
> 
> After further research, this is popping up on a number of chips (and 
> worked around in several vendor drivers).
> 
> 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.

Yeah we definitely need something like that. The optimal solution is to
make sure that all requests are fed through the bounce logic like fs
requests.

-- 
Jens Axboe


  reply	other threads:[~2005-02-17  8:38 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 [this message]
2005-02-17 13:26     ` Mark Lord
2005-02-17 18:36       ` Jeff Garzik
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=20050217083825.GA8695@suse.de \
    --to=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --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).