From: "Loreno Oliveira" <lorenooliveira@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] reducing dongle coverage area
Date: Thu, 19 Apr 2007 09:16:22 -0300 [thread overview]
Message-ID: <c49421c50704190516n2d23c01ep4df69fa9d6b9ff29@mail.gmail.com> (raw)
In-Reply-To: <c49421c50704131206m19108a6ctc86461e05137570e@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 562 bytes --]
I´m really sorry the re-post,
but does anyone can give me some direction on this?
Regards,
Loreno
On 4/13/07, Loreno Oliveira <lorenooliveira@gmail.com> wrote:
>
> Hi,
>
> is there any way to reduce the coverage area of a bluetooth dongle? That
> is, I have a class 2 dongle and I need to make some tests with it. However,
> the tests would be quite simpler if I could reduce the range of the device
> to about 2 or 4 meters.
>
> Does anyone know how can I do that with bluez, or even if this is
> possible?
>
> Regards,
>
> Loreno
>
[-- Attachment #1.2: Type: text/html, Size: 868 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-04-19 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 19:06 [Bluez-users] reducing dongle coverage area Loreno Oliveira
2007-04-19 12:16 ` Loreno Oliveira [this message]
2007-04-19 13:15 ` Raymond Ingles
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=c49421c50704190516n2d23c01ep4df69fa9d6b9ff29@mail.gmail.com \
--to=lorenooliveira@gmail.com \
--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