From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] channel-surfing cellphone
Date: Fri, 04 Aug 2006 18:39:50 +0200 [thread overview]
Message-ID: <1154709590.3905.97.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <44D35444.8000304@xmission.com>
Hi Brad,
> I have a Treo 700p that I use for dialup networking. I have to reset the
> thing every once in a while and it seems to invariably alternate between
> channel 1 and 4 for dialup networking.
>
> I'm all set up with the rfcomm mapping, ppp settings, and diald to fire
> up the network using this phone but sometimes things break down because
> the channel has changed! Has anyone worked out a good way to see this
> coming and adapt automatically? I'd like to avoid parsing sdptool output.
so far the only way is to write a wrapper that queries the SDP database
of the phone and creates RFCOMM TTY devices dynamically. The nice static
mapping will no longer work. We don't have SDP support in the Linux
kernel and we will _never_ move this protocol into the kernel.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-08-04 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 14:05 [Bluez-users] channel-surfing cellphone Brad Midgley
2006-08-04 16:39 ` Marcel Holtmann [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=1154709590.3905.97.camel@aeonflux.holtmann.net \
--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