From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 2/5 v3] Cell-info: Header file for Neighbor cell info
Date: Mon, 07 Feb 2011 11:30:12 -0800 [thread overview]
Message-ID: <1297107012.1520.446.camel@aeonflux> (raw)
In-Reply-To: <1294833919-1510-3-git-send-email-antti.paila@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
Hi Antti,
> +#define OFONO_CI_FIELD_TA_UNDEFINED 0xFF
> +#define OFONO_CI_FIELD_UCID_UNDEFINED 0xFFFFFFFF
> +#define OFONO_CI_FIELD_ECN0_UNDEFINED 0xFF
> +#define OFONO_CI_FIELD_RSCP_UNDEFINED -127
> +#define OFONO_CI_FIELD_PATHLOSS_UNDEFINED 0xFF
> +#define OFONO_CI_FIELD_FREQ_UNDEFINED 0xFFFF
> +
> +#define OFONO_MAX_NMR_COUNT 15
> +#define OFONO_MAX_MEASURED_CELL_COUNT 32
> +#define OFONO_MAX_MEAS_RES_LIST_COUNT 8
> +
> +enum ofono_cell_type {
> + OFONO_CELL_TYPE_GERAN,
> + OFONO_CELL_TYPE_UTRAN_FDD
> +};
anything we have to keep in mind for LTE here? Or does LTE not matter
for neighbor cell info?
Regards
Marcel
next prev parent reply other threads:[~2011-02-07 19:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 12:05 [PATCH 0/5 v3] Neighbor Cell Info Atom Antti Paila
2011-01-12 12:05 ` [PATCH 1/5 v3] Cell-info: CellInfo DBUS interface definition Antti Paila
2011-02-07 19:27 ` Marcel Holtmann
2011-01-12 12:05 ` [PATCH 2/5 v3] Cell-info: Header file for Neighbor cell info Antti Paila
2011-02-07 19:30 ` Marcel Holtmann [this message]
2011-02-09 6:54 ` Antti Paila
2011-01-12 12:05 ` [PATCH 3/5 v3] Cell-info: Atom for obtaining ECID info of cells Antti Paila
2011-01-12 12:05 ` [PATCH 4/5 v3] Cell-info: New files included in compilation Antti Paila
2011-01-12 12:05 ` [PATCH 5/5 v3] Cell-info: Documentation Antti Paila
2011-02-07 19:24 ` Marcel Holtmann
2011-02-09 7:12 ` Antti Paila
2011-02-02 8:08 ` [PATCH 0/5 v3] Neighbor Cell Info Atom Antti Paila
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=1297107012.1520.446.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 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.