On Sat, 2017-03-25 at 19:32 +0100, Aleksander Morgado wrote:
> Hey Dan, Daniele, Carlo & everyone,
>
> This series of patches tries to implement proper flow control
> settings on the serial port, and is based on letting MM detect which
> are the supported modes with AT+IFC=?. This makes it unneces
On Tue, Mar 28, 2017 at 10:57 AM, carlo wrote:
>> BTW; does the PLATFORM_DRIVER_PROBE tag work if you tag
>> "/devices/pnp0/00:05/" instead of "/devices/pnp0/00:05/tty/ttyS0"?
>
>
> uhm, no, this way ttyS0 is not whitelisted, but it works with
> "/devices/pnp0/00:05/*"
> (or "/devices/pnp0/00:05/t
I assume you have the LABEL in a new line? i.e. this:
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"
Yes, correct :D
Baudrate? The modem should use 57600bps, as that is what MM expects.
Oh, s
On Tue, Mar 28, 2017 at 10:21 AM, carlo wrote:
> Oops
> also a == for DEVPATH test
>
Oh, yeah, and that :)
> 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"
>
I assume you have the LABEL in
Thanks to Daniele's suggestion, I changed modem baudrate to 57600 and
now it works fine
Carlo
On 28/03/2017 10:21, carlo wrote:
> Ok, please retry after adding the missing comma between the DEVPATH
and the ENV:
Oops
also a == for DEVPATH test
ACTION!="add|change|move", GOTO="mm_serial_end
> Ok, please retry after adding the missing comma between the DEVPATH
and the ENV:
Oops
also a == for DEVPATH test
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"
Now ttyS0 is whitelisted cor
On Tue, Mar 28, 2017 at 9:01 AM, Carlo Lobrano wrote:
> Here it is
>
> $ udevadm info -p /sys/class/tty/ttyS0
> P: /devices/pnp0/00:05/tty/ttyS0
> N: ttyS0
> E: DEVNAME=/dev/ttyS0
> E: DEVPATH=/devices/pnp0/00:05/tty/ttyS0
> E: ID_MM_CANDIDATE=1
> E: MAJOR=4
> E: MINOR=64
> E: SUBSYSTEM=tty
> E: T
Here it is
$ udevadm info -p /sys/class/tty/ttyS0
P: /devices/pnp0/00:05/tty/ttyS0
N: ttyS0
E: DEVNAME=/dev/ttyS0
E: DEVPATH=/devices/pnp0/00:05/tty/ttyS0
E: ID_MM_CANDIDATE=1
E: MAJOR=4
E: MINOR=64
E: SUBSYSTEM=tty
E: TAGS=:systemd:
E: USEC_INITIALIZED=955641
On Mon, 27 Mar 2017 at 20:44 Aleksa
On Mon, Mar 27, 2017 at 6:04 PM, carlo wrote:
>> Does this work?
>>
>> # cat < /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 con
> Does this work?
# cat < /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
On Mon, Mar 27, 2017 at 3:52 PM, Carlo Lobrano wrote:
> I've got some problems configuring MM for this test. This is the message I
> got just after applying the patch:
>
> ModemManager[28005]: [1490621030.009049] [mm-base-manager.c:263]
> device_added(): (tty/ttyS0): adding device at sysfs path:
Hi Aleksander,
I've got some problems configuring MM for this test. This is the message I
got just after applying the patch:
ModemManager[28005]: [1490621030.009049] [mm-base-manager.c:263]
device_added(): (tty/ttyS0): adding device at sysfs path:
/sys/devices/pnp0/00:05/tty/ttyS0
ModemManager[2
12 matches
Mail list logo
