From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:51000) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKd08-0005U6-UT for qemu-devel@nongnu.org; Thu, 12 May 2011 17:00:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QKd07-0002Um-TV for qemu-devel@nongnu.org; Thu, 12 May 2011 17:00:52 -0400 Received: from caiajhbdcbef.dreamhost.com ([208.97.132.145]:56979 helo=homiemail-a12.g.dreamhost.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKd07-0002Ua-IO for qemu-devel@nongnu.org; Thu, 12 May 2011 17:00:51 -0400 Message-ID: <4DCC4A7D.5000802@elasticsheep.com> Date: Thu, 12 May 2011 23:00:45 +0200 From: Mathieu Sonet MIME-Version: 1.0 References: <1305069201-15961-1-git-send-email-contact@elasticsheep.com> <201105111058.33682.paul@codesourcery.com> <4DCAD212.7090601@elasticsheep.com> <201105121841.33091.paul@codesourcery.com> In-Reply-To: <201105121841.33091.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] Add AACI audio playback support to the ARM Versatile/PB platform List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org Paul Brook wrote: >> On the other hand the current ac97.c implementation is a closely coupled >> combination of a PCI/ACLink bridge (Intel 82801AA) with a generic AC97 >> codec. This has prevent me to easily reuse this code. >> >> The milkymist-ac97 implementation is another case. It looks like a basic >> implementation with the AC97 registers directly mapped on the system bus. >> >> Using the ACLink bus I defined, it could be interesting to implement >> separately the PCI/ACLink bridge from ac97.c. >> >> Is it what you mean by saying this should be shared with the other AC97 >> devices ? > > Yes. The whole point of AClink is that it separates the host bridge from the > codec. We now have at least three devices implementing this. Your aclink > implementation is only used by one of these, which gives me little confidence > it actually does what it claims. > > Paul I understand your concern. In fact after digging the Intel PCI bridge documentation, I see that it offers a mapping of the AC97 registers in the PCI I/O space. Reusing my current ACLink bus with this bridge would mean to encode register accesses into ACLink frames and then to decode them again on the codec side. Not very simple just for the sake of device models correctness and no added value. Also QEMU may not need N different re-implemention of an AC97 codec. So I will ditch ACLink/LM4549 and will instead interface the PL041 driver with the codec defined in ac97.c. PCI---AC97 PL041--/ Thanks for your input Mathieu