Den 29. aug. 2012 19:59, skrev Marius Kotsbak:
I did, but maybe hit a bad timing. Anyway, master version now builds
and connection still works with my ZTE modem, but I got a crash with
the Sierra modem (which is not Icera):
ERROR:mm-port-probe.c:531:serial_probe_at_icera_result_processor:
ass
On Tue, 2012-08-21 at 11:44 +0200, Aleksander Morgado wrote:
> Hey Bjørn,
>
> >>> >> 3) I still wonder how to handle the usb => usbmisc transition. For now
> >>> >> I've just been searching and replacing, but that is of course not
> >>> >> supportable. And it isn't really a one-to-one replacemen
On 08/30/2012 02:10 PM, Marius Kotsbak wrote:
> Den 30. aug. 2012 14:05, skrev Aleksander Morgado:
>> On 08/30/2012 01:30 PM, Marius Kotsbak wrote:
>>> For the Sierra MC7710, it also does not work:
>>>
>>> $ mmcli -m 0 --set-preferred-mode 4g --set-allowed-modes 4g
>>>
>>> That is also strange, as
> And note: you are the first one testing the port of the Sierra plugin
> (so thanks thanks); but be aware that more nasty issues may happen, just
> report them if possible.
Forgot to say; there are some additional fixes to get ported from
MM06/MM05 to git master regarding the Sierra plugin (disa
>>
>> I did, but maybe hit a bad timing. Anyway, master version now builds and
>> connection still works with my ZTE modem, but I got a crash with the
>> Sierra modem (which is not Icera):
>>
>> ERROR:mm-port-probe.c:531:serial_probe_at_icera_result_processor:
>> assertion failed: (g_variant_is_of
Den 30. aug. 2012 14:05, skrev Aleksander Morgado:
On 08/30/2012 01:30 PM, Marius Kotsbak wrote:
For the Sierra MC7710, it also does not work:
$ mmcli -m 0 --set-preferred-mode 4g --set-allowed-modes 4g
That is also strange, as it is possible to set preference using custom
AT command AT!SELRAT
On 08/30/2012 01:30 PM, Marius Kotsbak wrote:
>
> For the Sierra MC7710, it also does not work:
>
> $ mmcli -m 0 --set-preferred-mode 4g --set-allowed-modes 4g
>
> That is also strange, as it is possible to set preference using custom
> AT command AT!SELRAT (or maybe it is only allowed modes?).
Den 30. aug. 2012 00:24, skrev Aleksander Morgado:
>>>I actually got the connection up now using the method above (mmcli +
>>>ifup wwan0) so it seems to be close to functional now.
>>>
>>Regarding connectivity; QMI-powered MM is fully functional. Missing
>>things include messaging and location,
Den 30. aug. 2012 00:24, skrev Aleksander Morgado:
I did, but maybe hit a bad timing. Anyway, master version now builds and
connection still works with my ZTE modem, but I got a crash with the
Sierra modem (which is not Icera):
ERROR:mm-port-probe.c:531:serial_probe_at_icera_result_processor:
a
>>> I actually got the connection up now using the method above (mmcli +
>>> ifup wwan0) so it seems to be close to functional now.
>>>
>> Regarding connectivity; QMI-powered MM is fully functional. Missing
>> things include messaging and location, which are scheduled for next
>> weeks.
>
> Okay.
Den 29. aug. 2012 15:52, skrev Aleksander Morgado:
I actually got the connection up now using the method above (mmcli +
ifup wwan0) so it seems to be close to functional now.
Regarding connectivity; QMI-powered MM is fully functional. Missing
things include messaging and location, which are sc
>> More or less, yes. You have the 'mmcli' utility in that branch,
> though,
>> so you can skip writing raw dbus-send commands and play with the cli
>> instead, like this (assuming only one modem connected, so index 0):
>>
>> Show modem info and status:
>> $> mmcli
On Aug 6, 2012 2:54 PM, "Aleksander Morgado" wrote:
>
>
> More or less, yes. You have the 'mmcli' utility in that branch,
though,
> so you can skip writing raw dbus-send commands and play with the cli
> instead, like this (assuming only one modem connected, so index 0):
>
> >>>
Hey Bjørn,
>>> >> 3) I still wonder how to handle the usb => usbmisc transition. For now
>>> >> I've just been searching and replacing, but that is of course not
>>> >> supportable. And it isn't really a one-to-one replacement either.
>>> >> There are places where "usb" actually refer to the sub
> More or less, yes. You have the 'mmcli' utility in that branch, though,
> so you can skip writing raw dbus-send commands and play with the cli
> instead, like this (assuming only one modem connected, so index 0):
>
> Show modem info and status:
>$> mmcli -m 0
>
>>
More or less, yes. You have the 'mmcli' utility in that branch, though,
so you can skip writing raw dbus-send commands and play with the cli
instead, like this (assuming only one modem connected, so index 0):
Show modem info and status:
$> mmcli -m 0
Send
Den 06. aug. 2012 12:07, skrev Aleksander Morgado:
More or less, yes. You have the 'mmcli' utility in that branch, though,
so you can skip writing raw dbus-send commands and play with the cli
instead, like this (assuming only one modem connected, so index 0):
Show modem info and status:
$>
> Is this branch working now with master version of Network manager
> including the gnome applet?
>
Not yet, no. The 'qui-support' branch is to be considered unstable, as
I'm still hacking into it extensively. That branch is then based on git
master, which is more stable
Den 06. aug. 2012 11:28, skrev Aleksander Morgado:
Is this branch working now with master version of Network manager
including the gnome applet?
Not yet, no. The 'qui-support' branch is to be considered unstable, as
I'm still hacking into it extensively. That branch is then based on git
master,
>> >
>> > Is this branch working now with master version of Network manager
>> > including the gnome applet?
>> >
>>
>> Not yet, no. The 'qui-support' branch is to be considered unstable, as
>> I'm still hacking into it extensively. That branch is then based on git
>> master, which is more stable,
On Aug 6, 2012 8:38 AM, "Aleksander Morgado" wrote:
>
>
> >
> > Is this branch working now with master version of Network manager
> > including the gnome applet?
> >
>
> Not yet, no. The 'qui-support' branch is to be considered unstable, as
> I'm still hacking into it extensively. That branch is t
>
> Is this branch working now with master version of Network manager
> including the gnome applet?
>
Not yet, no. The 'qui-support' branch is to be considered unstable, as
I'm still hacking into it extensively. That branch is then based on git
master, which is more stable, but not integrated y
Den 05. aug. 2012 20:47, skrev Aleksander Morgado:
Hello,
I am playing a bit with the qmi-support branch, which seems to be
getting close to operational. Nice work!
I am having trouble now building that branch:
mm-broadband-modem-qmi.c: In function ‘set_allowed_modes_context
If you are not the email I need to notify, please let me know who.
I would like to be removed from the mailing list.
Thank you,
R. Clark Webb
On Sun, Aug 5, 2012 at 2:47 PM, Aleksander Morgado wrote:
>
> > Hello,
> >
> > I am playing a bit with the qmi-support branch, which seems to be
> Hello,
>
> I am playing a bit with the qmi-support branch, which seems to be
> getting close to operational. Nice work!
>
>
> I am having trouble now building that branch:
>
> mm-broadband-modem-qmi.c: In function ‘set_allowed_modes_context_step’:
> mm-broadband-modem-qmi.c:216
2012/7/31 Bjørn Mork
> Hello,
>
> I am playing a bit with the qmi-support branch, which seems to be
> getting close to operational. Nice work!
>
>
I am having trouble now building that branch:
mm-broadband-modem-qmi.c: In function ‘set_allowed_modes_context_step’:
mm-broadband-modem-qmi.c:2165
Aleksander Morgado writes:
> Hey!
>
> You're truly trying *a lot* of untested code :-)
Oh, yeah. It's a lot easier to find bugs then :-)
> The new API allows users to create more than one bearer; when it's done
> we'll allow to do all that. I must say, I didn't really cover yet the
> case of m
Hey!
You're truly trying *a lot* of untested code :-)
>
> I am playing a bit with the qmi-support branch, which seems to be
> getting close to operational. Nice work!
>
> But I have a few issues I don't like, as usual :-)
>
Don't worry, I think I already owe you a couple of beers for all thi
Hello,
I am playing a bit with the qmi-support branch, which seems to be
getting close to operational. Nice work!
But I have a few issues I don't like, as usual :-)
1) On exit, ModemManager does this:
ModemManager[5390]: [1343739104.306007] [mm-serial-port.c:969]
mm_serial_port_close(): (t
29 matches
Mail list logo
