Open Source Telephony
 help / color / mirror / Atom feed
From: =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont <remi@remlab.net>
To: ofono@ofono.org
Subject: Re: PIPE use in ofono
Date: Tue, 20 Jul 2010 18:49:08 +0300	[thread overview]
Message-ID: <201007201849.09617.remi@remlab.net> (raw)
In-Reply-To: <81C3A93C17462B4BBD7E272753C10579169FAB466E@EXDCVYMBSTM005.EQ1STM.local>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

Le mardi 20 juillet 2010 14:33:51 Hemant-vilas RAMDASI, vous avez écrit :
> Today's Phonet stack in 2.6.24, gprs interface looks like virtual interface
> (similar to TUN) where no connection with real hardware is possible.

Phonet was released in Linux kernel 2.6.27 if I recall correctly.

> I
> can't understand how peps (one on modem and other on linux phonet stack)
> are connected, so that IP packets coming from nokia modem can be forwarded
> to IP stack directly instead of routing from user space using sequence
> socket.

The virtual GPRS network interface runs on top of the Phonet packet socket, 
much like a virtual PPP network interfaces run on top of a TTY port.

The packet socket itself is the Linux-side endpoint of the Phonet pipe between 
the modem and the Linux CPU.

> Is it possible with today's phonet stack? Is there a need of third
> entity like controller to do this?

That's done with the pep_gprs.c network device driver. However, GPRS signaling 
needs to be done in userspace. This is implemented in oFono already.

-- 
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis

      reply	other threads:[~2010-07-20 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20  7:22 PIPE use in ofono Hemant-vilas RAMDASI
2010-07-20  7:56 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2010-07-20 11:33   ` Hemant-vilas RAMDASI
2010-07-20 15:49     ` =?unknown-8bit?q?R=C3=A9mi?= 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=201007201849.09617.remi@remlab.net \
    --to=remi@remlab.net \
    --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