some more info:
> karl@karl-acer2:~$ mmcli -m 24
> --
> General | dbus path: /org/freedesktop/ModemManager1/Modem/24
>| device id: 20a6ea01070a5cfbf57a23af244a7645728eef2b
> --
> Hardware | manufacturer: Huawei
Dear All...
I have now retried getting that blasted thing to work in the current
buster kernel, 4.19.0-2-amd64 but still same problem.
I applied the cdc_mbim_info_avoid_altsetting_toggle patch to no avail.
Cant get any data down, some packages are sent out.
Please help, my original post
matthew stanger writes:
>>
>> Forgot to comment on this. They use a SIMCom SIM7100E or SIM7100A WWAN
>> module according to
>> https://developer.puri.sm/Librem5/Hardware_Reference.html
>
> Oh that's new, they where going to use the PLS8 with PCIe. That's what got
> my attention.
That's also a
>
> Forgot to comment on this. They use a SIMCom SIM7100E or SIM7100A WWAN
> module according to
> https://developer.puri.sm/Librem5/Hardware_Reference.html
Oh that's new, they where going to use the PLS8 with PCIe. That's what got
my attention.
On Fri, Mar 15, 2019 at 10:04 AM Bjørn Mork
On Fri, 2019-03-15 at 16:34 +0100, Sven Schwermer wrote:
> Hi all,
>
> > On 15 Mar 2019, at 16:03, matthew stanger
> > wrote:
> >
> > Anyway, the only thing I can think of is a timing issue with the
> > modem
> > firwmare and network registration or initial bearer setup or
> > something
> >
matthew stanger writes:
> I thought
> the (Librem 5 Linux Phone) ( https://puri.sm/products/librem-5/ ) was
> already using MM with PCIe? I know that's their plan.
Forgot to comment on this. They use a SIMCom SIM7100E or SIM7100A WWAN
module according to
matthew stanger writes:
> Is this thread implying the MM doesn't support PCIe in general?
No. Only that kernel drivers are required.
The situation for USB devices is good because there are only a few
host<->device protocols in use, and those protocols are well known by
now. We even have a
Hi all,
> On 15 Mar 2019, at 16:03, matthew stanger wrote:
>
> Anyway, the only thing I can think of is a timing issue with the modem
> firwmare and network registration or initial bearer setup or something
> like that. Perhaps MM isn't querying some ready state well enough, or
> the modem
Is this thread implying the MM doesn't support PCIe in general? I thought
the (Librem 5 Linux Phone) ( https://puri.sm/products/librem-5/ ) was
already using MM with PCIe? I know that's their plan.
On Fri, Mar 15, 2019 at 4:01 AM Bjørn Mork wrote:
> 王道之 writes:
>
> > Intel have the plan to
On Fri, 2019-03-15 at 14:20 +0100, Sven Schwermer wrote:
> Hi again,
>
> I did some more work and now I am able to connect manually (without
> ModemManager). All that’s required is the AT^SWWAN=1,1 command if the
> APN is already correctly configured. I checked this via AT+CGDCONT?.
> Note, that
Hi again,
I did some more work and now I am able to connect manually (without
ModemManager). All that’s required is the AT^SWWAN=1,1 command if the APN is
already correctly configured. I checked this via AT+CGDCONT?. Note, that this
only works for CID=1. After changing the APN for CID=1, the
王道之 writes:
> Intel have the plan to opensource the PCIe driver. I would put it here
> once the Intel opensource it.
Looking forward to that!
Bjørn
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
Hey
I am trying to find a way to use the AT ports or mbim ports that occupied
by MM as all the device ports were used by MM. eg. I want send AT command
to the modem, but MM occupies the AT port. Is there any way to make MM stop
using the AT port for a while but not kill the MM? To do that, maybe
Intel have the plan to opensource the PCIe driver. I would put it here
once the Intel opensource it.
But the driver do not offer a cdc_mbim port, just offer AT port. In MM, it
would manage with the base modem. And the VLAN ID map is defined by Intel,
so I do not think the driver could be use in
Now you made me really curious. That sounds a lot like the cdc_mbim userspace
ABI. And I didn't expect anyone to copy that since I don't think anyone is
happy with it. Including me.
Or are they simply creating a usb mbim device? That would make sense. But then
it should have worked with mm, so
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
Hi Matthew,
Thanks for the update!
> I've had a long back-and-forth with the vendor but basically we still can't
> get the demo board reliably working with basic AT commands.
> In short I'm still working on it but really don't understand why this modem
> model continues to prove so difficult
17 matches
Mail list logo
