From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: [Patch] Some btsco modifications
Date: Wed, 16 Mar 2005 20:34:42 +0100 [thread overview]
Message-ID: <42388A52.3050601@dark-reality.de> (raw)
In-Reply-To: <1110978114.19889.45.camel@pc7.dolda2000.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Fredrik Tolf wrote:
| On Wed, 2005-03-16 at 13:30 +0100, Lars Grunewaldt wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Fredrik Tolf wrote:
|>| On Tue, 2005-03-15 at 17:17 -0700, Brad Midgley wrote:
|>| In a perfect world, yes. But the question is: Does the kernel actually
|>| detect wandering out of range, and if so, after how long? If the kernel
|>| can't detect it, is there a way of periodically pinging the headset to
|>| detect it manually?
|>
|>Of course the kernel detects it when a device get's out of range. Not
|>immediatly, but as soon as the lower level BT links break down. Pretty
|>much a protocol feature...
|
|
| Well, I have to admit that I don't really know much about how BT works.
| I just got into the btsco project because I wanted to integrate it
| closer with Gnomemeeting and other VoIP programs, as can be seen from
| the fact that the features I've contributed are pretty
| non-bluetooth-related.
|
| Thanks for enlightening me, though. I would have thought that when the
| device got out of range, the kernel just wouldn't know the status of it
| since it couldn't reach it (and maybe time out after a longer period of
| time). Does anyone have any pointers to good documentation that I can
| use to read up on BT?
As Brad already wrote, dig bluetooth.org. The whole BT thing is set up
as a standard (sort of), from hardware up to the software/driver level.
You can find everything (i.e. AT commands) in the core docs. Maybe you
have to check the older BT specs (1.1) for the headset profile and
especially the sco stuff. And make sure to understand what the different
transport layers do, it helps a lot.
good luck :)
- - Lars
- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCOIpRQWC6DTWkDAoRAjOFAJ9I3dRVDKIq2ueykN9KG7t59+H8dQCgti/I
YW48SkCAWRHezHM4rMGmQeg=
=SilZ
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-03-16 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1110683934.5056.43.camel@pc7.dolda2000.com>
[not found] ` <4233C663.80109@xmission.com>
2005-03-14 1:11 ` [Bluez-devel] Re: [Patch] Some btsco modifications Fredrik Tolf
2005-03-14 11:52 ` Lars Grunewaldt
2005-03-14 13:51 ` Fredrik Tolf
2005-03-14 15:00 ` Fredrik Tolf
2005-03-14 12:55 ` Brad Midgley
2005-03-14 14:05 ` Fredrik Tolf
2005-03-14 17:26 ` Brad Midgley
2005-03-14 19:01 ` Florian Echtler
2005-03-14 20:34 ` Brad Midgley
2005-03-15 7:22 ` Brad Midgley
2005-03-15 23:42 ` Fredrik Tolf
2005-03-16 0:17 ` Brad Midgley
2005-03-16 1:56 ` Fredrik Tolf
2005-03-16 12:30 ` Lars Grunewaldt
2005-03-16 13:01 ` Fredrik Tolf
2005-03-16 15:18 ` Brad Midgley
2005-03-16 19:34 ` Lars Grunewaldt [this message]
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=42388A52.3050601@dark-reality.de \
--to=lgw@dark-reality.de \
--cc=bluez-devel@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.