Thread (5 messages) 5 messages, 3 authors, 2021-08-26

Re: [PATCH v5] Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller

From: Matthias Kaehlcke <mka@chromium.org>
Date: 2021-08-26 17:55:45
Also in: linux-arm-msm, linux-bluetooth

On Tue, Aug 24, 2021 at 02:12:00AM -0700, Matthias Kaehlcke wrote:
On Tue, Aug 24, 2021 at 04:28:03PM +0800, Zijun Hu wrote:
quoted
From: Tim Jiang <redacted>

we have variant wcn6855 soc chip from different foundries, so we should
use different nvm file with suffix to distinguish them.
Similar question as on v4: why is it necessary to know where a chip was
manufactured? Is the hardware different? Should the FW behave differently
for some reason (e.g. regulatory differences)?
Tim briefly responded in private, I'm not sure if I'm allowed to share it
publicly.

I still doubt whether the 'foundry' is the right way to split things, I'm
more inclined towards the concept of a 'variant', which is more flexible.

Anyway, I'll leave it to the maintainers, if they are happy with the foundry
thing I'm fine with it.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help