From: Valentin SURREL <dev@surrel.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] PATCH for dund : correct --dialup behavior (Tomtom GPS)
Date: Sun, 19 Nov 2006 12:04:05 +0100 [thread overview]
Message-ID: <45603A25.9080806@surrel.org> (raw)
Hello,
I've found a little problem when trying to connect my Tomtom One GPS to
the Intenet via my computer.
Tomtom GPS expect to find a GSM Phone with DUN. I changed the class in
/etc/bluetooth/hcid.conf to 0x520204.
Then I started dund with the correct options (--dialup particularly).
It did'nt work, Tomtom claiming that my 'phone' have not DUN.
I made this very little modification to dund/sdp.c :
./bluez-utils-3.7/dund$ diff sdp_original.c sdp.c
173a174,176
> case DIALUP:
> sdp_uuid16_create(&svclass, DIALUP_NET_SVCLASS_ID);
> break;
After that, it works perfectly. Maybe this patch should be integrated
into the official Bluez utils...
Valentin SURREL
-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-11-19 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 11:04 Valentin SURREL [this message]
2006-11-19 11:13 ` [Bluez-devel] PATCH for dund : correct --dialup behavior (Tomtom GPS) Marcel Holtmann
2006-11-19 11:31 ` Valentin SURREL
2006-11-20 8:16 ` Marcel Holtmann
[not found] <mailman.55247.1163941931.8777.bluez-devel@lists.sourceforge.net>
2006-11-19 13:27 ` Arjan van de Ven
2006-11-20 8:17 ` Marcel Holtmann
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=45603A25.9080806@surrel.org \
--to=dev@surrel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox