linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
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 04:07:13 +0200	[thread overview]
Message-ID: <1272334033.22838.117.camel@localhost.localdomain> (raw)
In-Reply-To: <20100427012059.GG12813@vigoh>

Hi Gustavo,

> 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.
> 
> Here follows a simple, and possible not complete, roadmap:
> 
> 1. Put send_method_call() and send_method_call_with_reply() on gdbus: those
> functions are very useful for DBus operations. You can send a DBus message
> just calling them with the right parameters. Patch for that work already 
> on the mailing list.
> 
> 2. Create a bluetooth.c file with the bluetooth helpers. oFono plugins for HFP,
> DUN and SAP will be able to share the same bluetooth code to access BlueZ
> stuff. This is a ongoing work.
> 
> 3. plugin/dun.c prototype. A simple prototype for the DUN client.
> 
> 4. Agent server on BlueZ. This one is very similar to the HFP Agent server. At
> the end of the DUN agent project I plan to merge the both agent servers. SAP
> will take advantage of that merge too.
> 
> 5. oFono DUN agent. Implement the agent handling for DUN.
> 
> 6. AT command parser and PPP stack integration with DUN. The biggest task,
> where the core of the project is.

this is pretty clear. oFono carries the GAtChat library that comes with
AT command and PPP support. So oFono should carry the DUN client.

Regards

Marcel



  reply	other threads:[~2010-04-27  2:07 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 [this message]
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

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=1272334033.22838.117.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --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).