From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 2/5] speedup: Check for supported modem capabilities first
Date: Mon, 09 Jan 2012 11:36:20 -0800 [thread overview]
Message-ID: <1326137780.6454.151.camel@aeonflux> (raw)
In-Reply-To: <4F088E4B.7010708@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
Hi Denis,
> > plugins/speedup.c | 40 ++++++++++++++++++++++++++++++++++++++--
> > 1 files changed, 38 insertions(+), 2 deletions(-)
> >
> > diff --git a/plugins/speedup.c b/plugins/speedup.c
> > index a90dfe3..f03f8f3 100644
> > --- a/plugins/speedup.c
> > +++ b/plugins/speedup.c
> > @@ -25,6 +25,7 @@
> >
> > #include <errno.h>
> > #include <stdlib.h>
> > +#include <string.h>
> >
> > #include <glib.h>
> > #include <gatchat.h>
> > @@ -47,11 +48,15 @@
> > #include <drivers/atmodem/atutil.h>
> > #include <drivers/atmodem/vendor.h>
> >
> > +static const char *gcap_prefix[] = { "+GCAP:", NULL };
> > +
> > struct speedup_data {
> > GAtChat *modem;
> > GAtChat *aux;
> > gboolean have_sim;
> > struct at_util_sim_state_query *sim_state_query;
> > + gboolean have_gsm;
> > + gboolean have_cdma;
>
> It might be a good idea to use a single gboolean, or better yet an enum
> here instead. There's no point to waste 8 bytes when a single byte can do.
I did this on purpose for the Huawei driver. We can unify this later on,
but at this moment I rather see what is actually happening.
Since we keep parsing all capabilities, I wanna avoid that a later one
overwrites a previous one. That said, just using some flags would be
better anyway. Especially since we also always have have_sim as well.
However that can be done as a further optimization in the Speedup and
Huawei drivers.
Regards
Marcel
next prev parent reply other threads:[~2012-01-09 19:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 13:10 [PATCH 0/5] Unify SpeedUp plugin Guillaume Zajac
2012-01-09 13:10 ` [PATCH 1/5] udevng: Remove huaweicdma label from driver_list Guillaume Zajac
2012-01-07 18:26 ` Denis Kenzior
2012-01-09 13:10 ` [PATCH 2/5] speedup: Check for supported modem capabilities first Guillaume Zajac
2012-01-07 18:26 ` Denis Kenzior
2012-01-09 19:36 ` Marcel Holtmann [this message]
2012-01-07 19:26 ` Denis Kenzior
2012-01-10 13:43 ` Guillaume Zajac
2012-01-08 10:12 ` Denis Kenzior
2012-01-10 15:37 ` Guillaume Zajac
2012-01-08 14:27 ` Denis Kenzior
2012-01-11 10:48 ` Guillaume Zajac
2012-01-11 11:06 ` Denis Kenzior
2012-01-11 15:12 ` Guillaume Zajac
2012-01-09 13:10 ` [PATCH 3/5] speedup: Create GSM/UMTS atoms only if support has been detected Guillaume Zajac
2012-01-09 13:10 ` [PATCH 4/5] speedup: Create CDMA atoms " Guillaume Zajac
2012-01-09 13:11 ` [PATCH 5/5] udevng: Simplify vendor and driver list for SpeedUp Guillaume Zajac
2012-01-09 13:14 ` [PATCH] speedupcdma: Delete unused plugin Guillaume Zajac
2012-01-12 10:00 ` [PATCH 0/5] Unify SpeedUp plugin Guillaume Zajac
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=1326137780.6454.151.camel@aeonflux \
--to=marcel@holtmann.org \
--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