[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <BD312721-96F1-4E12-914B-6F3C0C398E57@holtmann.org>
Date: Mon, 13 Jul 2020 18:32:41 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Vasily Khoruzhick <anarsoul@...il.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Maxime Ripard <mripard@...nel.org>,
Chen-Yu Tsai <wens@...e.org>,
Johan Hedberg <johan.hedberg@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
devicetree <devicetree@...r.kernel.org>,
arm-linux <linux-arm-kernel@...ts.infradead.org>,
kernel list <linux-kernel@...r.kernel.org>,
linux-bluetooth <linux-bluetooth@...r.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
Ondrej Jirman <megous@...ous.com>
Subject: Re: [PATCH 1/3] Bluetooth: Add new quirk for broken local ext
features max_page
Hi Vasily,
>> maybe just the read sync train params command is broken? Can you change the init code and not send it and see if the rest of the init phase proceeds. I would rather have the secure connections actually tested before dismissing it altogether.
>
> I don't think that I have any devices that support secure connections
> to test, I've got only a bluetooth mouse and headphones, both are from
> the 2.0 era.
>
> FWIW unofficial recommendation from Realtek to Pine64 was to avoid
> using any 4.1+ features on this chip. Unfortunately I don't have any
> contacts with Realtek, so I can't confirm that.
>
>> Mind you, there were broken Broadcom implementation of connectionless slave broadcast as well. Maybe this is similar.
>
> I'd prefer to stick to what works unless there's some comprehensive
> test that can figure out what's broken.
check if removing the read sync trains params command makes the controller initialize and usable. Then we see about the rest.
Regards
Marcel
Powered by blists - more mailing lists