[RFC] Probing ttys by default

Lars Knudsen larsgk at gmail.com
Mon Mar 24 05:00:51 PDT 2014

On Fri, Mar 21, 2014 at 5:44 PM, Ben Chan <benchan at chromium.org> wrote:

> On Fri, Mar 21, 2014 at 5:14 AM, Aleksander Morgado <
> aleksander at aleksander.es> wrote:
>> +Ben
>> On Fri, Mar 21, 2014 at 1:05 PM, Lars Knudsen <larsgk at gmail.com> wrote:
>> >> sending a QCDM probe to see if the port replies correctly to it. If
>> >> nothing is replied to the probe, the port will finally be discarded.
>> >> This whole sequence may take up several seconds, as for each AT and
>> >> QCDM probe we retry a couple of times. BTW, all this is for MM 1.x,
>> >> the logic in MM 0.6.x is a bit different.
>> >
>> > How many seconds for the version in the current Chromebooks (approx?).
>> > As the Chromebooks are not easily possible to hack a blacklist in - AND
>> they
>> > are considered a std consumer device, they will be most exposed to this
>> > problem.
>> I think it's around 9s for AT probing (3x3s) and 6s for QCDM probing
>> (2x3s).
>> Ben, is the ModemManager package updated regularly in Chromebooks?
>> i.e. how long would it take to have a blacklist update be released in
>> ChromeOS?
> I'd love to say "as soon as we can" :) but there is no guarantee on
> whether or how long a upstream change would be pulled into Chromium OS.
ouch ;) - can you (or someone else) please tell me what I should do to get
our VID/PID listed so the modemmanager doesn't pick it up?


> That said, we've been tracking upstream ModemManager very closely so far
> and pull upstream changes when necessary. As soon as upstream changes are
> pulled, they usually appear in the Chrome OS stable channel in about 6
> weeks, which is our typical release cycle.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/modemmanager-devel/attachments/20140324/e412f43b/attachment.html>

More information about the ModemManager-devel mailing list