From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JpqjB-00043h-A6 for qemu-devel@nongnu.org; Sat, 26 Apr 2008 16:10:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jpqj9-00043G-Hb for qemu-devel@nongnu.org; Sat, 26 Apr 2008 16:10:32 -0400 Received: from [199.232.76.173] (port=55053 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jpqj9-000436-CI for qemu-devel@nongnu.org; Sat, 26 Apr 2008 16:10:31 -0400 Received: from ug-out-1314.google.com ([66.249.92.169]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jpqj9-0003Li-33 for qemu-devel@nongnu.org; Sat, 26 Apr 2008 16:10:31 -0400 Received: by ug-out-1314.google.com with SMTP id m2so386325uge.4 for ; Sat, 26 Apr 2008 13:10:30 -0700 (PDT) Message-ID: Date: Sat, 26 Apr 2008 22:10:30 +0200 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] [4254] Let WM8750 users write to audio buffer directly. In-Reply-To: <48133826.80501@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48132E27.6090301@web.de> <48133826.80501@web.de> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 26/04/2008, Jan Kiszka wrote: > andrzej zaborowski wrote: > > On 26/04/2008, Jan Kiszka wrote: > >> Andrzej Zaborowski wrote: > >> > Revision: 4254 > >> > http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4254 > >> > Author: balrog > >> > Date: 2008-04-26 12:00:18 +0000 (Sat, 26 Apr 2008) > >> > > >> > Log Message: > >> > ----------- > >> > Let WM8750 users write to audio buffer directly. > >> > >> > >> Works - but who is now in charge of applying volume and mute settings, > >> the wm8750 on dac_commit or its user? Or do you plan to switch to > >> AUD-level control directly? > > > > The wm8750 for sure, maybe in wm8750_out_flush just before > > AUD_write(). But I'm not sure that it's a useful feature enough to do > > it in software. I'd rather wait until there appears a generic mixer > > api (don't know about any plans). > > > Hmm, unfortunate situation. We currently even have the regression that > muting, which worked fine with the wm8750 before, is now broken and Yes, my doubt is if there is a use case in which this ever makes a difference (and if it's valid for svn users), i.e. when you can't use the host's mixer (using a mixer app outside qemu). With the VirtualBox style mixer api the guest and host mixers can be the same and that would be best to have. Regards -- Please do not print this email unless absolutely necessary. Spread environmental awareness.