From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] mbm: add quirks for Dell D5530
Date: Wed, 25 Aug 2010 13:08:40 -0500 [thread overview]
Message-ID: <4C755C28.9020106@gmail.com> (raw)
In-Reply-To: <1282759557.6841.53.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
Hi Marcel,
On 08/25/2010 01:05 PM, Marcel Holtmann wrote:
> Hi Denis,
>
>>> Dell D5530 is an OEM version of F3507g. It has an annoying habit of
>>> announcing itself to world with its own name. It also crashes upon
>>> processing received cbs messages.
>>> ---
>>> plugins/mbm.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++--
>>> 1 files changed, 53 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/plugins/mbm.c b/plugins/mbm.c
>>> index c9b0ea4..1c2b9a8 100644
>>> --- a/plugins/mbm.c
>>> +++ b/plugins/mbm.c
>>> @@ -53,9 +53,15 @@ static const char *cfun_prefix[] = { "+CFUN:", NULL };
>>> static const char *cpin_prefix[] = { "+CPIN:", NULL };
>>> static const char *none_prefix[] = { NULL };
>>>
>>> +enum mbm_variant {
>>> + MBM_GENERIC,
>>> + MBM_DELL_D5530, /* OEM of F3507g */
>>> +};
>>> +
>>> struct mbm_data {
>>> GAtChat *modem_port;
>>> GAtChat *data_port;
>>> + enum mbm_variant variant;
>>> guint poll_source;
>>> guint poll_count;
>>> gboolean have_sim;
>>> @@ -137,9 +143,50 @@ static gboolean init_simpin_check(gpointer user_data)
>>> return FALSE;
>>> }
>>>
>>> +static void d5530_notify(GAtResult *result, gpointer user_data)
>>> +{
>>> + DBG("D5530");
>>> +}
>>> +
>>
>> Should we really bother with this one? Or you're trying to be like
>> Marcel and waste some processing time with unused unsolicited
>> notifications? :)
>
> I think we should until we have this all figured out. More debug output
> is always a good thing.
>
> And yes, essentially there is some processing wasted, but then again,
> this hardware is so damn stupid broken it deserves to be punished ;)
>
I have to disagree, I can understand if you take the unsolicited
notification and break it down somewhat (like we used to with OCTI,
OWCTI, etc for HSO). But just printing a debug seems useless.
Regards,
-Denis
next prev parent reply other threads:[~2010-08-25 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 16:16 [PATCH] mbm: add quirks for Dell D5530 Pekka.Pessi
2010-08-25 16:46 ` Denis Kenzior
2010-08-25 16:54 ` Pekka Pessi
2010-08-25 18:05 ` Marcel Holtmann
2010-08-25 18:08 ` Denis Kenzior [this message]
2010-08-25 18:23 ` Marcel Holtmann
2010-08-25 18:29 ` Denis Kenzior
2010-08-25 18:40 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2010-08-25 17:13 Pekka.Pessi
2010-08-25 17:18 ` Denis Kenzior
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=4C755C28.9020106@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