linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Tejun Heo <htejun@gmail.com>, Alan Cox <alan@redhat.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 4/4] libata sata_qstor conversion to new error handling (EH).
Date: Wed, 07 Nov 2007 18:58:24 -0500	[thread overview]
Message-ID: <47325120.8020500@rtr.ca> (raw)
In-Reply-To: <20071107234514.GC26706@havoc.gtf.org>

Jeff Garzik wrote:
> On Wed, Nov 07, 2007 at 06:36:13PM -0500, Mark Lord wrote:
>> Mark Lord wrote:
>> ..
>>> and SG_IO WRITEs don't work.  That's really no different from
>>> the existing 2.6.24 version.  Regular I/O looks fine.
>> ...
>>
>> I should qualify that:  SG_IO *PIO* WRITEs don't work.
>> SG_IO PIO READs do work, and SG_IO DMA R/W both work.
> 
> multi-sector or single-sector PIO?
..

I was issuing single-sector PIO writes for one sector.
Something gets confused somewhere by that.

It really didn't seem worth tracking down further,
as regular kernel initiated I/O is fine (DMA though),
and this chip doesn't have much of a user/testing base.

I suppose it has to do with the initial DRQ interrupt
from a PIO WRITE --> the chip designers actually never
tested anything other than READ and IDENTIFY in register
PIO mode, so it could even be a chip issue.

The full-fledged qstor driver uses the chip's packet mode
for *everything*, including "PIO" R/W, so this is actually
the first time that direct PIO has even been attempted.
No surprise that it might fail.

If the chip were more commonly available/used, then I would
probably update sata_qstor to use packet mode for PIO as well.
But that's more effort than it's worth, really.

Cheers

  reply	other threads:[~2007-11-07 23:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 15:51 [PATCH 1/4] libata sata_qstor fix oops on rmmod Mark Lord
2007-11-07 15:52 ` [PATCH 2/4] libata sata_qstor nuke idle state Mark Lord
2007-11-08 18:14   ` Jeff Garzik
2007-11-07 15:53 ` [PATCH 3/4] libata sata_qstor workaround for spurious interrupts Mark Lord
2007-11-07 15:54 ` [PATCH 4/4] libata sata_qstor conversion to new error handling (EH) Mark Lord
2007-11-07 23:27   ` Jeff Garzik
2007-11-07 23:32     ` Mark Lord
2007-11-07 23:36       ` Mark Lord
2007-11-07 23:45         ` Jeff Garzik
2007-11-07 23:58           ` Mark Lord [this message]
2007-11-07 16:24 ` [PATCH 1/4] libata sata_qstor fix oops on rmmod Mark Lord
2007-11-08  2:30 ` Tejun Heo
2007-11-08 13:45 ` Mark Lord

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=47325120.8020500@rtr.ca \
    --to=liml@rtr.ca \
    --cc=alan@redhat.com \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --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).