Re: MM 0.6.0 conflicts with USB GPS device?

[Dan Williams <dcbw redhat com>]

On Fri, 2013-06-07 at 18:26 +0200, Aleksander Morgado wrote:
> On 06/07/2013 06:16 PM, poma wrote:
> > > > Maybe in the very distant future, MM would not probe the serial
> > > > > > device at all - instead I imagine a "serial detector" software
> > > > > > component, that does all kind of probing and only sends signals on
> > > > > > the DBus about the result ("modem found at /dev/ttyUSB0", "GPS
> > > > > > found at /dev/ttyUSB1", "voltmeter found...").
> > > >
> > > > In MM git master, USB<->RS232 adaptors are never probed by default when
> > > > detected, so there shouldn't be any direct conflict. Instead, they will
> > > > only be probed to look for modems if Scan() is called explicitly.
> > Are you saying that there is no more need for acrobatics[1] regarding
> > analog modems and UPSes connected to the serial ports or via adapters.
>
> That should be the case, yes.
>
> Platform RS232 ports need to be explicitly tagged with
> ID_MM_PLATFORM_DRIVER_PROBE to get automatically probed; and USB devices
> listed in the greylist of USB<->Serial devices won't get automatically
> probed by MM, only when Scan() is called.

That said, if some UI decided to add a "Look for all modems" button,
then you'd still have problems if a non-modem was connected to one of
the greylisted serial adapters.  It doesn't mean MM won't touch them, it
just means that MM won't touch them *by itself*.  But if there's some UI
or some script that tells MM to do so, then MM will because it was told
to.

Dan