From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Patch to add a --dailup option to dund, needed to make TomTomGo navigators connect to linux
Date: Mon, 16 Jan 2006 23:38:12 +0100 [thread overview]
Message-ID: <1137451092.24817.2.camel@localhost> (raw)
In-Reply-To: <1137340560.3001.21.camel@laptopd505.fenrus.org>
Hi Arjan,
> Below is a patch to dund that adds a -dailup option. This option changes
> the class that is advertized by dund to be "dailup", TomTom Go
> navigators require this to connect to (they only want to connect to
> phones normally ;)
>
> http://www.fenrus.org/tomtom has a howto-in-progress on how to use the
> linux bluez stack to connect a tomtom go to the internet, this patch is
> one of the more hairy aspects of this, so it'd be nice if this got
> merged...
>
> In addition I suspect that tomtom isn't the only one wanting a dailup
> device, so it ought to be a pretty generic feature.
nice patch, but do you mind redoing it and change "dailup" into "dialup"
for some nicer English ;)
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-01-16 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 15:56 [Bluez-devel] Patch to add a --dailup option to dund, needed to make TomTomGo navigators connect to linux Arjan van de Ven
2006-01-16 22:38 ` Marcel Holtmann [this message]
[not found] <20060117040805.07FFC134B1@sc8-sf-spam2.sourceforge.net>
2006-01-17 7:46 ` Arjan van de Ven
2006-01-17 10:49 ` 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=1137451092.24817.2.camel@localhost \
--to=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).