From: Bastien Nocera <hadess@hadess.net>
To: Dan Williams <dcbw@redhat.com>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>,
networkmanager-list@gnome.org
Subject: Re: So very close, but so frustrating...
Date: Fri, 02 Oct 2009 00:19:29 +0100 [thread overview]
Message-ID: <1254439169.22191.317.camel@localhost.localdomain> (raw)
In-Reply-To: <1254433173.9657.155.camel@localhost.localdomain>
On Thu, 2009-10-01 at 14:39 -0700, Dan Williams wrote:
> On Wed, 2009-09-30 at 20:18 -0400, Darren Albers wrote:
<snip>
> > At this time Network Manager does not support Bluetooth modems. I
> > think 0.8 supports phones if they use Bluetooth PAN but not Bluetooth
> > DUN.
>
> Correct; I may just get bored enough today triaging bugs to go implement
> DUN in 0.8. That opens up a huge number of cellphones, which will
> inevitably lead to even more bugs since there's much more phone
> variation than in the relatively small data card space. Oh well; it
> would help a lot of people out.
1. Add ability for MM to identify Bluetooth modems
2. Add plugin in bluez to poke at the modem with MM if it doesn't know
the type of device, cache the result, the bluez plugin exports the
information through a service
3. Add DUN gnome-bluetooth plugin to nm-applet which would poke the
bluez service
4. Add native support in NM to do the connection through bluetoothd
After 3., if the box is ticked, the device should appear like an
unconfigured WWAN modem to the user. The service configuration can then
be done through nm-applet.
I can certainly take care of 2. and 3. if you do 1. and the left-overs
of 4 :)
Cheers
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
next parent reply other threads:[~2009-10-01 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AC3EFD9.1020602@shic.co.uk>
[not found] ` <7cd7fc040909301718r3e441c53x767084b0b01f4a7c@mail.gmail.com>
[not found] ` <1254433173.9657.155.camel@localhost.localdomain>
2009-10-01 23:19 ` Bastien Nocera [this message]
2009-10-02 0:55 ` So very close, but so frustrating Rick Jones
2009-10-02 8:39 ` Bastien Nocera
2009-10-03 1:44 ` Dan Williams
2009-10-03 8:08 ` Dan Williams
2009-10-05 10:55 ` Bastien Nocera
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=1254439169.22191.317.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=dcbw@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=networkmanager-list@gnome.org \
/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