From: Kevin Wolf <kwolf@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] ide/atapi: add support for GET EVENT STATUS NOTIFICATION
Date: Mon, 19 Jul 2010 17:28:40 +0200 [thread overview]
Message-ID: <4C446F28.7070201@redhat.com> (raw)
In-Reply-To: <1279547615-25599-1-git-send-email-aurelien@aurel32.net>
Am 19.07.2010 15:53, schrieb Aurelien Jarno:
> The GET EVENT STATUS NOTIFICATION is a mandatory command according
> to MMC-3, even if event status notification is not supported.
>
> This patch adds support for this command. It returns NEA ("No Event
> Available") with an empty "Supported Event Classes" to show that it
> doesn't event support status notification. If asychronous operation is
> requested, which requires NCQ support, it returns an error according
> to the specifications.
>
> This fixes HAL support on FreeBSD and derivatives, which fill up the
> logs every second with:
>
> acd0: FAILURE - unknown CMD (0x03) ILLEGAL REQUEST asc=0x20 ascq=0x00
>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Looks good to me.
Would you prefer me to take this into the block branch (actually, I have
already done this) or are you going to commit directly? This might
actually be something that should be in 0.13.
Have you tested some more OSes to ensure that they don't start to expect
events to actually work now the command "works"? I didn't see any
problems in a quick test with Linux, but you never know.
Kevin
next prev parent reply other threads:[~2010-07-19 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 13:53 [Qemu-devel] [PATCH] ide/atapi: add support for GET EVENT STATUS NOTIFICATION Aurelien Jarno
2010-07-19 15:28 ` Kevin Wolf [this message]
2010-07-19 15:36 ` [Qemu-devel] " Aurelien Jarno
2010-07-19 15:48 ` Kevin Wolf
2010-07-20 8:54 ` Aurelien Jarno
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=4C446F28.7070201@redhat.com \
--to=kwolf@redhat.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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.