From: Mario Limonciello <mario_limonciello@dell.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Remove hid2hci from bluez
Date: Mon, 15 Jun 2009 09:13:57 -0500 [thread overview]
Message-ID: <4A365725.5070503@dell.com> (raw)
In-Reply-To: <1245022400.11069.6101.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Hi Bastien:
Bastien Nocera wrote:
> 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.
>
This is a conflicting goal with the on-demand stuff I feel. You can't
have the on-demand stuff and this working if the BT radio is only
exposed after the device switches modes.
> 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.
>
I agree here, but I don't see the docs showing up anytime soon.
> So I'd rather hid2hci didn't go into udev-extras, and stayed in bluez
> until a better solution comes along.
>
Why? What's it's benefit living in the bluez tree? By moving to
udev-extras, it now lives in /lib/udev and will work even if the /usr
gets mounted on NFS late.
> (Still no luck on getting specs from Broadcom about the Dell adapters at
> least?)
>
I'll send another ping to ask about these again, but I wouldn't hold my
breath.
Regards
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2009-06-15 14:13 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
2009-06-15 14:13 ` Mario Limonciello [this message]
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=4A365725.5070503@dell.com \
--to=mario_limonciello@dell.com \
--cc=hadess@hadess.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.