From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] indication of Class 1 or Class 2 devices
Date: Fri, 14 Oct 2005 12:27:54 +0200 [thread overview]
Message-ID: <1129285674.5057.38.camel@localhost.localdomain> (raw)
In-Reply-To: <8664s05ro4.fsf@coulee.tdb.com>
Hi Russell,
> Is there a way, via /proc or /sys or something to discover whether a
> bluetooth device is Class 1 (100m) or Class 2 (10m)?
the simple answer is no.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-10-14 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 10:17 [Bluez-users] indication of Class 1 or Class 2 devices Russell Senior
2005-10-14 10:27 ` Marcel Holtmann [this message]
2005-10-14 10:40 ` Peter Stephenson
2005-10-14 15:08 ` Steven Singer
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=1129285674.5057.38.camel@localhost.localdomain \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox