From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
Alan Cox <alan@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Port-Multiplier hotplug support: ATA_FLAG_AN
Date: Tue, 13 May 2008 18:50:41 -0400 [thread overview]
Message-ID: <482A1B41.50507@rtr.ca> (raw)
Tejun,
Apparently the newer (GenIIe) sata_mv chips *can* support asynchronous
notification without problems. Some/all of the older ones cannot (errata).
So, I've done the one-liner change in sata_mv, to add ATA_FLAG_AN to
the 7042 and 6042 chips, and it all seems to work rather nicely.
Am I missing something? Is there any other local code to sata_mv
that should be provided before setting ATA_FLAG_AN ?
Like I said, it works, but I just want to check whether any other
pieces are expected to be present?
Cheers
Mark
next reply other threads:[~2008-05-13 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 22:50 Mark Lord [this message]
2008-05-13 23:25 ` Port-Multiplier hotplug support: ATA_FLAG_AN Jeff Garzik
2008-05-14 2:50 ` Mark Lord
2008-05-14 3:10 ` Tejun Heo
2008-05-14 12:46 ` 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=482A1B41.50507@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 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).