Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Telit driver implementation
Date: Tue, 16 Sep 2014 08:01:00 -0500	[thread overview]
Message-ID: <5418348C.3090602@gmail.com> (raw)
In-Reply-To: <CAH4ZQwudt7S0twGZRyMXOOZhoPcNJSjUmLo-wmniY9DrDgL4KQ@mail.gmail.com>

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

Hi Enrico,

Please do not top-post on this mailing list.

On 09/16/2014 04:36 AM, Enrico Sau wrote:
> Thanx for the quick answer,
> what I don't really understand is the difference between drivers and
> plugins in ofono.

Generally drivers/ directory contains atom drivers.  e.g. 
radio_settings, gprs, netreg, etc.  plugins/ contains modem drivers. 
There are a few additional special cases, but that is essentially the 
break down.

> Let's take an example: I need radio-settings interface to get and set
> the technology preference. This interface is not implemented in atmodem
> driver.
> Is it better to extend atmodem driver or to create a new driver? If I
> can do it in plugin it would be fine, but how?

In this case it would be better to write a new atom driver. e.g. 
drivers/telitmodem/radio-settings.c.

> Plus I will need to extend the dbus interfaces to have some more method.
> Looking at the dbus code I see that it calls the driver implementations,
> so I think I have to either extend the atmodem driver or to create a new
> one.

What methods do you need exactly?

Regards,
-Denis

  reply	other threads:[~2014-09-16 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  9:16 Telit driver implementation Enrico Sau
2014-09-16  9:24 ` Jonas Bonn
2014-09-16  9:36   ` Enrico Sau
2014-09-16 13:01     ` Denis Kenzior [this message]
2014-09-16 13:34       ` Enrico Sau

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=5418348C.3090602@gmail.com \
    --to=denkenz@gmail.com \
    --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