Return-Path: Cc: Johan Hedberg , "linux-bluetooth@vger.kernel.org" , "Liu, Bing Wei" , "Gao, Bin" , "Yin, Kangkai" Message-Id: <07313D9E-910D-4A9A-9403-54AF52CA5134@holtmann.org> From: Marcel Holtmann To: "Xu, Martin" In-Reply-To: <9F0C1DB20AFA954FA1DA05309350433D5B19E457@pdsmsx503.ccr.corp.intel.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: patch to fix a2dp issue Date: Wed, 8 Apr 2009 05:21:39 +0200 References: <1238730552-3765-1-git-send-email-forrest.zhao@gmail.com> <20090403201207.GA8156@jh-x301> <9F0C1DB20AFA954FA1DA05309350433D5B0B91CC@pdsmsx503.ccr.corp.intel.com> <20090407061728.GA9223@jh-x301> <9F0C1DB20AFA954FA1DA05309350433D5B19E457@pdsmsx503.ccr.corp.intel.com> Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Martin, > But we can not always leave the a2dp feature as broken. I used the > latest aplay application which is from alsa project(alsa-utils) to > test the a2dp feature. That shows the application part, at least > ALSA part is not fixed. > In my opinions, if the effort is not big, can we fix it at bluez > alsa plugin? At least, it is the alsa plugin and it should comply > with the interface although the interface keeps changing.:) we can NOT fix it on the BlueZ side. Please do read the discussion about it since it has been discussed in length. It is an ALSA API issue and needs to be fixed within the applications using ALSA. Regards Marcel