Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Sep 2021 07:35:33 +0000
From:      bugzilla-noreply@freebsd.org
To:        usb@FreeBSD.org
Subject:   [Bug 234578] Support for Sierra Wireless EM7455 modem
Message-ID:  <bug-234578-19105-g1johKFnOD@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-234578-19105@https.bugs.freebsd.org/bugzilla/>
References:  <bug-234578-19105@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234578

Maurice J Niessen <du@hohlhupe.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |du@hohlhupe.de

--- Comment #11 from Maurice J Niessen <du@hohlhupe.de> ---
As Qingjun Wei already mentioned, you are discussing different issues here =
and
you are losing focus...

The device 1199:9079 is not handled by u3g.ko to give us support (like
/dev/ttyU*, /dev/cuaU*) for sending AT commands to it. AFAIK other methods =
like
MBIM, QMI and RMNET* aren=E2=80=99t supported in FreeBSD at all.

Sending =E2=80=9Cmagic packets=E2=80=9D to specific OEM versions of 1199:90=
79 (and yes, mine
says =E2=80=9Ccustomer: lenovo-laptop=E2=80=9D as well) to overcome the =E2=
=80=9Clow power mode (LPM)/
FCC AUTH=E2=80=9D issue is something else. BUT for the =E2=80=9Cmagic=E2=80=
=9D of a challenge/response
authentication and setting FCC AUTH=3D0, it=E2=80=99s necessary to send AT =
commands to
our lovely 1199:9079.
Dean already mentioned the =E2=80=9Cdescription=E2=80=9D in form of a pytho=
n script how to do
that =E2=80=9Cmagic=E2=80=9D. Within the years, the link has changed. It ca=
n be found here now:

https://github.com/bkerler/edl/blob/master/modem/sierrakeygen.py

Patching the firmware of 1199:9079 with a black-boxed nvu-file from a
Russian-speaking technical forum nvu-file to make it less specific, is
something that I would neither do, nor recommend. This might be a workaroun=
d,
but like Ed Maste I want to know how to reproduce the nvu-file/fixes on my =
own
- generally. I love the fact, that my 1199:9079 is not able to produce high
power signals (or even signals at all, so that ue0 gets an IP address for
example) without =E2=80=9Cpermission=E2=80=9D. Sure=E2=80=A6 it=E2=80=99s m=
ore an annoying =E2=80=9Cfeature=E2=80=9D, but much
more important it=E2=80=99s not a bug of FreeBSD and nothing which needs to=
 be
discussed in this topic/thread here (no offense).

Yes, I know how to patch and build my own kernel=E2=80=A6 BUT you are speak=
ing of a
single line of =E2=80=9Ccode=E2=80=9D (more harmless definitions than real =
code) in two files
for years now. I would love to see those lines within FreeBSD 13 sources in=
 the
nearer future.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234578-19105-g1johKFnOD>