From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Reg: Memory capacity exceeded
Date: Mon, 20 Sep 2010 09:11:45 -0500 [thread overview]
Message-ID: <4C976BA1.30600@gmail.com> (raw)
In-Reply-To: <B668883EB5DD7144ADFC248A72176EA802A51A03@fioues07.ebgroup.elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
Hi Jeevaka,
On 09/20/2010 09:08 AM, Jeevaka.Badrappan(a)elektrobit.com wrote:
>
> Hi Denis,
>
>> The thing is, oFono configures SMS for direct delivery (e.g. no SM/ME
> storage). And even if direct delivery does not work (e.g. crappy modem
> or Class 2 / Class 3 messages) oFono still removes the SMS
>> as soon as it is delivered. We should never hit a sim/me memory full
> conditions.
>
>> So I don't see how this test case even applies.
>
> Little bit lost now. Are we speaking about the sending or receiving of
> SMS?
>
> Memory capacity exceeded applies to incoming SMS. Incoming SMS can be
> stored in SIM or in ME storage. If the SMS storage for incoming SMS is
> full, then the ME can inform the network that it can't handle any more
> class 1/class 2 incoming SMS due to maximum memory capacity reached.
> Once the user frees some memory by deleting some messages, then ME can
> inform network that it is ready now to receive messages. So, I believe
> this test case applies but as Pessi Pekka said we can waive this test
> case.
I know exactly the case you're talking about, but as I mentioned before,
oFono does not configure the modem to store on SIM or ME. The messages
are routed directly to oFono. See drivers/atmodem/sms.c for more
details. The only messages that *might* get routed to SM/ME are Class 2
/ 3 messages. These are automatically deleted on reception by the sms
driver.
The 'memory capacity reached' can simply never happen assuming sane
hardware.
Regards,
-Denis
next prev parent reply other threads:[~2010-09-20 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 10:45 Reg: Memory capacity exceeded linux mobile
2010-09-20 10:56 ` Marcel Holtmann
2010-09-20 11:09 ` Jeevaka.Badrappan
2010-09-20 12:25 ` Aki Niemi
2010-09-20 12:29 ` Pekka Pessi
2010-09-20 12:39 ` Jeevaka.Badrappan
2010-09-20 12:44 ` Denis Kenzior
2010-09-20 14:08 ` Jeevaka.Badrappan
2010-09-20 14:11 ` Denis Kenzior [this message]
2010-09-20 12:53 ` Aki Niemi
2010-09-21 6:34 ` linux mobile
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=4C976BA1.30600@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