From: "Rémi Denis-Courmont" <remi@remlab.net>
To: dag@bakke.com
Cc: netdev@vger.kernel.org
Subject: Re: Phonet userspace bits?
Date: Sun, 15 Nov 2009 18:31:23 +0200 [thread overview]
Message-ID: <200911151831.23974.remi@remlab.net> (raw)
In-Reply-To: <1272976626.71600.1258301725789.JavaMail.mail@webmail06>
Hello,
Le dimanche 15 novembre 2009 18:15:25 dag@bakke.com, vous avez écrit :
> How do an end-user make use of a phonet network interface?
>
> Nov 15 16:31:54 toshr500 usb 1-1: New USB device found, idVendor=0421,
> idProduct=046e Nov 15 16:31:54 toshr500 usb 1-1: New USB device strings:
> Mfr=1, Product=2, SerialNumber=0 Nov 15 16:31:54 toshr500 usb 1-1:
> Product: Nokia 6110 Navigator
> Nov 15 16:31:54 toshr500 usb 1-1: Manufacturer: Nokia
> Nov 15 16:31:54 toshr500 usb 1-1: configuration #1 chosen from 1 choice
> Nov 15 16:31:54 toshr500 cdc_acm 1-1:1.8: ttyACM0: USB ACM device
>
> So I can use /dev/ttyACM0 with pppd and get a 3G connection. so far, so
> good.
>
> But what is the usbpn0 network interface, and could I use that instead of
> fiddling with chatscripts and pppd, to get a 3G connection? Is this
> feature complete?
Just like with PPP, only the Phonet data path is implemented in kernel. The
setup is done in userspace. In theory, it could be done in kernelspace too,
but there was strong reluctance against this on usb-devel. And well, maybe we
don't want to taint the kernel with too much of the GPRS specifics.
There was a preliminary patch adding the userspace bits to oFono here:
http://lists.ofono.org/pipermail/ofono/2009-September/000376.html
(especially part 0003) but this is still work in progress.
Best regards,
--
Rémi Denis-Courmont
http://www.remlab.net/
prev parent reply other threads:[~2009-11-15 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <!256485B18-474275-V2@support.norwegian.no>
2009-11-15 16:15 ` Phonet userspace bits? dag
2009-11-15 16:31 ` Rémi Denis-Courmont [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=200911151831.23974.remi@remlab.net \
--to=remi@remlab.net \
--cc=dag@bakke.com \
--cc=netdev@vger.kernel.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).