On Thu, 2014-09-11 at 10:06 -0700, Marcel Holtmann wrote:
> Hi Bastien,
> 
> >>>> Your device is a child of 80860F0A (UART) which is driven by the 8250_dw 
> >>>> driver.
> >>>> OBDA8723 is the BT part of the realtek 8723 WiFi/BT combo chip.
> >>>> acpi_platform should create a platform device from the ACPI desc.
> >>> 
> >>> That does show up already in udev, so I should be fine.
> >>> 
> >>>> Then, you can add the OBDA8723 acpi id to the rfkill-gpio platform 
> >>>> driver (net/rfkill) which
> >>>> seems to handle correctly the basic power management of this chip.
> >>> 
> >>> OK. Something like that should do:
> >>> http://paste.fedoraproject.org/132832/14104505
> >>> 
> >>>> You need to use hciattach to attach the chip to the BT stack (with 
> >>>> H5/3-wire proto).
> >>> 
> >>> Will that be required to enable Bluetooth at every boot?
> >>> 
> >>> After inserting the above module, I ran:
> >>> hciattach -n ttyS0 3wire
> >>> 
> >>> But no Bluetooth adapters showed up in hciconfig. The rfkill device did
> >>> show up in rfkill list though.
> >> 
> >> my bet is that you need to start with the correct default speed, load
> >> some firmware and do more settings and then switch to the faster
> >> speed. There is an effort ongoing for the USB version of Realtek
> >> Bluetooth, but even that one has not yet completed.
> > 
> > I have a firmware and a config file from the Windows driver, but I doubt
> > I'd be able to make great headway without more info.
> 
> in theory this is straight forward, but since this is H:5 it needs extra work 
> to make this nice and clean. So far no H:5 hardware required extra settings. 
> This will be the first one. That is mainly because H:5 is not that popular.
> 
> If you can have the basic attachment done with btattach and bring it up in 
> raw only mode, then you could use HCI User Channel to poke with it. We have 
> easy code in src/shared/hci.c that allows you to use the HCI User Channel.
> 
> And you want a 3.17 kernel for toying with this of course since I only 
> recently added the extra flags to hci_uart.ko driver to allow bringing the 
> device up in raw only mode or in unconfigured mode.

This will have to wait a little then, as 3.17 kernel don't boot on this
device yet:
https://bugzilla.kernel.org/show_bug.cgi?id=84241

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to