From: Mario Limonciello <mario_limonciello@dell.com>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: BlueZ devel list <linux-bluetooth@vger.kernel.org>
Subject: Re: hid2hci rules breaks standard USB dell mouses
Date: Thu, 05 Nov 2009 13:10:00 -0600 [thread overview]
Message-ID: <4AF32308.3060400@dell.com> (raw)
In-Reply-To: <20091028093118.71e8f55c@strolchi.home.s3e.de>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
Stefan:
Stefan Seyfried wrote:
> On Tue, 27 Oct 2009 16:24:44 -0500
> Mario Limonciello <mario_limonciello@dell.com> wrote:
>
> Maybe a compromise for the near future:
> * update the rules / tools in bluez to be in sync with udev
> * don't install them by default unless "--enable-old-udev" (or
> something like that) is ./configure'd
>
> Reasoning:
> * people might want to use new bluez with old udev (I personally would
> avoid updating udev in a running system since it seems to interdepend
> on many things. Updating bluez has been painless for me over the last
> years).
>
> Marcel, Mario, does this sound acceptable? If yes, I am willing to
> prepare a patch.
>
Since Marcel doesn't seem keen on my dropping support in BlueZ for
hid2hci (the patch has been ignored twice now), i'm fine with this.
--
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-11-05 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 11:08 hid2hci rules breaks standard USB dell mouses Ozan Çağlayan
2009-10-23 17:03 ` Mario Limonciello
2009-10-24 8:38 ` Marcel Holtmann
2009-10-27 21:24 ` Mario Limonciello
2009-10-28 8:31 ` Stefan Seyfried
2009-11-05 19:10 ` Mario Limonciello [this message]
2009-10-24 10:10 ` Ozan Çağlayan
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=4AF32308.3060400@dell.com \
--to=mario_limonciello@dell.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=stefan.seyfried@googlemail.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 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.