Without patch unloading the dwc3-of-simple module went stuck after
successfully removing hcd.1 during the hcd.0 removal:
root@LEDE:/# rmmod dwc3-of-simple
[ 21.391846] xhci-hcd xhci-hcd.1.auto: remove, state 1
[ 21.391931] usb usb4: USB disconnect, device number 1
[ 21.397038] xhci-hcd xhci-
On Sun, Apr 02, 2017 at 06:16:10PM +0200, Hauke Mehrtens wrote:
> The Vendor SDK is based on UGW 6.1.1, based on OpenWrt 12.09 with kernel
> 3.10 and device tree support. Probably even the vendor image uses a
> device tree compiled into the kernel image.
> According to the configuration file in
> /
The patch follows the qualcomm code comments setting
SSUSB_CTRL_TEST_POWERDOWN to 0x1 and is testing and clearing the
Bit during usb superspeed phy init.
Fixes: dwc3 module unloading and re-loading
Signed-off-by: Thomas Reifferscheid
---
Changes since v3:
* Revert v1/v2
* Set SSUSB_CTRL_TEST_
On 04/02/2017 05:48 PM, Hauke Mehrtens wrote:
> On 04/02/2017 05:02 PM, Baptiste Jonglez wrote:
>> Hi,
>>
>> I am currently adding LEDE support for the Netgear DM200 VDSL modem
>> [https://wiki.openwrt.org/toh/netgear/dm200], which uses a Lantiq VR9 SoC.
>>
>> I was able to boot LEDE from RAM, and
On 04/02/2017 05:02 PM, Baptiste Jonglez wrote:
> Hi,
>
> I am currently adding LEDE support for the Netgear DM200 VDSL modem
> [https://wiki.openwrt.org/toh/netgear/dm200], which uses a Lantiq VR9 SoC.
>
> I was able to boot LEDE from RAM, and got the LEDs working, but I cannot
> get the flash t
binutils 2.27 checks if the target compiler supports -Wstack-
usage=262144, and also uses this setting for the host compiler. If the
host compiler is gcc < 4.9 binutils build will fail. This backports 2
commits which are fixing this problem for binutils 2.28.
Signed-off-by: Hauke Mehrtens
---
I
Hi,
I am currently adding LEDE support for the Netgear DM200 VDSL modem
[https://wiki.openwrt.org/toh/netgear/dm200], which uses a Lantiq VR9 SoC.
I was able to boot LEDE from RAM, and got the LEDs working, but I cannot
get the flash to work with LEDE :(
The bootloader (u-boot) has access to the
You can flash via tftp recovery (serve factory image as /mr6400_tp_recovery.bin
on 192.168.0.66/24, connect to any ethernet port and power on device while
holding the reset button). Flashing via OEM web interface does not work.
Hardware Specification (v1.0 EU):
- SoC: QCA9531
- Flash: Winbond W2