summaryrefslogtreecommitdiff
path: root/data/mbim-service-basic-connect.json
AgeCommit message (Collapse)AuthorFilesLines
2014-03-06libmbim-glib: fix typo in MBIM_CID_DEVICE_SERVICE_SUBSCRIBE_LISTBen Chan1-1/+1
This patch renames 'MBIM_CID_DEVICE_SERVICE_SUBSCRIBER_LIST' to 'MBIM_CID_DEVICE_SERVICE_SUBSCRIBE_LIST' to be consistent with the MBIM specification. This CID is for subscribing notifications for CIDs that the host is interested in, and is not related to mobile 'subscriber'.
2014-03-03basic-connect: implement 'Emergency Mode' notification handlingBen Chan1-1/+4
2014-03-03basic-connect: fix notification code generationBen Chan1-12/+12
2014-02-26basic-connect: implement 'Subscriber Ready Status' notification handlingBen Chan1-1/+16
2014-02-20basic-connect,stk: make naming more consistentBen Chan1-4/+4
Also fixes a few indentation issues.
2013-06-24basic-connect: implement 'Multicarrier Providers' command handlingAleksander Morgado1-1/+25
2013-06-24basic-connect: implement 'IP Packet Filters' command handlingAleksander Morgado1-1/+41
2013-06-24basic-connect: implement 'Emergency Mode' command handlingAleksander Morgado1-1/+13
2013-06-24basic-connect: implement 'Network Idle Hint' command handlingAleksander Morgado1-1/+13
2013-06-23basic-connect: implement 'Packet Statistics' command handlingAleksander Morgado1-1/+24
2013-06-23mbim-codegen: rename 'byte-array' format to 'unsized-byte-array'Aleksander Morgado1-2/+2
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-21basic-connect: implement 'Device Service Subscriber List' command handlingAleksander Morgado1-1/+28
2013-06-06basic-connect: implement 'Service Activation' command handlingAleksander Morgado1-0/+13
Also add unit tests for the message builder and response parser, as we're testing the new 'byte-array' type reader.
2013-06-06basic-connect: implement 'Visible Providers' command handlingAleksander Morgado1-0/+14
2013-06-06basic-connect: implement 'Preferred Providers' command handlingAleksander Morgado1-0/+24
2013-06-06basic-connect: implement 'Home Provider' command handlingAleksander Morgado1-0/+29
2013-05-21mbim-codegen: require a 'Service' entry in the data fileAleksander Morgado1-0/+4
2013-04-21mbim-codegen: huge refactorAleksander Morgado1-3/+136
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-21basic-connect: implement 'Packet Service' command handlingAleksander Morgado1-0/+34
2013-04-21basic-connect: implement 'Connect' command handlingAleksander Morgado1-0/+72
2013-04-21basic-connect: implement 'Provisioned Contexts' command handlingAleksander Morgado1-0/+55
2013-04-21basic-connect: implement 'Register State' command handlingAleksander Morgado1-0/+62
2013-04-21basic-connect: implement 'Signal State' command handlingAleksander Morgado1-0/+32
2013-04-21basic-connect: implement 'Pin List' command handlingAleksander Morgado1-0/+49
2013-04-21mbim-codegen: properly define the 4 types of messages that we may haveAleksander Morgado1-106/+111
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 Morgado1-40/+40
Write all field names in CamelCase, to match the name given in the docs.
2013-04-21mbim-codegen: simplify APIAleksander Morgado1-35/+32
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-04-21basic-connect: new 'MbimRadioSwitchState' enumAleksander Morgado1-2/+2
2013-04-07basic-connect: fix some field namesAleksander Morgado1-13/+13
2013-04-07basic-connect: implement 'Pin' command handlingBjørn Mork1-0/+31
Signed-off-by: Bjørn Mork <bjorn@mork.no>
2013-04-07basic-connect: implement 'Radio State' query handlingBjørn Mork1-0/+11
Signed-off-by: Bjørn Mork <bjorn@mork.no>
2013-02-02libmbim-glib,basic-connect: implement 'Device Services' query handlingAleksander Morgado1-2/+16
2013-02-02mbim-codegen: add new 'Struct' type generationAleksander Morgado1-1/+19
2013-02-02mbim-codegen,libmbim-glib: improve general array and variable readingAleksander Morgado1-2/+6
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 Morgado1-0/+57
Setup code generation for the request creator and the response getters.