From: Gerd Hoffmann <kraxel@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: alevy@redhat.com, yhalperi@redhat.com, qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] hda: do not mix output and input stream states, RHBZ #740493
Date: Fri, 14 Oct 2011 13:38:31 +0200 [thread overview]
Message-ID: <4E981F37.8040805@redhat.com> (raw)
In-Reply-To: <CAJ+F1CKAatOeZR2JfuL+TMKp9nRWWgc_unxnQOROw_XBmYydfg@mail.gmail.com>
Hi,
>> a) My understanding of this patch is that we move from an array of 16
>> bools representing anything to one array where the 1st 16 represent if
>> there are input and the 2nd 16's reprosenting if there are output for
>> that channel.
Correct.
>> So, what we should do if we migrate from one old version that only has
>> 16 bools? My understanding is that copying directly is not gonna work?
Yes. Putting output first increases the chance that it works as sound
playback is used much more than sound recording.
I think hda-audio doesn't need so safe any running state. intel-hda
knows which streams are running and it can call
intel_hda_notify_codecs() for each stream in intel_hda_post_load(). The
only problem is that intel_hda_post_load() might get called before
hda-audio state is loaded.
Now how to handle compatibility? We can have a running_compat[] array
with the current (broken) semantics, so we can write out the state which
older qemu versions expect to see. Also on load running_compat[] will
be filled, and any state already set by intel_hda_post_load in
running_real[] (or however we'll name this) will be kept intact.
cheers,
Gerd
next prev parent reply other threads:[~2011-10-14 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 16:07 [Qemu-devel] [PATCH 0/2] HDA fixes for Windows 7 Marc-André Lureau
2011-10-04 16:07 ` [Qemu-devel] [PATCH 1/2] hda: do not mix output and input streams, RHBZ #740493 Marc-André Lureau
2011-10-04 16:07 ` [Qemu-devel] [PATCH 2/2] hda: do not mix output and input stream states, " Marc-André Lureau
2011-10-04 17:21 ` Juan Quintela
2011-10-05 1:43 ` Marc-André Lureau
2011-10-14 11:38 ` Gerd Hoffmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-17 10:58 [Qemu-devel] [PATCH 1/2] hda: do not mix output and input streams, " Marc-André Lureau
2011-10-17 10:58 ` [Qemu-devel] [PATCH 2/2] hda: do not mix output and input stream states, " Marc-André Lureau
2011-10-25 14:53 [Qemu-devel] [PATCH 1/2] hda: do not mix output and input streams, " Marc-André Lureau
2011-10-25 14:53 ` [Qemu-devel] [PATCH 2/2] hda: do not mix output and input stream states, " Marc-André Lureau
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=4E981F37.8040805@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yhalperi@redhat.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 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.