Hello Dev´s,
I hope someone can help me here. I have noticed since the
kernel update in the master branch of OpenWrt to 6.6 that
the enumeration of the USB host controllers is suddenly
randomly.
This has been encountered on the APU3 board from PCengine[1].
That wasn't the case with the 5.15 ker
On 17.07.24 13:10, Florian Eckert wrote:
Hello Dev´s,
I hope someone can help me here. I have noticed since the
kernel update in the master branch of OpenWrt to 6.6 that
the enumeration of the USB host controllers is suddenly
randomly.
This has been encountered on the APU3 board from PCengine[1
Hello Felix,
thanks for your reply.
As you can see the usb1 and usb2 are swapped!
The problem now is that the ModemManager is using the syspath
to reference the modem in the uci configuration [2]. If the modem's
syspath is now random, the system can no longer find the modem and
cannot establis
Hello,
if things work as expected, MM will auto-discover the modem.
You may get sysfs path from mmcli itself and dynamically set it viauci.
I didn't use very much this protocol handler, so I do not have better
suggestions.
Genuine question: are we sure sysfs path is necessary in the config?
Enr
On 17.07.24 14:29, Florian Eckert wrote:
In my opinion, the best course of action is to just deal with it by
changing the code to no longer rely on usbX names. Better make it
depend on the sysfs path, similar to wifi-device path handling in the
wireless config.
I am already using the sysfs path
Hi,
i have only recently started working with OpenWrt. I think the project of an
own hardware platform is great. I don't know how far the development has
progressed. However, I am missing a very important interface in the hardware
specification!
A PCIe M.2 E-Key interface would open the way for
