On Thu, 7 Sept 2023 at 23:27, Nicholas Smith <nicho...@nbembedded.com> wrote: > > Yeah the quectel hack job is not fun, have to load their driver too. I was > forced to because I couldn’t get good speeds on a RM500q nor do bridge mode > without it. Has that changed in recent versions of MM and qmi_wwan? Would > really love to retire that hack
I just got the ModemManager and everything else backport to 19.07, all I did test so far was mmcli and some basic functions. I am using their driver for MHI as QCA-s 5.4 kernel MHI WWAN support is non-existent, but still need to test that path as I was just using qmi_wwan as I would really love to avoid their abomination with the qmi_wwan_q mess Quectel has. Regards, Robert > > > All the best, > Nicholas Smith > > > On Thu, 7 Sep 2023 at 23:55, Robert Marko <robima...@gmail.com> wrote: >> >> On Wed, 6 Sept 2023 at 23:10, Nicholas Smith <nicho...@nbembedded.com> wrote: >> > >> > Hey, >> > >> > The idea of modemmanager is that it’s an abstract generic manager for any >> > modem that uses MBIM, QMI or sometimes AT commands. It’s like >> > networkmanager in that sense; you don’t care what brand your NIC is or >> > whether it’s wireless, networkmanager just works. >> > >> > Only issue up until recently has been notifying hotplug and netifd of >> > events that MM is aware of, as well as the size (about 2MB for a full >> > installation). But there has been some good work by Florian E recently >> > around that, and you get the lite option by default so size is kept to a >> > minimum. >> >> Hi, >> This is basically why I want to use modemmanager, size is not an issue >> so I spent some time backporting it as well as libqmi, libmbim and >> libqrtr-glib to 19.07. >> Fingers crossed it actually works so I dont have to use the Quectel hackjob. >> >> Regards, >> Robert >> > >> > All the best, >> > Nicholas Smith >> > >> > >> > On Thu, 7 Sep 2023 at 04:53, Robert Marko <robima...@gmail.com> wrote: >> >> >> >> On Wed, 6 Sept 2023 at 20:22, Philip Prindeville >> >> <philipp_s...@redfish-solutions.com> wrote: >> >> > >> >> > Hi all, >> >> > >> >> > I was reading through some of the online documentations as I try to >> >> > bring up a 5G modem w/ Verizon and modemmanager, and bounced between >> >> > various settings (it's a Quectel EM120R-GL modem for the moment until >> >> > something better arrives), trying to decide if I wanted to use QMI or >> >> > MBIM, if I should use the "qui" protocol directly or "modemmanager" >> >> > instead... And thought it would be nice to have 2 or 3 groups of meta >> >> > packages that you select and the rest gets taken care of for you by >> >> > dependencies. >> >> > >> >> > In particular: >> >> > >> >> > https://openwrt.org/docs/guide-user/network/wan/wwan/ltedongle >> >> > >> >> > Talks about kmod's and user-space tools necessary for QMI, different >> >> > packages necessary for MBIM, and then what's needed for NCM (anyone >> >> > still using that or 3G)... >> >> > >> >> > General debugging tools like minicom so you don't need to use "echo" or >> >> > "socat"... >> >> > >> >> > Before I start on the effort (shouldn't take more than a couple of >> >> > hours), does anyone object to the project (or conversely, is anyone >> >> > willing to review and sign-off on it)? >> >> >> >> I would find this rather useful, to have meta-packages for modems >> >> instead of having to select everything manually. >> >> I am working on RM520N-GL support at work (For QSDK, dont ask why) and >> >> I am not sure whether I want to use the mess called Quectel CM(Vendor >> >> tool) or modemmanager. >> >> >> >> Regards, >> >> Robert >> >> > >> >> > Eckert: thanks for the quick turnaround on the MBIM-disabled issue when >> >> > building modemmanager... >> >> > >> >> > If anyone is wondering, no, I still don't have wireless up... not sure >> >> > if that hardware is in a weird persistent state (a lot of settings get >> >> > saved to NVRAM) or if modemmanager doesn't handle certain corner cases >> >> > (although Verizon on a Quectel EM120R-GL using QMI would seem to be >> >> > pretty mainstream). Please reach out to me if you have any >> >> > troubleshooting suggestions, and I'll update the docs appropriately >> >> > when I'm done. >> >> > >> >> > Thanks, >> >> > >> >> > -Philip >> >> > >> >> > >> >> > _______________________________________________ >> >> > openwrt-devel mailing list >> >> > openwrt-devel@lists.openwrt.org >> >> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel >> >> >> >> _______________________________________________ >> >> openwrt-devel mailing list >> >> openwrt-devel@lists.openwrt.org >> >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
