Hi Loic, > New ACPI ID means that this is a different hardware. So it needs to be > tested before being added into the driver supported list. An already > supported hardware should keep the same ACPI ID, making it work out-of > the-box. That makes sense. What about the other ACPI ID (BCM2E3C) that I've found in the ACPI table of that ThinkPad 8 tablet? Is it included in its table to cover another HW variant of that product, using a different Broadcom chipset? Any value for you if I create a similar patch (without being able to test it)? I guess the answer will be "No" from your message above but just let me know. >> Finally, is btattach the only command recommended and supported moving >> forward > > > Absolutely, think btattach is the only recommended way. > Even if you can make it work with hciattach by adding device entry with > correct protocol ID, it is not recommended since hciattach is dedicated > to user-space initialisation (old-way) and code is pretty deprecated. That's what I thought, thanks for the confirmation. Regards, Jérôme -- 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
