| Age | Commit message (Collapse) | Author |
|---|
|
sms_parse_pdu(): Protocol ID doesn't actually affect decoding, so
don't fret about its value.
ChromeOS:
Change-Id: Ia4cb20c415aed1026bb7b8dd4daa8ae53dd749e8
|
|
Chromium:
Change-Id: I0629706985f273832ac3662acb260388d0e6ed83
|
|
|
|
If the modem sends the same notification on more than one port,
make sure we don't send a signal out to clients more than once.
|
|
|
|
|
|
It was being used in several places with different static implementations
|
|
|
|
Huawei will need this.
|
|
Instead of having two places that custom init stuff got processed
(a hook in the MMPluginBase class itself and a callback too) just
use a callback, and simplify it somewhat so that the plugin tracks
how many tries it cares about and what to do based on the response
or error.
|
|
Make sure all pending work, if any, is torn down when closing
the port, since it's closed, and is likely going to get unreffed
soon and we don't want anything running after the port is dead.
|
|
If the modem for some reason returns ERROR for a +CPIN when it's
unlocked, and subsequent PIN post-unlock pin checks return READY,
just treat the modem as unlocked don't return the +CPIN error.
|
|
|
|
|
|
|
|
Change interface to take the number of GSM characters
rather than the number of octets, so that it is possible to
distinguish the 7-character and 8-character cases.
|
|
Since we don't allow properties to be passed into the serial port
create routines we don't want a construct-only property here.
|
|
It's only used during probing where some port types (Sierra CnS
and some Icera devices) may send streams of data that we can't
understand until we close the port. It interferes with some SMS
operations, so turn it off for ports opened after probing.
|
|
|
|
|
|
Let modems we know don't suck use a zero send-delay at probe time,
which greatly reduces time required to probe AT-compatible ports.
|
|
Otherwise we don't get the expected "Incorrect password" error if the
PIN is wrong, just a generic error.
|
|
Avoids additional USB latency and groups the whole command into one
USB packet.
BUG=chromium-os:13506
|
|
|
|
New mm_serial_parser_v1_set_custom_regex() method.
|
|
So that cached values can be returned if querying while the port is connected.
|
|
If a port returns EAGAIN on write attempts, previously the code would
spin and attempt to resend the failed byte after send_delay
microseconds. This resulted in up to 3 second hard blocks in
the serial code when sending to ports that don't respond. While
in this blocking loop no other events or dbus commands could be
processed.
Instead, send each byte and reschedule sending the next byte in
send_delay microseconds, so that we can process other events in between
attempts to write to stupid ports.
This doesn't hugely decrease the amount of time that probing
requires, since we still need to probe all ports of the device
before exporting the modem to D-Bus, but it does let MM find
responsive ports much more quickly, and ensures that MM doesn't
block any D-Bus requests.
|
|
|
|
The new and old state arguments were flipped.
|
|
Isn't really needed since it's just the same as any other net
device port type.
|
|
BUG=chrome-os-partner:2394
TEST=gmerge modemmanager, watch logs, see detected as Samsung modem, connect to AT&T network
Review URL: http://codereview.chromium.org/6614026
Patch from Jun Woo Lee <jw86.lee@samsung.com>.
Change-Id: I913628ff4a1cd16c8180e3c808644b0134e69e31
|
|
From an HP un2400;
GMR: D1020-SUUAASFA-4352 1 [Apr 14 2008 18:00:00]
GMM: 88
|
|
|
|
|
|
It's part of the D-Bus API, so it needs to be implemented somewhere
even if it's not used yet.
|
|
|
|
Since platform devices don't usually have them.
|
|
And add new reason codes to the C headers.
|
|
|
|
We actually don't care about the result here. But we do in other
places, so we want to keep the warning in general.
|
|
|
|
|
|
|
|
|
|
We want to enable unsolicited responses on secondary ports too,
so that if the modem only sends unsolicited responses on the ports
on which they were enabled, that we can get resposnes off the
secondary port when the primary port is connected. But we can't
always trust devices to actually send them on the secondary port,
so we enable the unsolicited responses on both the primary and
secondary ports just in case.
|
|
|
|
Make it more flexible, add logging to a file, and absolute and
relative timestamps.
|
|
|
|
Based on a patch by Elly Jones from Google.
|
|
(testcases by dcbw)
|
