From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Alan Cox <alan@redhat.com>
Subject: Re: ata_std_qc_defer not good enough for FIS-based switching ?
Date: Wed, 30 Apr 2008 10:02:46 -0400 [thread overview]
Message-ID: <48187C06.5090901@rtr.ca> (raw)
In-Reply-To: <48175664.5030702@rtr.ca>
Mark Lord wrote:
..
> For the first time ever, I can now *heavily* mix PIO commands
> with NCQ/non-NCQ DMA commands, to drives on an attached PM
> (well, two attached PMs even), and the thing doesn't croak.
> Woo-hoo!
>
>
> Time to batch up some patches for Jeff. But sadly, just in time
> to have missed his weekly visit to linux-ide. :)
..
Since I've just missed Jeff's weekly capture window (Mondays, it seems),
I'm holding off on the new patches while I work on getting the EH code
to fully/correctly handle (single/multiple) PMP error(s). Currently,
it just resets the port without doing full NCQ diagnosis for PMP ports,
and that has to change.
It's a bit complex for this chip (sata_mv) architecture, but doable.
If all goes well, there'll be a full patch series out for next Monday.
Cheers
prev parent reply other threads:[~2008-04-30 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 21:06 ata_std_qc_defer not good enough for FIS-based switching ? Mark Lord
2008-04-28 22:08 ` Mark Lord
2008-04-28 23:11 ` Tejun Heo
2008-04-28 23:42 ` Mark Lord
2008-04-29 1:18 ` Tejun Heo
2008-04-29 2:26 ` Mark Lord
2008-05-14 14:11 ` Tejun Heo
2008-05-14 14:45 ` Mark Lord
2008-05-14 14:53 ` Mark Lord
2008-05-14 15:50 ` Mark Lord
2008-05-14 15:59 ` Mark Lord
2008-05-15 7:12 ` Tejun Heo
2008-05-15 6:51 ` Tejun Heo
2008-04-29 17:09 ` Mark Lord
2008-04-29 17:17 ` Mark Lord
2008-04-30 9:38 ` Tejun Heo
2008-04-30 14:02 ` Mark Lord [this message]
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=48187C06.5090901@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@redhat.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.