On Thu, 2014-09-11 at 08:06 -0700, Marcel Holtmann wrote: > Hi Bastien, > > > I have a tablet that seems to be using Realtek chips to do wireless > > communications (hopefully, this time I won't be wrong[1]). > > > > The device, under the gpio class in /sys, shows with a modalias of > > "acpi:OBDA8723:" (that's on "O", not "0"). This seems to correspond to a > > Realtek chipset (Larry tells me it matches the PCI ID of 0bda:8723 for > > the RTL8723AE chipset). > > > > It shows up under: > > /sys/devices/platform/80860F0A:00/subsystem/devices > > > > Does anyone have details on how this chipset is actually hooked up? Can > > a portion of the existing RTL8723AE driver code be reused? > > so after a little bit of digging, this seems to be the UART device for > the Bluetooth chip. Can you try using 8250_dw.ko driver and see if it > binds to it and you get a new serial port. > > If I am correct then you have to run H:5 UART transport protocol to > enable Bluetooth for this device. > > Please double check that this ACPI tables really wrongly declare this > as a Broadcom chip. This seems to be a firmware bug then. No, there are devices declared in the DSDT that won't be available on the platform itself. The _STA function for each device will tell you whether the device is available or not (look for TSC in the DSDT, I don't have 3 touchscreens either ;). > Unfortunately I think that for Broadcom you run H:4 UART transport > protocol and for Realtek you have to run H:5 UART transport protocol. > So no idea how to nicely differentiate these. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
