From: Bastien Nocera <hadess@hadess.net>
To: "Gustavo F. Padovan" <gustavo@padovan.org>
Cc: ofono@ofono.org,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: DUN client for oFono and BlueZ
Date: Tue, 27 Apr 2010 16:40:44 +0100 [thread overview]
Message-ID: <1272382844.17421.6792.camel@localhost.localdomain> (raw)
In-Reply-To: <20100427153043.GA3374@vigoh>
On Tue, 2010-04-27 at 12:30 -0300, Gustavo F. Padovan wrote:
> Hi Bastien,
>
>
> * Bastien Nocera <hadess@hadess.net> [2010-04-27 09:15:28 +0100]:
>
> > On Mon, 2010-04-26 at 22:20 -0300, Gustavo F. Padovan wrote:
> > > Hi all,
> > >
> > > I'm starting the DUN Client implementation for the Linux Stack. DUN is
> > > the Bluetooth dial-up network profile. It makes possible share internet
> > > connection between two Bluetooth devices. That is my Google Summer of Code
> > > project for this year.
> >
> > Does this project include anything that will be reusable by non-oFono
> > based projects? Native BT PPP line discipline would have been nice.
> >
>
> Yes, oFono will be only the Agent, you can implement a new one if you
> want.
The ppp implementation in NetworkManager already works for me.
> Also oFono already does the PPP line discipline, so we don't need
> to duplicate such feature in BlueZ.
I thought BT PPP line discipline was a kernel feature.
prev parent reply other threads:[~2010-04-27 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 1:20 DUN client for oFono and BlueZ Gustavo F. Padovan
2010-04-27 2:07 ` Marcel Holtmann
2010-04-27 2:12 ` Gustavo F. Padovan
2010-04-27 2:14 ` Zhang, Zhenhua
2010-04-27 2:19 ` Gustavo F. Padovan
2010-04-27 2:40 ` Zhang, Zhenhua
2010-04-27 2:35 ` Denis Kenzior
2010-04-27 6:03 ` Kalle Valo
2010-04-27 6:35 ` Gustavo F. Padovan
2010-04-27 7:26 ` Kalle Valo
2010-04-27 8:15 ` Bastien Nocera
2010-04-27 15:30 ` Gustavo F. Padovan
2010-04-27 15:40 ` Bastien Nocera [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=1272382844.17421.6792.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ofono@ofono.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;
as well as URLs for NNTP newsgroup(s).