Hey The Intel offer a PCIe device driver to suit my situation. The driver could grab a virtual net port from the PCIe modem, then the user like me could use VLAN to divide the virtual net port in several VLAN ports, the VLAN port can be mapped by socat as AT port and trace port. The map is defined by Intel. But the MM could not add those virtual AT ports and virtual net port. To do that, I change some filter logic that would not influence the architecture now in use. And I add two UDEV flag to set the subsystem and port name of the virtual ports, flags named ID_MM_VIRTUAL_SUBSYSTEMS and ID_MM_VIRTUAL_NAME, the way that the two new flags work just like the already existing UDE flag D_MM_PHYSDEV_UID did. In this way, the MM would support modem devices with virtual ports.
Bjørn Mork <bj...@mork.no> 于2019年3月9日周六 下午8:09写道： > Daniele Palmas <dnl...@gmail.com> writes: > > Il giorno lun 10 dic 2018 alle ore 14:25 Bjørn Mork <bj...@mork.no> ha > scritto: > >> > >> As for Qualcomm based modems: Haven't yet seen any docs for the PCIe > >> interface there either. So I'll assume it is similar to the Intel one. > > > > related to Qualcomm I guess this development > > > > > http://archive.lwn.net:8080/linux-kernel/1524795811-21399-1-git-send-email-sd...@codeaurora.org/ > > > > should be related, but unfortunately it seems that the attempt for > > upstream inclusion stopped. > > Thanks for the pointer! Really interesting and encouraging. > > > Bjørn >
_______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
