Hey Ian,
On Thu, Oct 12, 2017 at 2:39 PM, Ian Jackson
<ijack...@chiark.greenend.org.uk> wrote:
> Aleksander Morgado writes ("Bug#877024: modemmanager should ask before
> messing with serial ports"):
>> This is part of the discussion we had in the MM mailing list for
> Many such modems present as USB serial devices, eg ttyACM or ttyUSB.
> Consequently, modemmanager has the ability to open serial ports and
> probe them to see if they respond to Hayes-style AT commands. That
> functionality is currently triggered automatically by default, even
> for USB serial
Hey Ian!
> Since the maintainers and upstream evidently disagree with this
> tradeoff, it has been necessary for me to ask the TC to step in.
>
The maintainers don't actually disagree. Why didn't you bring this issue to the
ModemManager mailing list in the first place? I personally don't
> It is evident from the history of this bug that the maintainers don't
> agree with this as an approach.
>
I wonder how that is evident given that we (maintainers) still keep the bug
open upstream and discuss about it from time to time...
https://bugs.freedesktop.org/show_bug.cgi?id=85007
I
>
> /* Is the device in the manual-only greylist? If so, return if this is an
> * automatic scan. */
> -if (!manual_scan && g_udev_device_get_property_as_boolean (physdev,
> "ID_MM_DEVICE_MANUAL_SCAN_ONLY")) {
> -mm_dbg ("(%s/%s): port probed only in manual scan", subsys,
>
> However, I have to say that that upstream bug log does not really
> suggest to me that upstream thinks that the current probing behaviour
> is unacceptable. It has been open since 2014 and if the bug is to be
> believed the modemmanager default behaviour in upstream has not
> changed.
>
We
>
> What I'd love to see is a patch that makes modemmanger behave better for
> our users while remaining installed and operational. If it's useful
> enough, it should be acceptable upstream as Debian is not the only
> community affected by this particular problem.
>
This is part of the discussion
Hey Sam,
> It looks like there hasn't been much traffic on this issue in the last
> couple of weeks.
>
Well, I moved the discussion to the ModemManager mailing list and it's
already been discussed there among MM developers.
> My analysis is that the key technical point here is whether it's
>
FYI, already implemented an initial approach, ready for testing:
https://lists.freedesktop.org/archives/modemmanager-devel/2017-October/005969.html
In the Debian case, you would want to use "--filter-policy=STRICT"
when starting ModemManager.
--
Aleksander
https://aleksander.es
On Tue, Oct 17, 2017 at 6:48 PM, Ian Jackson
<ijack...@chiark.greenend.org.uk> wrote:
> Aleksander Morgado writes ("Re: Bug#877024: modemmanager should ask before
> messing with serial ports"):
>> FYI, already implemented an initial approach, ready for testing:
>
>
> As soon as we get this merged to git master, I can tag a 1.8 beta
> release (e.g. 1.7.990). What do you think?
>
FYI, 1.8-rc1 has been tagged with the optional filter policy support included:
https://lists.freedesktop.org/archives/modemmanager-devel/2018-January/006157.html
By default it
>>
>> As soon as we get this merged to git master, I can tag a 1.8 beta
>> release (e.g. 1.7.990). What do you think?
>>
>
> FYI, 1.8-rc1 has been tagged with the optional filter policy support included:
> https://lists.freedesktop.org/archives/modemmanager-devel/2018-January/006157.html
>
> By
>> Also, is there any new maintainer I should talk to regarding
>> integration tasks for this new version?
>
> I've been in touch with Mathieu Trudel-Lapierre (Cc:ed) and he's still
> happy to act as maintainer. He's currently not a DD/DM so needs
> sponsorship for his packages, but that should
I am not yet sure what to do with this issue.
The Arduino is saying that it has an AT-capable ttyACM port, so ModemManager
tries to use the port. I'd like to improve the heuristics to detect this
without falling back to the blacklist, but not sure yet how to reliable do
that. Ideally, the
And this is the suggested change to avoid the issue with the Arduinos wrongly
claiming AT protocol support:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/143
--
Aleksander
https://aleksander.es
The ID_MM_DEVICE_IGNORE udev tag is being ignored in strict filter mode, I'm
trying to change that in this MR for the next MM release:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/138
Iain, could you let me know the full lsusb -v output of that specific DMR
This issue should be hopefully solved in ModemManager 1.10.6 after adding
several new heuristics to the "strict" filter mode.
Also, the logic behind ID_MM_DEVICE_IGNORE was updated and this udev tag is now
applicable in all filter modes (including "strict") and for all device types
(not only
17 matches
Mail list logo
