Hi Inaky,
> src/smsutil.h |9 +
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/src/smsutil.h b/src/smsutil.h
> index 66ef6f8..baa3eca 100644
> --- a/src/smsutil.h
> +++ b/src/smsutil.h
> @@ -18,6 +18,14 @@
> * Foundation, Inc., 51 Franklin St, Fifth Floor, Bos
Hi Inaky,
> These have been stolen from the Linux kernel source; come pretty handy
> to make build-time consistency checks and thus avoid run-time
> surprises.
> ---
> src/util.h | 28
> 1 files changed, 28 insertions(+), 0 deletions(-)
I still think that using inc
> So my current thinking is to drop any Tech reporting in gprs atom for now. >
> At least until we actually find a usecase for EPSB/CPSB style reporting.
What about the CGREG style tech reporting?
Cheers,
Waldo
___
ofono mailing list
ofono@ofono.org
From: Inaky Perez-Gonzalez
When calling sms_text_prepare(), pass a new argument (srr) that
denotes if the TP-SRR bit in the PDU should be set to request an
Status Report from the Service Center.
---
src/sms.c | 13 ++---
src/smsutil.h |2 ++
2 files changed, 12 insertions(+), 3
From: Inaky Perez-Gonzalez
---
src/smsutil.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/src/smsutil.c b/src/smsutil.c
index cdf28f9..54278ad 100644
--- a/src/smsutil.c
+++ b/src/smsutil.c
@@ -2831,6 +2831,9 @@ static inline GSList *sms_list_append(GSList *l, const
From: Inaky Perez-Gonzalez
Up until now, SMSManager::SendMessage() and SMSMessage::Cancel() where
D-Bus asynchronous. They would perform the D-Bus method return reply
inside the callbacks, as they needed to wait for the operation to
complete.
Relying on previous commits that make the SMS message
From: Inaky Perez-Gonzalez
This hooks __sms_msg_state_change_dbus_signal() into
__ofono_sms_tx_state_set(), so that a D-Bus signal will be emitted
whenever an SMS Message transitions state. This allows a client to
track, if desired, what is going on with the SMS Message it cares about.
With this
From: Inaky Perez-Gonzalez
'msg' gets too confusing: is it the SMS message, a D-Bus message?
---
src/sms.c | 25 +
1 files changed, 13 insertions(+), 12 deletions(-)
diff --git a/src/sms.c b/src/sms.c
index faaacbe..4ad9e61 100644
--- a/src/sms.c
+++ b/src/sms.c
@@ -13
From: Inaky Perez-Gonzalez
Currently this only returns the state of the SMS message.
---
src/sms.c | 43 +++
1 files changed, 43 insertions(+), 0 deletions(-)
diff --git a/src/sms.c b/src/sms.c
index 4ad9e61..77904ad 100644
--- a/src/sms.c
+++ b/src/sms
From: Inaky Perez-Gonzalez
This introduces the ability to cancel a pending SMS message,
accessible via an internal API and over a D-Bus wrapper.
Sending a note to the network to cancel an in-transit message is not
yet implemented.
---
src/sms.c | 57 +++
From: Inaky Perez-Gonzalez
This introduces basic infrastructure to support wait-for-ack in SMS
messages. It consists of a state definition in the state transtition
machine, a wait-for-ack queue (ofono_sms->wfaq) and a flag setting in
which a message is tagged as 'requests wait for ack'.
This doe
From: Inaky Perez-Gonzalez
sms_send_message() is unfolded into:
- sms_msg_send(), a full C interface for SMS sending
- dbus_SendMessage(), which adapts sms_msg_send() to be a D-Bus call
This is done to allow plugins to use the same infrastructure as D-Bus
clients to send SMS messages.
---
src
From: Inaky Perez-Gonzalez
This creates two frunctions, sms_msg_[un]register() which will
add/remove a D-Bus object for each SMS message when in transit.
Future changes make sms_msg_register() need information that is not
available at the time create_tx_queue_entry() is called, thus why
registra
From: Inaky Perez-Gonzalez
This adds state to outgoing/in-transit SMS messages. This will be used
later on for persistence / D-Bus, when the SMS life cycle is expanded.
The state is a variable in the 'struct tx_queue_entry' which gets
updated as messages go through the hoops.
---
src/sms.c | 1
From: Inaky Perez-Gonzalez
This name will be used for persistence and D-Bus object naming. It is
not very humanly readable, but most dependable to avoid collisions.
---
src/sms.c | 12
src/smsutil.h |6 ++
2 files changed, 18 insertions(+), 0 deletions(-)
diff --git a
From: Inaky Perez-Gonzalez
Add a name field that will be used to contain a permanent name for
each SMS message in-transit, to be used for persistent storage and for
D-Bus object naming.
The persist name will be used to denote if persistence has to be
implemented in this in-transit SMS or not.
I
From: Inaky Perez-Gonzalez
---
doc/sms-api.txt | 94 +++
1 files changed, 94 insertions(+), 0 deletions(-)
diff --git a/doc/sms-api.txt b/doc/sms-api.txt
index baa4aa1..a23486a 100644
--- a/doc/sms-api.txt
+++ b/doc/sms-api.txt
@@ -46,3 +46,
From: Inaky Perez-Gonzalez
This patch removes the sequential SMS message identification gig and
replaces it with a 16-bit hash cookie based off message contents.
FIXME: [incomplete] need to figure out how to do so that identical
messages sent to the same number also have a different ID.
Note th
From: Inaky Perez-Gonzalez
For generating unique message naming (for persistence and D-Bus object
naming), we'll be using the address. Instead of repeating the
functions, we reuse the same infrastructure used by the SMS assembly
code.
---
src/smsutil.c |4 ++--
src/smsutil.h |2 ++
2 fil
From: Inaky Perez-Gonzalez
This adds a simple API to use for generating unique IDs for SMS
messages.
---
Makefile.am|5 +-
src/smsutil.c | 191 +++
src/smsutil.h | 82 +++
unit/test-sms-msg-id.c | 212 +
From: Inaky Perez-Gonzalez
Introduce DECLARE_SMS_ADDR_STR(), which declares a string variable of
the right size for passing to sms_assembly_decode_address(). This way
we detach each client having to have the knowledge of what the right
size is, leaving that decission to the infrastructure
provide
From: Inaky Perez-Gonzalez
Modified HACKING and man page to have more formation on what are the
debugging options and how to enable them.
---
HACKING | 10 ++
doc/ofonod.8 |5 -
src/main.c |4 +++-
3 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/HACKI
From: Inaky Perez-Gonzalez
---
doc/standards.txt |8
1 files changed, 8 insertions(+), 0 deletions(-)
create mode 100644 doc/standards.txt
diff --git a/doc/standards.txt b/doc/standards.txt
new file mode 100644
index 000..c4b68eb
--- /dev/null
+++ b/doc/standards.txt
@@ -0,0 +
From: Inaky Perez-Gonzalez
write_file(), as written wasn't transaction-safe; a crash bewtween a
file being open and the buffer being written before a safe close would
leave the file with a set of undetermined contents.
Modified to the file is written to a temporary file name; once
completed, it
From: Inaky Perez-Gonzalez
---
src/smsutil.h |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/src/smsutil.h b/src/smsutil.h
index 66ef6f8..baa3eca 100644
--- a/src/smsutil.h
+++ b/src/smsutil.h
@@ -18,6 +18,14 @@
* Foundation, Inc., 51 Franklin St, Fifth Floor,
From: Inaky Perez-Gonzalez
These have been stolen from the Linux kernel source; come pretty handy
to make build-time consistency checks and thus avoid run-time
surprises.
---
src/util.h | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/src/util.
From: Inaky Perez-Gonzalez
Hi All
This patchset is the current state of my tree that changes the D-Bus
interface for SMS:
- adds object based management of SMS messages
- adds a cancelation operation for in-transit / pending messages
- holds messages waiting for acknoledgement (delivery re
Hi Kristen,
> --- a/src/stkutil.c
> +++ b/src/stkutil.c
> @@ -26,6 +26,7 @@
> #include
> #include
> #include
> +#include
Minor nitpick, but this include is not needed.
>
> #include
>
Regards,
-Denis
___
ofono mailing list
ofono@ofono.org
ht
Hi Daniel,
> This series adds a new property to DCM to export the
> current technology used.
>
So I've been reviewing your patches and also thinking about solving this
technology problem nicely. First a bit of background on the state of hardware
today:
27.007 (The Standard):
- +CREG - Report
Hi Satya,
> I have a third part OEM layer.
> According to the oFono architecture and standards can any one suggest
> the good approach to use the third part OEM layer @ oFono.
oFono is licensed under GPL v2 and as long as your OEM layer is
compatible with GPL v2 you can use it.
Regards
Marcel
Hi all,
I have a third part OEM layer.
According to the oFono architecture and standards can any one *suggest* the
good *approach* to use the third part OEM layer @ oFono.
Regards,
Satya.
___
ofono mailing list
ofono@ofono.org
http://lists.ofono.org/li
31 matches
Mail list logo