Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info
W dniu 2015-05-05 o 08:56, Johannes Berg pisze:
On Mon, 2015-05-04 at 23:16 +0200, Sylwester Petela wrote:
[ 456.056000] DSL[00]: negative response for MsgID=0x2B0A
(Class=0x3100) - on try 0!
[ 456.764000] DSL[00]: Error for send CMD MsgID=0x2B0A - KEEP line!
[ 456.768000] DSL[00]: ERROR - ReTx PM counters read failed!
[ 457.032000] MEI_DRV[00 - 01]: ReadAck[0x2B0A] - FctOP ERROR 0x31!
and after about 20-30 min hangs, after disabling ReTx at build system
How did you disable ReTx?
Added to makefile in vdsl-app and vdsl-control
--disable-dsl-pm-retx-counters \
--disable-dsl-pm-retx-thresholds \
vdsl_cpe_control commands were ignored when trying to disable it by them.
stays online for at least 6 hours (didn't test further) with some
warnings repeating every two seconds:
[ 458.772000] DSL[00]: WARNING - Data Path counters are not supported
for the FE!
That seems pretty harmless - the driver code is really really ugly
though. Probably should just remove the message.
Cannot find witch function this message is referring to, need to
investigate more.
vectoring and ReTx works acording to friend but system log shows some
errors as well like on my ADSL line but not so many.
What firmware/driver combination was this with?
xcpe_567517_562301.bin: VDSL over ISDN incl. vectoring support for
VRX200, version: 6.7.5 | ADSL Annex A for VRX200, version: 6.2.3
4.15.2 -app/control; 1.4.5 -mei
On ADSL and also on VDSL with never firmware and errors/warnings
appearing in log, system is under quite big load, compared to stock drivers.
Yeah, this is true. I'm not sure what I said yesterday ("it's too slow")
is correct, but certainly it's pretty loaded.
johannes
Yes slow but why ? Because of load or because of hardware, Zyxel on
stock openwrt driver can achieve 80Mbps without that much load.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info
On Tue, 2015-05-05 at 09:28 +0200, Sylwester Petela wrote: > >> [ 458.772000] DSL[00]: WARNING - Data Path counters are not supported > >> for the FE! > > That seems pretty harmless - the driver code is really really ugly > > though. Probably should just remove the message. > > Cannot find witch function this message is referring to, need to > investigate more. I found it in Martin's drv_dsl_cpe_api_vrx repository. > >> vectoring and ReTx works acording to friend but system log shows some > >> errors as well like on my ADSL line but not so many. > > What firmware/driver combination was this with? > > xcpe_567517_562301.bin: VDSL over ISDN incl. vectoring support for > VRX200, version: 6.7.5 | ADSL Annex A for VRX200, version: 6.2.3 > > 4.15.2 -app/control; 1.4.5 -mei Ok, I'll give that a try as soon as I've removed this from my productive env. Or perhaps I'll just put another image on a separate extroot since I have extroot setup anyway. > Yes slow but why ? Because of load or because of hardware, Zyxel on > stock openwrt driver can achieve 80Mbps without that much load. Not sure, perhaps the CPU is just slow? johannes ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] netsupport: l2tp-ip: only depend on IPv6 if IPv6 support is enabled
Before r45593 kmod-l2tp-ip did not depend on kmod-ipv6. With r45593 support for L2TP IPv6 encapsulation was added and included in the kmod-l2tp-ip package. This change also added the dependency to kmod-ipv6 to kmod-l2tp-ip, regardless of whether the user chose to generally include IPv6 support or not. Change this so L2TP over IPv6 and the resulting dependency to kmod-ipv6 is only included in kmod-l2tp-ip if IPv6 support is enabled. Signed-off-by: Daniel Golle --- package/kernel/linux/modules/netsupport.mk | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/package/kernel/linux/modules/netsupport.mk b/package/kernel/linux/modules/netsupport.mk index 7ec3d29..4483581 100644 --- a/package/kernel/linux/modules/netsupport.mk +++ b/package/kernel/linux/modules/netsupport.mk @@ -895,11 +895,13 @@ $(eval $(call KernelPackage,l2tp-eth)) define KernelPackage/l2tp-ip SUBMENU:=$(NETWORK_SUPPORT_MENU) - TITLE:=L2TP IP + IPv6 encapsulation for L2TPv3 - DEPENDS:=+kmod-l2tp +kmod-ipv6 + TITLE:=L2TP IP encapsulation for L2TPv3 + DEPENDS:=+kmod-l2tp +IPV6:kmod-ipv6 KCONFIG:=CONFIG_L2TP_IP - FILES:=$(LINUX_DIR)/net/l2tp/l2tp_ip.ko $(LINUX_DIR)/net/l2tp/l2tp_ip6.ko - AUTOLOAD:=$(call AutoLoad,33,l2tp_ip l2tp_ip6) + FILES:= \ + $(LINUX_DIR)/net/l2tp/l2tp_ip.ko \ + $(if $(CONFIG_IPV6),$(LINUX_DIR)/net/l2tp/l2tp_ip6.ko) + AUTOLOAD:=$(call AutoLoad,33,l2tp_ip $(if $(CONFIG_IPV6),l2tp_ip6)) endef define KernelPackage/l2tp-ip/description -- 2.3.7 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Device tree issues with TL-WDR4900 (mpc85xx) and kernel 4.0.1
Am 05.05.2015 um 08:29 schrieb Wojciech Dubowik:
> On 04/05/15 22:45, Heiner Kallweit wrote:
>> I tried to make the TL-WDR4900 work under kernel 4.0.
>> Adjusting the platform-specific patches was quickly done and the system
>> boots.
>> However I get the following error messages.
>>
>> [2.959975] /leds/system: could not get #gpio-cells for
>> /soc@ffe0/gpio-controller@f000
>> [2.968276] leds-gpio: probe of leds failed with error -22
>> [ 34.622909] /buttons/reset: could not get #gpio-cells for
>> /soc@ffe0/gpio-controller@f000
>> [ 34.631383] gpio-keys buttons: Failed to get gpio flags, error: -22
>> [ 34.637657] gpio-keys: probe of buttons failed with error -22
>>
>> I'm not a device tree expert, what I checked so far:
>> The gpio-related section in tl-wdr4900-v1.dts is empty
>>
>> gpio0: gpio-controller@f000 {
>> };
> Gpio controller is now at fc00. See latest commit for
> arch/powerpc/boot/dts/fsl/pq3-gpio-0.dtsi.
> Regards,
> Wojtek
>
> PS. I have been also trying 4.0 but I have ran into so many problems with
> gianfar that I have given it up.
> For now...
Thanks. I face issues with the network as well and had to attach a serial
console + tftpboot to make it work again.
Back to 3.19.0 now ..
Heiner
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ipq806x: add pcie support to ipq806x based platforms
This change adds PCIe support to IPQ806x based platforms. The driver is actually cherry-picked from the following LKML thread: *https://lwn.net/Articles/643086/ (patches 110-111) We also add here an additional fix to support multiple PCI controllers on the same platform (patch 112), and to patch the ap148 & dbs149 DTS files (patch 113). Signed-off-by: Mathieu Olivari --- target/linux/ipq806x/config-3.18 | 6 + target/linux/ipq806x/config-4.0| 10 +- ...CI-qcom-Document-PCIe-devicetree-bindings.patch | 266 ...-qcom-Add-Qualcomm-PCIe-controller-driver.patch | 753 + ...-qcom-add-pcie-nodes-to-ipq806x-platforms.patch | 268 ...tomatically-select-PCI_DOMAINS-if-PCI-is-.patch | 29 + .../patches-3.18/700-add-gmac-dts-suport.patch | 19 +- ...CI-qcom-Document-PCIe-devicetree-bindings.patch | 266 ...-qcom-Add-Qualcomm-PCIe-controller-driver.patch | 753 + ...-qcom-add-pcie-nodes-to-ipq806x-platforms.patch | 260 +++ ...tomatically-select-PCI_DOMAINS-if-PCI-is-.patch | 29 + .../patches-4.0/700-add-gmac-dts-suport.patch | 26 +- 12 files changed, 2662 insertions(+), 23 deletions(-) create mode 100644 target/linux/ipq806x/patches-3.18/110-DT-PCI-qcom-Document-PCIe-devicetree-bindings.patch create mode 100644 target/linux/ipq806x/patches-3.18/111-PCI-qcom-Add-Qualcomm-PCIe-controller-driver.patch create mode 100644 target/linux/ipq806x/patches-3.18/112-ARM-dts-qcom-add-pcie-nodes-to-ipq806x-platforms.patch create mode 100644 target/linux/ipq806x/patches-3.18/113-ARM-qcom-automatically-select-PCI_DOMAINS-if-PCI-is-.patch create mode 100644 target/linux/ipq806x/patches-4.0/110-DT-PCI-qcom-Document-PCIe-devicetree-bindings.patch create mode 100644 target/linux/ipq806x/patches-4.0/111-PCI-qcom-Add-Qualcomm-PCIe-controller-driver.patch create mode 100644 target/linux/ipq806x/patches-4.0/112-ARM-dts-qcom-add-pcie-nodes-to-ipq806x-platforms.patch create mode 100644 target/linux/ipq806x/patches-4.0/113-ARM-qcom-automatically-select-PCI_DOMAINS-if-PCI-is-.patch diff --git a/target/linux/ipq806x/config-3.18 b/target/linux/ipq806x/config-3.18 index 8de4cb4..32f4b67 100644 --- a/target/linux/ipq806x/config-3.18 +++ b/target/linux/ipq806x/config-3.18 @@ -257,6 +257,11 @@ CONFIG_OLD_SIGSUSPEND3=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_PAGE_OFFSET=0xC000 CONFIG_PCI=y +CONFIG_PCIEAER=y +CONFIG_PCIEPORTBUS=y +CONFIG_PCIE_DW=y +CONFIG_PCIE_QCOM=y +CONFIG_PCI_DOMAINS=y CONFIG_PCI_MSI=y CONFIG_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=y @@ -294,6 +299,7 @@ CONFIG_QCOM_BAM_DMA=y CONFIG_QCOM_GSBI=y CONFIG_QCOM_SCM=y CONFIG_QCOM_WDT=y +CONFIG_RAS=y # CONFIG_RCU_BOOST is not set CONFIG_RCU_CPU_STALL_TIMEOUT=21 CONFIG_RCU_CPU_STALL_VERBOSE=y diff --git a/target/linux/ipq806x/config-4.0 b/target/linux/ipq806x/config-4.0 index c7bbcd9..1786abb 100644 --- a/target/linux/ipq806x/config-4.0 +++ b/target/linux/ipq806x/config-4.0 @@ -266,7 +266,14 @@ CONFIG_OLD_SIGSUSPEND3=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_PAGE_OFFSET=0xC000 CONFIG_PCI=y -# CONFIG_PCI_DOMAINS_GENERIC is not set +CONFIG_PCIEAER=y +CONFIG_PCIEPORTBUS=y +CONFIG_PCIE_DW=y +CONFIG_PCIE_PME=y +CONFIG_PCIE_QCOM=y +CONFIG_PCI_DEBUG=y +CONFIG_PCI_DOMAINS=y +CONFIG_PCI_DOMAINS_GENERIC=y CONFIG_PCI_MSI=y CONFIG_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=y @@ -306,6 +313,7 @@ CONFIG_QCOM_BAM_DMA=y CONFIG_QCOM_GSBI=y CONFIG_QCOM_SCM=y CONFIG_QCOM_WDT=y +CONFIG_RAS=y # CONFIG_RCU_BOOST is not set CONFIG_RCU_CPU_STALL_TIMEOUT=21 CONFIG_RCU_STALL_COMMON=y diff --git a/target/linux/ipq806x/patches-3.18/110-DT-PCI-qcom-Document-PCIe-devicetree-bindings.patch b/target/linux/ipq806x/patches-3.18/110-DT-PCI-qcom-Document-PCIe-devicetree-bindings.patch new file mode 100644 index 000..95398e0 --- /dev/null +++ b/target/linux/ipq806x/patches-3.18/110-DT-PCI-qcom-Document-PCIe-devicetree-bindings.patch @@ -0,0 +1,266 @@ +Content-Type: text/plain; charset="utf-8" +MIME-Version: 1.0 +Content-Transfer-Encoding: 7bit +Subject: [v2,3/5] DT: PCI: qcom: Document PCIe devicetree bindings +From: Stanimir Varbanov +X-Patchwork-Id: 6326181 +Message-Id: <1430743338-10441-4-git-send-email-svarba...@mm-sol.com> +To: Rob Herring , Kumar Gala , + Mark Rutland , + Grant Likely , + Bjorn Helgaas , + Kishon Vijay Abraham I , + Russell King , Arnd Bergmann +Cc: linux-arm-...@vger.kernel.org, linux-ker...@vger.kernel.org, + linux-arm-ker...@lists.infradead.org, devicet...@vger.kernel.org, + linux-...@vger.kernel.org, Mathieu Olivari , + Srinivas Kandagatla , + Stanimir Varbanov +Date: Mon, 4 May 2015 15:42:16 +0300 + +Document Qualcomm PCIe driver devicetree bindings. + +Signed-off-by: Stanimir Varbanov + +--- +.../devicetree/bindings/pci/qcom,pcie.txt | 231 + 1 files changed, 231 insertions(+), 0 deletions(-) + create mode 100644 Documentation/devicetree/binding
Re: [OpenWrt-Devel] Intermittent Ethernet failure
Thank you, Daniel - I think you are correct - this looks like the same issue. On 5/4/2015 6:36 PM, Daniel Golle wrote: Hi Bill! On Mon, May 04, 2015 at 05:53:21PM -0700, Bill wrote: I have finally been able to reproduce the problem here at home by setting up a bridge and leaving it alone for a few days. When it failed, this is what dmesg told me: [ 409.38] eth0: link up (100Mbps/Full duplex) [ 409.38] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 423.38] eth0: link down [ 424.38] eth0: link up (100Mbps/Full duplex) [ 560.38] eth0: link down [ 1674.38] eth0: link up (100Mbps/Full duplex) [ 1680.38] eth0: link down ... This very much looks like a known issue: https://dev.openwrt.org/ticket/19085 https://dev.openwrt.org/ticket/19579 Cheers Daniel -- Bill Moffitt Ayrstone Productivity http://ayrstone.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
