From: Kevin Wolf <kwolf@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Markus Armbruster <armbru@redhat.com>,
qemu list <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 4/5] atapi: GESN: Standardise event response handling for future additions
Date: Tue, 12 Apr 2011 15:09:33 +0200 [thread overview]
Message-ID: <4DA44F0D.2020506@redhat.com> (raw)
In-Reply-To: <2170ea9881efc68cd2265b9df956a30eb689b8cc.1302608369.git.amit.shah@redhat.com>
Am 12.04.2011 13:43, schrieb Amit Shah:
> Handle GET_EVENT_STATUS_NOTIFICATION's No Event Available response in a
> generic way so that future additions to the code to handle other
> response types is easier.
>
> Signed-off-by: Amit Shah <amit.shah@redhat.com>
> ---
> hw/ide/core.c | 24 +++++++++++++++++++-----
> 1 files changed, 19 insertions(+), 5 deletions(-)
>
> diff --git a/hw/ide/core.c b/hw/ide/core.c
> index e838990..a9bc1e3 100644
> --- a/hw/ide/core.c
> +++ b/hw/ide/core.c
> @@ -1098,9 +1098,17 @@ static void handle_get_event_status_notification(IDEState *s,
> uint8_t control;
> } __attribute__((packed)) *gesn_cdb;
>
> + struct {
> + uint16_t len;
> + uint8_t notification_class;
> + uint8_t supported_events;
> + } __attribute((packed)) *gesn_event_header;
> +
> unsigned int max_len, used_len;
>
> gesn_cdb = (void *)packet;
> + gesn_event_header = (void *)packet;
I think this should be buf, not packet.
> +
> max_len = be16_to_cpu(gesn_cdb->len);
>
> /* It is fine by the MMC spec to not support async mode operations */
> @@ -1111,12 +1119,18 @@ static void handle_get_event_status_notification(IDEState *s,
> return;
> }
>
> - /* polling */
> + /* polling mode operation */
> +
> /* We don't support any event class (yet). */
> - cpu_to_ube16(buf, 0x00); /* No event descriptor returned */
> - buf[2] = 0x80; /* No Event Available (NEA) */
> - buf[3] = 0x00; /* Empty supported event classes */
> - ide_atapi_cmd_reply(s, 4, max_len);
> + gesn_event_header->supported_events = 0;
> + gesn_event_header->notification_class = 0;
This line has no effect, even after the next patch.
Kevin
next prev parent reply other threads:[~2011-04-12 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 11:43 [Qemu-devel] [PATCH v3 0/5] atapi: Implement 'media' subcommand for GESN Amit Shah
2011-04-12 11:43 ` [Qemu-devel] [PATCH v3 1/5] atapi: Allow GET_EVENT_STATUS_NOTIFICATION after media change Amit Shah
2011-04-12 11:43 ` [Qemu-devel] [PATCH v3 2/5] atapi: Move GET_EVENT_STATUS_NOTIFICATION command handling to its own function Amit Shah
2011-04-12 11:43 ` [Qemu-devel] [PATCH v3 3/5] atapi: GESN: Use structs for commonly-used field types Amit Shah
2011-04-12 13:10 ` Markus Armbruster
2011-04-12 14:00 ` Amit Shah
2011-04-12 11:43 ` [Qemu-devel] [PATCH v3 4/5] atapi: GESN: Standardise event response handling for future additions Amit Shah
2011-04-12 13:09 ` Kevin Wolf [this message]
2011-04-12 13:59 ` Amit Shah
2011-04-12 14:07 ` Kevin Wolf
2011-04-12 14:12 ` Amit Shah
2011-04-12 14:40 ` Paolo Bonzini
2011-04-12 11:43 ` [Qemu-devel] [PATCH v3 5/5] atapi: GESN: implement 'media' subcommand Amit Shah
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=4DA44F0D.2020506@redhat.com \
--to=kwolf@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.com \
/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).