All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 7/8] sierra: Support CDMA modems
Date: Tue, 05 Mar 2013 14:52:09 -0600	[thread overview]
Message-ID: <51365AF9.6040600@gmail.com> (raw)
In-Reply-To: <20130305193619.GK11149@alittletooquiet.net>

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

Hi Forest,

>>> I'm looking to pick this series back up now.  I understand the implementation is
>>> not ideal, but it at least provides for basic connectivity until we have support
>>> for the CnS protocol.  Will you accept the full series if I address the other
>>> issues with the code that you mentioned?
>>
>> If we accept something upstream we assume full responsibility for
>> the code, and everything that entails, including future maintenance.
>> Thus we do not have a habit of accepting functionality that is
>> inherently broken.  So unless you can convince me otherwise, my
>> answer is: "I'd rather not" ;)
>
> Well I think the argument to make is that we ought to be able to gracefully
> degrade to handle a device that we have limited support for.  We know how to
> bring up a connection on this device.  I think users would prefer to have a
> device that works with a limited feature set than one that doesn't work at all.

Don't get me wrong, we do want to enable as many devices as possible... 
The problem is that the oFono clients do not know when the device is in 
'degraded' mode.  Our assumption was that we always have multiple AT 
ports available or we are using high-speed interfaces.  If the AT chat 
is blocked by PPP, then we can't even get basic things like signal 
strength notifications while on a data connection.  To me that is 
unacceptable, especially since we know that any AT command based 
implementation is a long-term dead end.

>
> Anyway, I notice that one of the ports appears to be QCDM.  It appears that QCDM
> support is partially implemented in oFono?  But I don't know QCDM at all.  Can
> we use it to do netreg?

oFono QCDM support is quite bare, not much beyond a test tool. 
Contributions are always welcome!

>
> If not, I could probably implement (partial) CnS support at some point.  I'm
> just not sure I will have time to do it right away.
>

That would be great.

> I assume a proper netreg implementation on one of these other ports would
> address your primary concern?

Yep, correct.

>
> Thanks,
> Forest

Regards,
-Denis

  reply	other threads:[~2013-03-05 20:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 19:31 [PATCH 0/8] Sierra Wireless CDMA modem support Forest Bond
2012-12-28 19:34 ` [PATCH 1/8] sierramodem: Add skeleton for Sierra Wireless modem driver Forest Bond
2012-12-28 19:34 ` [PATCH 2/8] sierramodem: Add skeleton cdma netreg driver Forest Bond
2012-12-31  2:11   ` Denis Kenzior
2012-12-28 19:35 ` [PATCH 3/8] sierramodem: Add ERI parsing functions Forest Bond
2012-12-31  2:19   ` Denis Kenzior
2012-12-28 19:35 ` [PATCH 4/8] sierramodem: Report network registration status Forest Bond
2012-12-31  2:26   ` Denis Kenzior
2012-12-28 19:35 ` [PATCH 5/8] sierra: Create GPRS context in post_sim function Forest Bond
2012-12-31  2:39   ` Denis Kenzior
2012-12-28 19:36 ` [PATCH 6/8] sierra: Initialize GSM error reporting separately Forest Bond
2012-12-31  2:40   ` Denis Kenzior
2012-12-28 19:36 ` [PATCH 7/8] sierra: Support CDMA modems Forest Bond
2012-12-31  2:34   ` Denis Kenzior
2013-03-04 16:48     ` Forest Bond
2013-03-04 23:03       ` Denis Kenzior
2013-03-05 19:36         ` Forest Bond
2013-03-05 20:52           ` Denis Kenzior [this message]
2013-03-05 21:45           ` =?unknown-8bit?q?Bj=C3=B8rn?= Mork
2013-03-05 22:15             ` Forest Bond
2013-03-06  9:43               ` =?unknown-8bit?q?Bj=C3=B8rn?= Mork
2013-03-06 13:36                 ` Forest Bond
2012-12-28 19:36 ` [PATCH 8/8] udevng: Support single-interface sierra devices Forest Bond

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=51365AF9.6040600@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.