On Mon, 30 Jan 2023 at 23:41, Jan Hoffmann wrote:
>
> Some VRX518 modems fail to initialize properly with the error message
> "dc_ep_clk_on failed". As a result, the DSL data path doesn't work.
>
> This hack, which is based on code from the FRITZ!Box 7530 GPL archive,
> fixes the issue. It
On 30/01/2023 23:18, Christian Marangi wrote:
On Mon, Jan 30, 2023 at 07:57:57PM +0100, Andre Heider wrote:
This reverts to the earlier behaviour, because:
* phys can be renamed, which breaks hardcoding "phy%d"
* /sys/class/ieee80211/*/device can return networks of other phys,
since "device"
Some VRX518 modems fail to initialize properly with the error message
"dc_ep_clk_on failed". As a result, the DSL data path doesn't work.
This hack, which is based on code from the FRITZ!Box 7530 GPL archive,
fixes the issue. It changes the PCIe vendor/device ID to values matching
a Lantiq SoC.
On Mon, Jan 30, 2023 at 07:57:57PM +0100, Andre Heider wrote:
> This reverts to the earlier behaviour, because:
> * phys can be renamed, which breaks hardcoding "phy%d"
> * /sys/class/ieee80211/*/device can return networks of other phys,
> since "device" is a symlink which can have multiple phys
This reverts to the earlier behaviour, because:
* phys can be renamed, which breaks hardcoding "phy%d"
* /sys/class/ieee80211/*/device can return networks of other phys,
since "device" is a symlink which can have multiple phys
The earlier behaviour fixes both points.
Fixes: 6194aaf0 "nl80211:
Hi Hauke!
On Sun, 29 Jan 2023 17:08:38 +0100
Hauke Mehrtens wrote:
> > drivers/char/random.c lines 1240- ...
> > * Reading from /dev/urandom has the same functionality as calling
> > * getrandom(2) with flags=GRND_INSECURE. Because it does not block
> > * waiting for the RNG to be ready,
