summaryrefslogtreecommitdiff
path: root/build-aux
AgeCommit message (Collapse)AuthorFilesLines
2016-08-01mbim-codegen: fix message name in generated code doc for parse functionsDan Williams1-2/+2
At the point where the codegen happens, {name} is the name of the last function argument, not of the message. Also fix up the documentation to say "Parses and returns parameters" instead of "Create a new request" since parsing doesn't create any requests. New: * Parses and returns parameters of the 'Signal State' notification command in the 'Basic Connect' service. Old: * Create a new request for the 'ErrorRateThreshold' notification command in the 'Basic Connect' service.
2016-07-05Avoid affecting the padding behavior for other services than QMIEmil Ljungdahl2-8/+10
2016-07-05QMI via MBIMCollin McMillan2-8/+8
Signed-off-by: Bjørn Mork <bjorn@mork.no>
2014-07-11build: update copyright years and authors listAleksander Morgado4-5/+5
2013-06-24mbim-codegen: handle reading/writing byte-arrays with shared length fieldAleksander Morgado2-20/+41
2013-06-24mbim-codegen: check message type when parsingAleksander Morgado1-0/+23
2013-06-24mbim-codegen: fix offset after reading 'ref-byte-array'Aleksander Morgado1-1/+1
2013-06-24stk: add support for the STK serviceAleksander Morgado2-9/+21
2013-06-23mbim-codegen: add support for fixed-sized byte arraysAleksander Morgado2-9/+62
2013-06-23mbim-codegen: rename 'byte-array' format to 'unsized-byte-array'Aleksander Morgado2-15/+15
We only used this format type in the Service Activation command, and the format did indeed not have a specific size field for the byte array.
2013-06-23mbim-codegen: allow empty command nameAleksander Morgado1-5/+9
For the case when there is a single command in the service (e.g. USSD)
2013-06-23mbim-codegen: fix byte-array handlingAleksander Morgado1-1/+1
2013-06-21mbim-codegen: support setting arrays of struct referencesAleksander Morgado1-2/+26
2013-06-21mbim-codegen: handle optional fields flagged with 'available-if' in settersAleksander Morgado1-19/+33
2013-06-18mbim-codegen: include service name in methods if not the 'Basic Connect' serviceAleksander Morgado1-1/+4
2013-06-18mbim-codegen: handle 'ref-byte-array' type fieldsAleksander Morgado2-17/+46
Which are byte-arrays specified as offset+length.
2013-06-18mbim-codegen: handle optional fields flagged with 'available-if'Aleksander Morgado1-15/+58
A given MBIM message may contain fields which can be processed in different ways depending on the value of another field. This is the case for e.g. "SMS Read" Query operations, where the list of messages may be formatted as either PDU or CDMA, depending on the value of the 'Format' field. So, we now support to have fields configured like this: { "name" : "Something", "format" : "string" , "available-if" : { "field" : "ConditionField", "operation" : "==", "value" : "0" } }, { "name" : "OtherSomething", "format" : "string" , "available-if" : { "field" : "ConditionField", "operation" : "==", "value" : "1" } }, Meaning that: * Field "Something" will be given if "ConditionField" == 0 * Otherwise, Field "OtherSomething" will be given if "ConditionField" == 1 Note that in the message parser, BOTH fields will be provided, but only one will contain valid data.
2013-06-18mbim-codegen: handle 'byte-array' fields in StructsAleksander Morgado1-1/+24
2013-06-18mbim-codegen: don't setup reader offset if no fields in messageAleksander Morgado1-2/+6
2013-06-06mbim-codegen: support new 'byte-array' typeAleksander Morgado1-8/+41
2013-06-06libmbim-glib: fix reading strings within structsAleksander Morgado2-4/+4
https://bugs.freedesktop.org/show_bug.cgi?id=65452
2013-05-21mbim-codegen: fix generation of struct _free() methodsAleksander Morgado1-1/+2
2013-05-21docs: setup sections for commandsAleksander Morgado3-13/+39
2013-05-21mbim-codegen: generate section for all service specific data typesAleksander Morgado2-0/+37
2013-05-21mbim-codegen: require a 'Service' entry in the data fileAleksander Morgado1-0/+6
2013-05-21mbim-codegen: only generate _free() and _array_free() methods when neededAleksander Morgado3-33/+82
2013-05-21mbim-codegen: document generated structsAleksander Morgado1-0/+46
2013-05-21templates: include documentation for the _get_string() methods in the errorsAleksander Morgado1-0/+8
2013-04-21mbim-codegen: huge refactorAleksander Morgado13-836/+761
I really don't want to split this change into different commits... The overall changes are: * Skip using Value classes, it just complicates the logic a bit here. MBIM is not as complicated as QMI, so it's fine to define all the logic of the generation into 2 main parts: Message creation/parsing and Struct types. * Support for IPv4 and IPv6 values and arrays. If any of the MBIM protocol designers reads this, be aware that I've been cursing you all in the past few days. If you decided to reference IPs as offsets, why the hell don't you do the same when the values are defined within a struct? * Implement the 'IP configuration' message handling * Support for appending structs and arrays of structs into messages. Not fully implemented yet, anyway.
2013-04-21mbim-codegen: don't treat 'IP' as a CamelCase substringAleksander Morgado1-1/+2
2013-04-21mbim-codegen: implement guint64 supportAleksander Morgado4-0/+73
2013-04-21mbim-codegen: allow UUIDs in 'get' containersAleksander Morgado1-0/+5
2013-04-21mbim-codegen: allow UUIDs in 'set' containersAleksander Morgado1-0/+1
2013-04-21mbim-codegen: fix generation of the notification parsersAleksander Morgado1-4/+4
2013-04-21mbim-codegen: allow reading single structs from messagesAleksander Morgado3-21/+54
2013-04-21libmbim-glib: rename 'INDICATION' enum to 'INDICATE_STATUS'Aleksander Morgado1-1/+1
Keeping the same name as in the docs.
2013-04-21mbim-codegen: properly define the 4 types of messages that we may haveAleksander Morgado2-80/+49
MBIM defines 4 types of messages: * Query (host->function) * Set (host->function) * Response (function->host) * Indication (function->host) In particular, the Response message is used as reply for both Query and Set.
2013-04-21mbim-codegen: let the field names be written in CamelCase, as in the docsAleksander Morgado3-15/+17
Write all field names in CamelCase, to match the name given in the docs.
2013-04-21mbim-codegen: skip requiring transaction ID in command request buildersAleksander Morgado1-7/+4
2013-04-21mbim-codegen: simplify APIAleksander Morgado11-210/+276
Instead of per-variable getters, just dump a parser() method which reads all the requested variables from the message. Same logic for the message creators, passing all variables altogether.
2013-02-02mbim-codegen: split Value objectsAleksander Morgado10-111/+556
2013-02-02mbim-codegen: read 'struct' and 'struct-array' fieldsAleksander Morgado1-12/+48
2013-02-02mbim-codegen: add new 'Struct' type generationAleksander Morgado4-18/+270
2013-02-02libmbim-glib: implement 'uuid' type readingAleksander Morgado1-2/+8
2013-02-02mbim-codegen,libmbim-glib: improve general array and variable readingAleksander Morgado2-22/+91
In the general variable reading part, we no longer need specific methods for 'command' or 'command-done' message types. Also, when reading arrays, we will specify separately the variable with the array size and the variable with the actual array contents. Main reason for this is that it seems they don't have to be one after the other. The arrays of guint32 will be '0' terminated. This is useful for parameters where '0' is not an expected value. In general, the size of arrays of guint32 values is given in the output 'size' variable when the array is read.
2013-02-02mbim-codegen: setup code generatorAleksander Morgado7-1/+626
Setup code generation for the request creator and the response getters.
2013-01-21libmbim-glib: setup generation of enum typesAleksander Morgado3-1/+154
2013-01-21libmbim-glib: setup core, status and protocol error typesAleksander Morgado5-0/+127
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-25 07:54:18 +0000