Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 11 Mar 2021 08:05:56 -0700
From:   Taylor Phillips <taylor85345@gmail.com>
To:     Ricardo =?utf-8?Q?Ca=C3=B1uelo?= <ricardo.canuelo@collabora.com>
Cc:     linux-bluetooth@vger.kernel.org
Subject: Re: Bug caused by moving to BlueZ 5.56 (bytes stripped from HoG
 reports)
Message-ID: <20210311150556.7ym24egif67k6ilq@taylor-lt>
Reply-To: f6764fe94d45ff9211674c5799b193d15385a056.camel@collabora.com
References: <f6764fe94d45ff9211674c5799b193d15385a056.camel@collabora.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <f6764fe94d45ff9211674c5799b193d15385a056.camel@collabora.com>
Precedence: bulk

Hi Ricardo,

Just passing over this issue in the steam-for-linux github that seems
like it may be related:
https://github.com/ValveSoftware/steam-for-linux/issues/7697.

The latest BlueZ update seems to be causing issues with the Steam
Controller's ability to communicate specifically with the Steam client
over Bluetooth LE. I'm a casual non-dev, so can't tell you much more
than that.

Thanks,

Taylor

On 21/03/04 03:02PM, Ricardo Ca?uelo wrote:
> Hi all,
> 
> I discovered this fix https://github.com/bluez/bluez/commit/35a2c50 while
> debugging a fwupd plugin for a HoG device that implements its FW upgrade
> mechanism using vendor-specific HID reports (
> https://github.com/fwupd/fwupd/blob/master/plugins/pixart-rf/fu-pxi-device.c).
> 
> Initially, the developers were using BlueZ versions prior to 5.56, which is the
> first release that includes that fix, so their code was written with that
> behavior in mind. After moving to 5.56 we found out it crashed and we needed to
> adapt the code to the proper report format. I think this is the kind of issues
> that Dean mentioned here 
> https://marc.info/?l=linux-bluetooth&m=160590969013204&w=2
> 
> Have there been any more reports like this? Is this expected to have a greater
> impact than initially thought?
> 
> Cheers,
> Ricardo
>