Hi, > -----Original Message----- > From: Marcel Holtmann [mailto:marcel@xxxxxxxxxxxx] > Sent: Thursday, April 30, 2015 5:25 PM > To: One Thousand Gnomes > Cc: Eyal Reizer; linux-kernel@xxxxxxxxxxxxxxx; Reizer, Eyal; Pavan Savoy; > Mahaveer, Vishal; linux-bluetooth@xxxxxxxxxxxxxxx > Subject: Re: [PATCH] Bluetooth: Add tty HCI driver > > Hi, > > >> tty_hci driver exposes a /dev/hci_tty character device node, that > >> intends to emulate a generic /dev/ttyX device that would be used by > >> the user-space Bluetooth stacks to send/receive data to/from the WL > >> combo-connectivity chipsets. > > > > We have an in kernel bluetooth stack, why do we care about this - how > > will people test and debug driver interactions with binary only > > bluetooth stacks in userspace ? > > NAK to this driver. > > If you want to run an external Bluetooth stack, then use HCI User Channel. The > functionality already exists. This is a pretty old driver that has been written a couple of years back and is being used by customers (including android that use a userspace based stack). If there is another driver already available that provides same functionality, of course we will be happy to use it instead. Any idea of where we can get info on the HCI User Channel? > > We do not want to have two drivers for the same hardware. Work with the > Bluetooth stack that is present in the kernel and please stop hacking around it. > There are in fact quite a few products that use commercial user space based Bluetooth stacks. One reason is that bluez has not been certified but I assume they have other reasons as well. Best Regards, Eyal -- 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
