linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Add bluetooth-hid2hci to udev-extras
Date: Mon, 15 Jun 2009 14:09:27 +0000	[thread overview]
Message-ID: <4A365617.5030000@dell.com> (raw)
In-Reply-To: <4A303B6D.6020508@dell.com>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

Hi Kay:

Kay Sievers wrote:
>
> Any reason why the last section in the rules file was completely
> commented-out? I've removed the comment characters, if these rules
> should not be in the file, let me know and we will remove them.
>
>   http://git.kernel.org/?p=linux/hotplug/udev-extras.git;a=blob;f=hid2hci/62-hid2hci.rules;hb=HEAD
>   
They were actually intentionally commented out.  I believe those vid/pid
combos should be produced when the above vid/pid combos are ran (eg when
the device switches from hid->hci).  I don't have that particular
hardware so I can't verify that for sure.  I was leaving them commented
out in the event someone said "I can't get my device out of HCI mode.
Help!", but without causing an endless loop of switching modes.
-- 
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2009-06-15 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 23:02 [PATCH] Add bluetooth-hid2hci to udev-extras Mario Limonciello
2009-06-11 13:03 ` Marcel Holtmann
2009-06-11 16:13 ` Mario Limonciello
2009-06-11 19:41 ` Kay Sievers
2009-06-11 21:05 ` Mario Limonciello
2009-06-11 21:46 ` Kay Sievers
2009-06-12 18:31 ` Mario Limonciello
2009-06-12 19:14 ` Kay Sievers
2009-06-13  1:31 ` Kay Sievers
2009-06-15 14:09 ` Mario Limonciello [this message]
2009-06-15 14:18 ` Kay Sievers

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=4A365617.5030000@dell.com \
    --to=mario_limonciello@dell.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).