On Thu, 2023-04-06 at 11:15 +0000, Mikolaj Kucharski wrote: > On Thu, Apr 06, 2023 at 09:13:27AM +0000, Gerhard Roth wrote: > > > > The Sierra Wireless documentation is available. Alas, switching the > > mode seems far too complex and error prone to perform this inside > > a driver. > > > > When the AT (modem) interface is available, you would have to: > > > > 1) enter password protected command mode with "AT!ENTERCND=passwd" > > > > 2) query the list of modes with "AT!UDUSBCOMP=?". Example result: > > > > 0 - reserved NOT SUPPORTED > > 1 - DM AT SUPPORTED > > 2 - reserved NOT SUPPORTED > > 3 - reserved NOT SUPPORTED > > 4 - reserved NOT SUPPORTED > > 5 - reserved NOT SUPPORTED > > 6 - DM NMEA AT QMI SUPPORTED > > 7 - DM NMEA AT RMNET1 RMNET2 RMNET3 SUPPORTED > > 8 - DM NMEA AT MBIM SUPPORTED > > 9 - MBIM SUPPORTED > > 10 - NMEA MBIM SUPPORTED > > 11 - DM MBIM SUPPORTED > > 12 - DM NMEA MBIM SUPPORTED > > 13 - Config1: comp6 Config2: comp8 NOT SUPPORTED > > 14 - Config1: comp6 Config2: comp9 SUPPORTED > > 15 - Config1: comp6 Config2: comp10 NOT SUPPORTED > > 16 - Config1: comp6 Config2: comp11 NOT SUPPORTED > > 17 - Config1: comp6 Config2: comp12 NOT SUPPORTED > > 18 - Config1: comp7 Config2: comp8 NOT SUPPORTED > > 19 - Config1: comp7 Config2: comp9 SUPPORTED > > 20 - Config1: comp7 Config2: comp10 NOT SUPPORTED > > 21 - Config1: comp7 Config2: comp11 NOT SUPPORTED > > 22 - Config1: comp7 Config2: comp12 NOT SUPPORTED > > > > There is no guarantee that the table doesn't change. And every > > device has a differnt set of supported modes. > > > > 3) select the desired mode with "AT!UDUSBCOMP=X" > > 4) wait for the device to reset itself > > So, I am not sure do I understand the output right, but is this modem > already in correct mode?
Well "correct" depends on what you want ;)
Mode 6 offers AT mode (meaning you have a modem to control with AT-
commands) and QMI. Sadly, none of the supported modes includes
an MBIM (umb) interface. So mode 6 is probably the best one you can pick.
>
>
> AT!ENTERCND="A710"
> OK
> AT!UDUSBCOMP=?
> 0 - HIP DM NMEA AT MDM1 MDM2 MDM3 MS NOT SUPPORTED
> 1 - HIP DM NMEA AT MDM1 MS NOT SUPPORTED
> 2 - HIP DM NMEA AT NIC1 MS NOT SUPPORTED
> 3 - HIP DM NMEA AT MDM1 NIC1 MS NOT SUPPORTED
> 4 - HIP DM NMEA AT NIC1 NIC2 NIC3 MS NOT SUPPORTED
> 5 - HIP DM NMEA AT ECM1 MS NOT SUPPORTED
> 6 - DM NMEA AT QMI SUPPORTED
> 7 - DM NMEA AT RMNET1 RMNET2 RMNET3 SUPPORTED
> 8 - Win8 Std Net SUPPORTED
>
>
> OK
> AT!UDUSBCOMP?
> !UDUSBCOMP: 6
>
> OK
>
>
> That is on kernel with the below diff applied - on line change to umsm.c
>
> # dmesg
> ...
> umsm0 at uhub4 port 3 configuration 1 interface 0 "Sierra Wireless,
> Incorporated MC7750" rev 2.00/0.06 addr 3
> ucom0 at umsm0
> umsm1 at uhub4 port 3 configuration 1 interface 2 "Sierra Wireless,
> Incorporated MC7750" rev 2.00/0.06 addr 3
> ucom1 at umsm1
> umsm2 at uhub4 port 3 configuration 1 interface 3 "Sierra Wireless,
> Incorporated MC7750" rev 2.00/0.06 addr 3
> ucom2 at umsm2
> umsm3 at uhub4 port 3 configuration 1 interface 8 "Sierra Wireless,
> Incorporated MC7750" rev 2.00/0.06 addr 3
> ucom3 at umsm3
>
>
> > >
> > > Index: umsm.c
> > > ===================================================================
> > > RCS file: /cvs/src/sys/dev/usb/umsm.c,v
> > > retrieving revision 1.125
> > > diff -u -p -r1.125 umsm.c
> > > --- umsm.c 2 Apr 2023 23:57:57 -0000 1.125
> > > +++ umsm.c 6 Apr 2023 08:40:30 -0000
> > > @@ -271,6 +271,7 @@ static const struct umsm_type umsm_devs[
> > > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_AIRCARD_340U}, 0},
> > > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_AIRCARD_770S}, 0},
> > > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC7455}, 0},
> > > + {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC7700}, 0},
> > >
> > > {{ USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM5320}, 0},
> > > {{ USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM7600E}, 0},
> > >
> >
>
smime.p7s
Description: S/MIME cryptographic signature
