[RFC] Probing ttys by default
benchan at chromium.org
Fri Mar 21 09:44:34 PDT 2014
On Fri, Mar 21, 2014 at 5:14 AM, Aleksander Morgado <
aleksander at aleksander.es> wrote:
> 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
> > 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
> Ben, is the ModemManager package updated regularly in Chromebooks?
> i.e. how long would it take to have a blacklist update be released in
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.
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...
More information about the ModemManager-devel