mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Reizer, Eyal" <eyalr@ti.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Eyal Reizer <eyalreizer@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Pavan Savoy <pavan_savoy@ti.com>,
	"Mahaveer, Vishal" <vishalm@ti.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>, "Ziv, Dotan" <dotanz@ti.com>
Subject: RE: [PATCH] Bluetooth: Add tty HCI driver
Date: Thu, 30 Apr 2015 14:38:49 +0000	[thread overview]
Message-ID: <8665E2433BC68541A24DFFCA87B70F5B2365DFEB@DFRE01.ent.ti.com> (raw)
In-Reply-To: <2A731A0F-6BEB-4614-94E8-90B28BEE2DD9@holtmann.org>

Hi,

> -----Original Message-----
> From: Marcel Holtmann [mailto:marcel@holtmann.org]
> Sent: Thursday, April 30, 2015 5:25 PM
> To: One Thousand Gnomes
> Cc: Eyal Reizer; linux-kernel@vger.kernel.org; Reizer, Eyal; Pavan Savoy;
> Mahaveer, Vishal; linux-bluetooth@vger.kernel.org
> 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



  reply	other threads:[~2015-04-30 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30  7:48 Eyal Reizer
2015-04-30 10:31 ` One Thousand Gnomes
2015-04-30 14:24   ` Marcel Holtmann
2015-04-30 14:38     ` Reizer, Eyal [this message]
2015-04-30 14:58       ` Marcel Holtmann
2015-04-30 15:08         ` Ziv, Dotan
2015-04-30 15:19           ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8665E2433BC68541A24DFFCA87B70F5B2365DFEB@DFRE01.ent.ti.com \
    --to=eyalr@ti.com \
    --cc=dotanz@ti.com \
    --cc=eyalreizer@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=pavan_savoy@ti.com \
    --cc=vishalm@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®