From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, linux-ide@vger.kernel.org, htejun@gmail.com
Subject: [PATCHSET] sata_nv: convert to new EH and add hotplug support, take 2
Date: Sat, 17 Jun 2006 15:49:55 +0900 [thread overview]
Message-ID: <11505269953650-git-send-email-htejun@gmail.com> (raw)
In-Reply-To:
Hello,
This is the second take of convert-sata_nv-to-new-EH patchset.
Changes from the last take[1] are...
* controllers are differentiated by standard port_info/poert_ops
instead of nv_host/host_desc
* thaw() fixed such that only the affected port's irq status is
cleared.
I've tested it on ASUS A8N-E (nForce4, CK804, 10de:0054), and
everything works fine. However, the controller doesn't have
protection against data transfer hang (IORDY hang) and the machine
completely locks up if a device is removed during active data
transfer. I don't think it can be worked around without using the
better interface (ADMA).
This patchset contains 6 patches.
#01-03: prep sata_nv
#04 : improve irq handler
#05 : implement new EH
#06 : add hotplug support
This patchset is against
upstream (db9ca5803566078aafe63cf364ef98b5097e4194)
Thanks.
--
tejun
[1] http://article.gmane.org/gmane.linux.ide/11381
next reply other threads:[~2006-06-17 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 6:49 Tejun Heo [this message]
2006-06-17 6:49 ` [PATCH 1/6] sata_nv: kill not-working hotplug code Tejun Heo
2006-06-20 9:09 ` Jeff Garzik
2006-06-20 9:14 ` Tejun Heo
2006-06-17 6:49 ` [PATCH 2/6] sata_nv: kill struct nv_host_desc and nv_host Tejun Heo
2006-06-17 6:49 ` [PATCH 3/6] sata_nv: simplify constants Tejun Heo
2006-06-17 6:49 ` [PATCH 4/6] sata_nv: better irq handlers Tejun Heo
2006-06-17 6:49 ` [PATCH 6/6] sata_nv: add hotplug support Tejun Heo
2006-06-17 6:49 ` [PATCH 5/6] sata_nv: convert to new EH Tejun Heo
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=11505269953650-git-send-email-htejun@gmail.com \
--to=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.