From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez udev rules for Slackware 10.2
Date: Sat, 03 Jun 2006 21:14:33 +0200 [thread overview]
Message-ID: <1149362073.1977.0.camel@localhost> (raw)
In-Reply-To: <5d12691e0606031048o148ad92bre33d6efe2b280560@mail.gmail.com>
Hi Aaron,
> I'm sorry I wasn't more specific, I didn't realize that there were
> other devices then the rfcomm tty device node. This is actually the on
> I am after sense it is needed for my device to work with p3nfs.
>
> I have RFCOMM protocol support enabled in the kernel as a modules, and
> RFCOMM TTY support hard coded. I had to 'modprobe rfcomm' but the
> bluetooth module loaded automatically, both of which are listed in my
> 'lsmod'. How do I get udev to create the rfcomm device node? I
> searched for files containing "rfcomm" in the bluez build directory
> but didn't see anything relating to udev rules. Am I supposed to build
> this node myself or should udev be creating it automatically?
you will see these device nodes if you bind or connect a RFCOMM TTY to a
remote device. See the rfcomm command for more details.
Regards
Marcel
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-06-03 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 2:31 [Bluez-users] bluez udev rules for Slackware 10.2 Aaron Miller
2006-06-03 11:33 ` Marcel Holtmann
2006-06-03 17:48 ` Aaron Miller
2006-06-03 19:14 ` Marcel Holtmann [this message]
2006-06-05 23:52 ` Aaron Miller
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=1149362073.1977.0.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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.