>  Does this work?

# cat <<EOF > /lib/udev/rules.d/78-mm-serial.rules
ACTION!="add|change|move", GOTO="mm_serial_end"
DEVPATH=”/devices/pnp0/00:05/tty/ttyS0” ENV{ID_MM_PLATFORM_DRIVER_PROBE}=”1”
LABEL=”mm_serial_end"
EOF
# udevadm control --reload
# udevadm trigger
// Relaunch MM

unfortunately no, I got the same result

Carlo
On 27/03/2017 17:38, Aleksander Morgado wrote:
On Mon, Mar 27, 2017 at 3:52 PM, Carlo Lobrano <c.lobr...@gmail.com> wrote:
I've got some problems configuring MM for this test. This is the message I
got just after applying the patch:

ModemManager[28005]: <debug> [1490621030.009049] [mm-base-manager.c:263]
device_added(): (tty/ttyS0): adding device at sysfs path:
/sys/devices/pnp0/00:05/tty/ttyS0
ModemManager[28005]: <debug> [1490621030.009100]
[kerneldevice/mm-kernel-device-udev.c:474] kernel_device_is_candidate():
(tty/ttyS0): port's parent platform driver is not whitelisted

I saw the other email about udev rule to whitelist the serial device, but it
seems I could not get it right.

This is the udevadm info about the serial that responds to AT commands

$ udevadm info --attribute-walk /sys/class/tty/ttyS0

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

   looking at device '/devices/pnp0/00:05/tty/ttyS0':
     KERNEL=="ttyS0"
     SUBSYSTEM=="tty"
     DRIVER==""

   looking at parent device '/devices/pnp0/00:05':
     KERNELS=="00:05"
     SUBSYSTEMS=="pnp"
     DRIVERS=="serial"
     ATTRS{id}=="PNP0501"

   looking at parent device '/devices/pnp0':
     KERNELS=="pnp0"
     SUBSYSTEMS==""
     DRIVERS==""

I tried adding the line

     DRIVERS=="serial", ENV{ID_MM_PLATFORM_DRIVER_PROBE}="1"

to 77-mm-platform-serial-whitelist.rules and reloading the rules, but it
doesn't seem the correct way to do it.

What am I doing wrong?
Does this work?

# cat <<EOF > /lib/udev/rules.d/78-mm-serial.rules
ACTION!="add|change|move", GOTO="mm_serial_end"
DEVPATH=”/devices/pnp0/00:05/tty/ttyS0” ENV{ID_MM_PLATFORM_DRIVER_PROBE}=”1”
LABEL=”mm_serial_end"
EOF
# udevadm control --reload
# udevadm trigger
// Relaunch MM



_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Reply via email to