Re: [RFC BlueZ 1/3] audio/a2dp: connect A2DP vendor codec if possible

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Luiz,
On 05/07/2015 05:20 PM, Luiz Augusto von Dentz wrote:
Hi Chan-yeol,

On Wed, May 6, 2015 at 6:10 PM,  <chanyeol.park@xxxxxxxxxxx> wrote:
From: Chan-yeol Park <chanyeol.park@xxxxxxxxxxx>

This patch gives the priority on vendor codec during A2DP codec
negotiation.

There is already a prioritization based on the sender and in the order
the endpoints are registered, so by doing this you would be breaking
the prioritization instead register the codecs in order of preference
that should have the same results.


Yes you're right. but most of phone(Android/iOS) register their SBC in the first SEP to support compatibility because some of headset try to connect first SEP without codec comparison. As a result I could not register vendor codec in the first SEP. So without this patch vendor codec establishment would not be made.

I am not clear how to give the priority on vendor codec in this case.

Thanks
Chanyeol
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux