public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Add udev rules to start bluetooth on-demand
Date: Sun, 21 Jun 2009 15:05:52 +0100	[thread overview]
Message-ID: <1245593152.26486.7156.camel@localhost.localdomain> (raw)
In-Reply-To: <1245592251.15367.64.camel@violet>

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

On Sun, 2009-06-21 at 15:50 +0200, Marcel Holtmann wrote:
> Hi Bastien,
> 
> > As discussed in previous mails.
> 
> please name it bluetooth.rules. The daemon is also called bluetoothd and
> not bluezd.
> 
> Also you need to have the EXTRA_DIST part in it since _DATA doesn't get
> added to the distribution automatically. For all this changes, you have
> to check with make distcheck.

Fixed version attached

[-- Attachment #2: 0001-Add-udev-rules-to-start-bluetooth-on-demand.patch --]
[-- Type: text/x-patch, Size: 1381 bytes --]

>From f723fb9f588a987bfaba94cfb2c1acb6c89c926c Mon Sep 17 00:00:00 2001
From: Bastien Nocera <hadess@hadess.net>
Date: Sun, 21 Jun 2009 14:37:32 +0100
Subject: [PATCH] Add udev rules to start bluetooth on-demand

Those rules call bluetoothd --udev when a new dongle is inserted.
---
 scripts/Makefile.am     |    4 +++-
 scripts/bluetooth.rules |    5 +++++
 2 files changed, 8 insertions(+), 1 deletions(-)
 create mode 100644 scripts/bluetooth.rules

diff --git a/scripts/Makefile.am b/scripts/Makefile.am
index 494a9c2..d06f95e 100644
--- a/scripts/Makefile.am
+++ b/scripts/Makefile.am
@@ -11,6 +11,8 @@ endif
 if PCMCIARULES
 rules_DATA += bluetooth-serial.rules
 endif
+
+rules_DATA += bluetooth.rules
 endif
 
 if PCMCIARULES
@@ -20,7 +22,7 @@ udev_SCRIPTS = bluetooth_serial
 endif
 
 EXTRA_DIST = bluetooth.init bluetooth.default bluetooth-hid2hci.rules \
-				bluetooth-serial.rules bluetooth_serial
+				bluetooth-serial.rules bluetooth_serial bluetooth.rules
 
 MAINTAINERCLEANFILES = Makefile.in
 
diff --git a/scripts/bluetooth.rules b/scripts/bluetooth.rules
new file mode 100644
index 0000000..f3034b5
--- /dev/null
+++ b/scripts/bluetooth.rules
@@ -0,0 +1,5 @@
+# Run helper every time a Bluetooth device appears
+# On remove actions, bluetoothd should go away by itself
+
+ACTION=="add", SUBSYSTEM=="bluetooth",		RUN+="/usr/sbin/bluetoothd --udev"
+
-- 
1.6.2.2


  reply	other threads:[~2009-06-21 14:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-21 13:39 [PATCH] Add udev rules to start bluetooth on-demand Bastien Nocera
2009-06-21 13:50 ` Marcel Holtmann
2009-06-21 14:05   ` Bastien Nocera [this message]
2009-06-21 14:10     ` Marcel Holtmann
2009-06-24 11:35       ` Bastien Nocera
2009-06-24 16:43         ` Marcel Holtmann
2009-06-24 16:44           ` Bastien Nocera
2009-06-24 16:46             ` Marcel Holtmann
2009-06-24 16:52               ` Bastien Nocera
2009-06-27 10:27                 ` Marcel Holtmann
2009-06-29 15:03                   ` Bastien Nocera
2009-06-30  1:07                     ` 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=1245593152.26486.7156.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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