Hey,
> >> There's an ongoing discussion in the ModemManager package in github
> >> related to how the MTU may be configured in the network interface
> >> based on what the MM bearer object reports:
> >> https://github.com/openwrt/packages/issues/11383
> >>
> >> E.g.:
> >>
> >> $ ip route show
> >>
Hey,
>>
>> There's an ongoing discussion in the ModemManager package in github
>> related to how the MTU may be configured in the network interface
>> based on what the MM bearer object reports:
>> https://github.com/openwrt/packages/issues/11383
>>
>> E.g.:
>>
>> $ ip route show
>> default via 25
Hey Alex
> I have been trying to add support for the Quectel EM20-G LTE modem on
> openwrt, using a similar method to how the support for the RM500Q modem
> was implemented. I made changes to the qmi_wwan driver using the
> attached patch (which also has backported changes for the RM500Q).
>
Not
Hey!
There's an ongoing discussion in the ModemManager package in github
related to how the MTU may be configured in the network interface
based on what the MM bearer object reports:
https://github.com/openwrt/packages/issues/11383
E.g.:
$ ip route show
default via 25.225.105.222 dev wwan0 proto
Hey!
> > > > root@localhost:~# mmcli -b 2
> > > >
> > > > General| dbus path:
> > > > /org/freedesktop/ModemManager1/Bearer/2
> > > > | type: default
> > > >
> > > > Status
Hey,
>
> root@localhost:~# mmcli -b 2
>
> General| dbus path:
> /org/freedesktop/ModemManager1/Bearer/2
> | type: default
>
> Status | connected: yes
>
Hey!
>
> I found one :
> https://github.com/lkundrak/openwrt-network-manager
>
> I wonder if this is righty and worthy to try.
> I am now trying porting it anyway.
>
I would first write to lkundrak (who is one of the NetworkManager
maintainers) to ask whether this port is usable or not.
--
Alek
Hey,
> I checked the vid:pid. It is "1519:0443". I found this via lsusb -v:
>
> SIERRA WIRELESS HL7528
> root@LEDE:~# lsusb -v
> Bus 001 Device 002: ID 1519:0443 <
> Bus 001 Device 001: ID 1d6b:0002
> Bus 002 Device 001: ID 1d6b:0003
>
> But I changed modem to new one because you said Si
Hey,
> We have Sierra modem. HL7528
> So I tested my linux box with this modem and I received first prints below:
>
> root@LEDE:/lib/udev/rules.d# mmcli -L
> /org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless] HL7528
> root@LEDE:/lib/udev/rules.d# mmcli -m 0
> --
Hey,
> I guess I could try other LTE/5G modem.
> I'd like to know what is best supported by ModemManager or OpenWRT/LEDE.
>
Puff, lots of different devices. If you try anything from e.g. Sierra
Wireless, Quectel, Telit... they will probably work. BUT, the issues
seen in your setup may not be dire
Hey!
> Let me provide some additional information and new test log messages.
>
> The problem I reported is improved one setp. Originally it was like:
>root at LEDE:~# mmcli -L
>error: couldn't create manager: Timeout was reached
>
> Now it is like:
>root@LEDE:~# mmcli -L
>No modems
Hey Jeonghum,
> Thank you for the very kind message!
> I tried "mmcli -L" and received an error message:
> root at LEDE:~# mmcli -L
> error: couldn't create manager: Timeout was reached
>
This is extremely weird, and it would show some issue with your setup,
maybe with how DBus is installed/r
Hey!
> > I'm working on porting your 4-byte opcode support fix for the w25q256
> > (in openwrt git master, 4745969ad7c0cb65f55c8de1f05eba786ca27f71) to
> > the 4.14 kernel used in 19.07 for the Lima board.
> >
> > The port is relatively easy just adding the post-bfpt parsing hook,
> > but I'm stuc
Hey Mantas,
I'm working on porting your 4-byte opcode support fix for the w25q256
(in openwrt git master, 4745969ad7c0cb65f55c8de1f05eba786ca27f71) to
the 4.14 kernel used in 19.07 for the Lima board.
The port is relatively easy just adding the post-bfpt parsing hook,
but I'm stuck much earlier t
Hey Ameretat,
On Sat, Nov 26, 2016 at 11:05 PM, Ameretat Reith
wrote:
>
> I got a gl-inet Domino board having a Quectel UC20 UMTS/HSPA+ module [1]
> installed on. I was under the impression that it can talk with QMI but then
> I
> checked website, realized It's nowhere mentioned so. On the other
Hey,
At which stage of the system boot are the hotplug events for the
already available hardware emitted?
E.g. if I want to talk to a system daemon for each hotplug event, I'd
like to make sure the daemon is already up and running. Currently I've
got such a daemon started with a /etc/rc.d/S70- ru
On 02/28/2013 02:13 PM, Felix Fietkau wrote:
> By the way, I'm almost done with my QMI code rewrite. You can find it
> here: http://nbd.name/gitweb.cgi?p=uqmi.git;a=summary or
> git://nbd.name/uqmi.git.
> I think it can already do pretty much all that's necessary to bring up
> the connection like q
ModemManager is a DBus-activated service which provides a unified high level
interface for communicating with mobile broadband modems.
Signed-off-by: Aleksander Morgado
---
Hey,
So, this patch includes packaging of the ModemManager daemon. It currently
depends on the following patches
But make it configurable.
Signed-off-by: Aleksander Morgado
---
utils/systemd-udev/Config.in | 6 ++
utils/systemd-udev/Makefile | 18 +-
2 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/utils/systemd-udev/Config.in b/utils/systemd-udev/Config.in
index
So, this third series of the patches include additional fixes:
* Udev daemon is renamed from 'systemd-udevd' to 'udevd'
* Fixes in library paths for DevInstall vs the paths given in the pkg-config
files
* Avoid using SSP-specific stuff (so the uClibc patch to enable SSP is no
longer needed)
compilation of the
package with the uClibc toolchain, which lacks several features used within
systemd.
Signed-off-by: Aleksander Morgado
---
utils/systemd-udev/Config.in | 58 +
utils/systemd-udev/Makefile| 169 ++
...ine-MS_REC-and
On 02/13/2013 11:43 AM, Florian Fainelli wrote:
> Hello,
>
> On 02/13/2013 09:21 AM, Aleksander Morgado wrote:
>> Needed for systemd-udev compilation.
>
> When you enable such a feature system-wide for all platforms, it might
> be a good thing to also get some figures ab
I'm trying to prepare an update of udev/libudev to latest upstream. As
you may already know, udev/libudev sources are now within systemd. I'm
not fully sure how to handle this issue; so I'm hoping to get some
advice here. Comments welcome!
>>>
>>> Why do we need this at all? Mo
Signed-off-by: Aleksander Morgado
---
libs/libqmi/Makefile | 5 +
1 file changed, 5 insertions(+)
diff --git a/libs/libqmi/Makefile b/libs/libqmi/Makefile
index 8e742f7..a9db3c0 100644
--- a/libs/libqmi/Makefile
+++ b/libs/libqmi/Makefile
@@ -35,6 +35,11 @@ define Build/InstallDev
On 02/13/2013 12:22 PM, Florian Fainelli wrote:
>
>
> On 02/13/2013 09:21 AM, Aleksander Morgado wrote:
>> Needed for systemd-udev compilation.
>
> Why would we need this at all? I would rather you teach systemd-udev
> about the availability of ssp.
-fstack-protector,
But make it configurable.
Signed-off-by: Aleksander Morgado
---
utils/systemd-udev/Config.in | 6 ++
utils/systemd-udev/Makefile | 18 +-
2 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/utils/systemd-udev/Config.in b/utils/systemd-udev/Config.in
index
compilation of the
package with the uClibc toolchain, which lacks several features used within
systemd.
Signed-off-by: Aleksander Morgado
---
utils/systemd-udev/Config.in | 58 +
utils/systemd-udev/Makefile| 177 ++
...ine-MS_REC-and
Updated the systemd-udev specific patches with some fixes.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> I'm trying to prepare an update of udev/libudev to latest upstream. As
>> you may already know, udev/libudev sources are now within systemd. I'm
>> not fully sure how to handle this issue; so I'm hoping to get some
>> advice here. Comments welcome!
>
> Why do we need this at all? Most confi
But make it configurable.
Signed-off-by: Aleksander Morgado
---
utils/systemd-udev/Config.in | 6 ++
utils/systemd-udev/Makefile | 18 +-
2 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/utils/systemd-udev/Config.in b/utils/systemd-udev/Config.in
index
Needed for systemd-udev compilation.
Signed-off-by: Aleksander Morgado
---
toolchain/uClibc/config-0.9.33.2/common | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/toolchain/uClibc/config-0.9.33.2/common
b/toolchain/uClibc/config-0.9.33.2/common
index f806194..1af90da 100644
Needed for systemd-udev compilation.
Signed-off-by: Aleksander Morgado
---
toolchain/uClibc/config-0.9.33.2/common | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/toolchain/uClibc/config-0.9.33.2/common
b/toolchain/uClibc/config-0.9.33.2/common
index 4e4da3e..f806194 100644
compilation of the
package with the uClibc toolchain, which lacks several features used within
systemd.
Signed-off-by: Aleksander Morgado
---
utils/systemd-udev/Config.in | 58 +
utils/systemd-udev/Makefile| 177 ++
...ine-MS_REC-and
>>> I'm trying to prepare an update of udev/libudev to latest upstream. As
>>> you may already know, udev/libudev sources are now within systemd. I'm
>>> not fully sure how to handle this issue; so I'm hoping to get some
>>> advice here. Comments welcome!
>>>
>>> One option is to build systemd com
>> A third approach would be to actually provide a stripped down
>> configure.ac and Makefile.am just with the udev/libudev stuff. Quite
>> a nightmare to update these in each new udev/libudev release, though.
>>
> LFS maintain a makefile to only build a minimal udev.
> http://www.linuxfromscratch
>> I'm trying to prepare an update of udev/libudev to latest upstream. As
>> you may already know, udev/libudev sources are now within systemd. I'm
>> not fully sure how to handle this issue; so I'm hoping to get some
>> advice here. Comments welcome!
>>
>> One option is to build systemd completel
> You forgot option #4: forget about the whole systemd madness, and
> migrate to eudev (1)
> Systemd bloat simply doesn't belong on an embedded system, IMHO.
>
> (1) http://www.gentoo.org/proj/en/eudev/
>
That's not really a replacement; the developers of eudev themselves say
that it's just a t
On 02/11/2013 09:04 PM, Aleksander Morgado wrote:
> But I'm
> not sure how to handle the case of a package from 'trunk' requiring a
> package from 'packages'. Is that an issue at all?
I'd actually like to enable libgudev compilation from the systemd/udev
re
Hey,
I'm trying to prepare an update of udev/libudev to latest upstream. As
you may already know, udev/libudev sources are now within systemd. I'm
not fully sure how to handle this issue; so I'm hoping to get some
advice here. Comments welcome!
One option is to build systemd completely (e.g. with
Traces are always built now, and can be enabled/disabled with
'qmi_utils_set_traces_enabled()'.
Signed-off-by: Aleksander Morgado
---
libs/libqmi/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/libs/libqmi/Makefile b/libs/libqmi/Makefile
index d49b43e..8e742f7 100644
> Am 09.01.2013 13:06, schrieb Aleksander Morgado:
>> Oh, hey again André :-)
>> Will that be much different to the 'qmi4g' protocol handler I wrote some
>> time ago? See:
>> https://gitorious.org/lanedo/openwrt-packages/blobs/qmi-support/net/qmi4g/files/q
Oh, hey again André :-)
>
> if you want integration of qmi in OpenWRT, I'm working on it in netifd
> and luci. It's nearly finished. Just some tests and core cleanup are
> missing.
>
Will that be much different to the 'qmi4g' protocol handler I wrote some
time ago? See:
https://sigquit.wordpr
Hey,
Now that libqmi got in OpenWRT, I would like to use ModemManager as
well. The only missing dependency seems to be GUdev; which depends on
libudev, which depends on udev.
All GUdev, libudev and udev are now within the systemd sources, and all
this collection seems not packaged for OpenWRT.
I
43 matches
Mail list logo
