From: Bastien Nocera <hadess@hadess.net>
To: Mario_Limonciello@Dell.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Remove hid2hci from bluez
Date: Mon, 15 Jun 2009 00:33:20 +0100 [thread overview]
Message-ID: <1245022400.11069.6101.camel@localhost.localdomain> (raw)
In-Reply-To: <6BE8CE7840AC9F459EF5A0693CA2744D5DB52E@ausx3mpc138.aus.amer.dell.com>
On Sun, 2009-06-14 at 17:54 -0500, Mario_Limonciello@Dell.com wrote:
> Hi:
>
> Since hid2hci has been accepted into udev-extras, I'd like to remove it
> from bluez source. Attached is a patch.
I really wonder how good an idea that is, given that, ultimately, we'd
want to remove hid2hci from everything, and handle the switching from
within bluetoothd.
If we had specs for the devices (or at least rev-eng'ed specs), we'd
need to do link keys management, and switching the devices to hci mode
from within the same codebase.
So I'd rather hid2hci didn't go into udev-extras, and stayed in bluez
until a better solution comes along.
(Still no luck on getting specs from Broadcom about the Dell adapters at
least?)
Cheers
next prev parent reply other threads:[~2009-06-14 23:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 22:54 [PATCH] Remove hid2hci from bluez Mario_Limonciello
2009-06-14 23:33 ` Bastien Nocera [this message]
2009-06-15 14:13 ` Mario Limonciello
2009-06-15 14:28 ` Bastien Nocera
2009-06-15 14:43 ` Mario Limonciello
2009-06-15 19:08 ` Marcel Holtmann
2009-06-19 17:04 ` Mario Limonciello
2009-06-19 17:05 ` Mario Limonciello
2009-06-15 8:20 ` Simon Kenyon
2009-06-15 10:03 ` Bastien Nocera
2009-06-15 15:07 ` Simon Kenyon
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=1245022400.11069.6101.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=Mario_Limonciello@Dell.com \
--cc=linux-bluetooth@vger.kernel.org \
/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