| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
rfcomm devices seem to be created as 'virtual' devices first, without
any parents, then moved to the right place in the device tree. So
handle moves too; if the modem was already found in the 'add' phase
it'll be ignored in the move phase.
|
|
|
|
Two hacks here:
1) rfcomm ports don't have an easily accessible driver name, so we just
match the parent's subsystem to 'bluetooth' and use that
2) libgudev doesn't seem be be able to get the rfcomm device's device file,
which would normally be /dev/rfcommX. Oh well, we don't use the device file
yet anyway
|
|
|
|
Found by Eugene Crosser <crosser@average.org>
|
|
It's only relevant when the port is open anyway, and marking the port
disconnected in nm_serial_port_close(), which used to be called from
the finalize() function, would trigger the notifier when stuff was
already cleaned up. So move the nm_serial_port_close() call to
dispose() and remove the connected notifier before we clean the
port up.
|
|
Otherwise it could still be connected when the port was opened again,
and subsequent calls for stuff could fail.
|
|
Previously, a few operations (like disable) could trigger a modem
flash in parallel with another flash. That's wrong, don't allow
that. At the same time, add in finer-grained error checking on
serial port speed operations, and fix a GSM generic bug that would
send the POWER_UP string on disable.
|
|
fix device removal event handling to remove modems
if the associated parent usb device is removed
|
|
|
|
|
|
|
|
Specifically, SupportedModes, SupportedBands, and SMS completeness changes.
|
|
|
|
Use the same enum for set/get of band and mode, as for exposing the
device's capabilities.
|
|
Sierra 580 returns "+CSS: 0, Z , 0" when not associated. Handle that.
|
|
Like the Sanyo SCP-3800 (Sprint Katana LX). Make up your freakin'
mind people, either prefix *all* responses with the command stem,
or don't. But just pick one dammit.
|
|
|
|
So many modems just don't implement carrier detect that it makes
the previous 'connected' logic useless, so base it off connect/disconnect
and fix up a few places that didn't check connect status before
trying to send commands. Also ensure the serial port is unlocked
for PPP to use when connected.
|
|
ZTE modems need to use udev rules to assign port type hints,
so generalize that and port all the plugins over to suggested
port types in the MMModem interface's grab_port() function.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It helps make the supports/grab callchain less crappy to look at
in gdb by ensuring that the supports chain unwinds before the grab
happens, and also ensures that we use the right subsys/name variables
rather than depending on ones the plugin provided to supports_callback,
that may go be freed by the plugin somewhere in grab_port().
|
|
|
|
Don't mis-use udev's ID_BUS key.
|
|
|
|
|
|
|
|
|
|
git://gitorious.org/~torgny_j/modemmanager/mbm-mainline.git
And other cleanups by Dan.
|
|
Allow plugins to perform asynchronous port detection, and to defer port detection
until later. This moves the prober bits into MMPluginBase so that all plugins
can take adavantage of it only when needed; the probing is not done at udev time.
Furthermore, plugins like Novatel can flip the secondary ports over the AT mode
through deferred detection, by deferring the secondary ports until the main port
has been detected and AT$NWDMAT has been sent.
This commit also finishes the port of the rest of the plugins (except mbm) over
to the new port detection methods and plugin API.
|
|
|
|
Otherwise, if something else is mistakenly holding the serial port open at
the same time as this MMSerialPort, you get a stream of reads of size 0 and
effectively hang modem-manager.
|
|
|
|
We'll need it in more than one place, so make it generic.
|
|
Create a base MMPort class to handle both tty and net ports generically,
and move plugins over to that. Also port the 'hso' plugin to udev.
|
|
|
|
|
|
|
|
|
|
It's generic, everything implements some variant of +GMM, +GMR, and +GMI.
|
|
|
|
|
|
|
