Re: Profile versions are not supported with BT Sig

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

 



Hi Amisha,

On Wed, Oct 30, 2024 at 6:50 AM Amisha Jain (QUIC)
<quic_amisjain@xxxxxxxxxxx> wrote:
>
> Hi Luiz,
> We are verifying the PTS testcases for all supported profiles.
> We are seeing profile version issues for below profiles as current supported versions are in withdrawn state by BT Sig.
> BLUEZ Version - 5.72
>
> >> A2DP
>      Current version 1.3 - Withdrawn
>      Subversion 1.3.2 is adopted
>
> >> AVRCP CT
>      1.6 - Withdrawn
>      Subversion 1.6.2 is adopted
>
> >> HFP
>      1.7.1 - Withdrawn
>      1.7.2 need to be supported
>
> >> PBAP
>      1.1 - Withdrawn
>      Subversion 1.1.1 is adopted
>
>
> >> OPP
>      1.2 - Withdrawn
>      Subversion 1.2.1 is adopted
>
> >> FTP
>      1.2 - Withdrawn
>      1.3 need to be supported
>
> >> MAP
>      1.2 - Withdrawn
>      1.4.2 need to be supported
>
>
> So how do we upgrade the profiles versions so it must be aligned with the BT Sig ?

Normally you just update the SDP record if there are no mandatory
features missing, OBEX profile in particular has not been qualified in
some time which might explain why they were sort of left behind in
terms of version, anyway patches are welcomed and don't forget to
update supported-features.txt.

Speaking about qualification I would also welcome it if you guys are
willing to upstream the qualification documents, in the past we
attempted to document it as text files under pics-*.txt but this is
probably outdated as well.

>
>
> Thanks,
> Amisha
>
>
>
>


-- 
Luiz Augusto von Dentz





[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