Re: [LEDE-DEV] QCA Dakota support
Hi Matthew,
I took your patches to my tree. They are for Linux 4.7, so I tried to
make Lede build with that Linux version.
I ran into some trouble with musl+netifd (fixed it). Now compat-wireless
seems to expect an older Kernel:
compat-wireless-2016-10-08/backport-include/linux/netdevice.h:337:5:
error: 'struct net_device' has no member named 'trans_start'
dev->trans_start = jiffies;
The member was kicked in 4.7.
In case someone is willing to help, I'm open for code.
-> It's unclear to me how to generate a config-4.7 from config-4.4 and
store it. build system asks for the new flags every time.
-> why does netifd not handle musl c properly or vice versa?
include/linux/in6.h:32:8: error: redefinition of 'struct in6_addr'
struct in6_addr {
-> how to disable compat-wireless and exclude it from build?
Code: https://github.com/mehlis/source/commits/ipq40xx
Regards,
Christian
Am 2016-11-08 05:05, schrieb Matthew McClintock:
On Mon, Nov 7, 2016 at 3:49 PM, Christian Mehlis
wrote:
Dakota kernel support done by QCA is public here:
https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?h=release/collard_cc_cs&id=2e6acfb58dceee5baf746a9ed37a8efbad8a7626
For a little bit cleaner tree's take a look here:
https://source.codeaurora.org/quic/qsdk/mmcclint-qca/
https://chromium-review.googlesource.com/#/q/status:merged+project:chromiumos/third_party/kernel+branch:chromeos-3.18
-M
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ext4 / no space left on device / UML
* Bjørn Mork [11.11.2016 19:04]: > > can you read something interesting? > > Sure. "Free inodes: 0" is not good. And what was I suspected. We've > all been there in the past ;) thanks for spotting this - i never saw this before 8-) > Can you reduce the number of small files on this file system somehow? > If not, then you need to recreate it. AFAIK there is no way to adjust > the inode count of an existing file system. it's just an UML image which is for boot testing. I send a patch for increasing the inodes default. bye, bastian ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] LEDE Trunk RCU stalls with sqm scripts enabled
seems as soon as i enable sqm qos scripts regardless of using fq_codel or cake im hitting RCO issues, reboots even... as soon as i disable it... all is stable its a ZBT-WG3526 Firmware Version LEDE Reboot r2152+8 / LuCI Master (git-16.313.75284-4343b2f) Kernel Version 4.4.30 [ 149.49] INFO: rcu_sched detected stalls on CPUs/tasks: [ 149.49] 3-...: (0 ticks this GP) idle=b7c/0/0 softirq=3733/3733 fqs=0 [ 149.50] (detected by 1, t=6003 jiffies, g=1039, c=1038, q=10655) [ 149.50] Task dump for CPU 3: [ 149.51] swapper/3 R running 0 0 1 0x0010 [ 149.51] Stack : 5ac7 8e049880 7ffdecec 80418a90 8045a2a4 8041 [ 149.51]8041275c 0001 0001 80412680 80412724 8041 800132e8 [ 149.51] 0001 8fc64000 8fc65ec0 8041 8005c870 1100fc03 0003 [ 149.51] 8041 8045a2a4 8005c868 8041 8001ade0 1100fc03 [ 149.51]0004 804124a0 00a0 8001ade8 fefffbdb aefffbfb fff77fe7 dfef [ 149.51]... [ 149.55] Call Trace: [ 149.55] [<8000bba8>] __schedule+0x574/0x758 [ 149.56] [<800132e8>] r4k_wait_irqoff+0x0/0x20 [ 149.56] [ 149.56] rcu_sched kthread starved for 6009 jiffies! g1039 c1038 f0x0 s3 ->state=0x1 [ 1326.67] INFO: rcu_sched detected stalls on CPUs/tasks: [ 1326.67] 2-...: (0 ticks this GP) idle=998/0/0 softirq=56566/56566 fqs=0 [ 1326.68] (detected by 1, t=6003 jiffies, g=14603, c=14602, q=9455) [ 1326.68] Task dump for CPU 2: [ 1326.69] swapper/2 R running 0 0 1 0x0010 [ 1326.69] Stack : 0001 000a 0001 8045a2a4 8041 [ 1326.69]8041275c 0001 804125e0 80412724 8041 800132e8 [ 1326.69]1100fc03 0002 8fc62000 8fc63ec0 8041 8005c870 1100fc03 0002 [ 1326.69] 8041 8045a2a4 8005c868 8041 8001ade0 1100fc03 [ 1326.69]0004 804124a0 00a0 8001ade8 fbffbfdf 7fff7b3b 7ffaeff8 67fb [ 1326.69]... [ 1326.73] Call Trace: [ 1326.73] [<8000bba8>] __schedule+0x574/0x758 [ 1326.74] [<800132e8>] r4k_wait_irqoff+0x0/0x20 [ 1326.74] [ 1326.74] rcu_sched kthread starved for 6009 jiffies! g14603 c14602 f0x0 s3 ->state=0x1 [ 1392.20] INFO: rcu_sched detected stalls on CPUs/tasks: [ 1392.20] 2-...: (0 ticks this GP) idle=c80/0/0 softirq=56566/56566 fqs=0 [ 1392.21] (detected by 3, t=6003 jiffies, g=14669, c=14668, q=11973) [ 1392.21] Task dump for CPU 2: [ 1392.22] swapper/2 R running 0 0 1 0x0010 [ 1392.22] Stack : 4e88ab25 0148 011d 773206f0 8045a2a4 8041 [ 1392.22]8041275c 0001 804125e0 80412724 8041 10d9 800132e8 [ 1392.22]1100fc03 0002 8fc62000 8fc63ec0 8041 8005c870 1100fc03 0002 [ 1392.22] 8041 8045a2a4 8005c868 8041 8001ade0 1100fc03 [ 1392.22]0004 804124a0 00a0 8001ade8 fbffbfdf 7fff7b3b 7ffaeff8 67fb [ 1392.22]... [ 1392.26] Call Trace: [ 1392.26] [<8000bba8>] __schedule+0x574/0x758 [ 1392.27] [<800132e8>] r4k_wait_irqoff+0x0/0x20 [ 1392.27] [ 1392.27] rcu_sched kthread starved for 6009 jiffies! g14669 c14668 f0x0 s3 ->state=0x1 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: expose configuration for padata
On Fri, Nov 11, 2016 at 5:06 PM, Baptiste Jonglez wrote: > Looks good to me, I didn't see an increase in kernel size when selecting > this option on ar71xx (I looked at the size of > "build_dir/target-mips_24kc_musl-1.1.15/linux-ar71xx_generic/linux-4.4.30/vmlinuz") Right. What happens on this platform is since there's no SMP, that option gets automatically deactivated, so the net effect is zero. On SMP systems, it forces CONFIG_PADATA to be selected, which is the option we actually want. > > However, I had to do a "make clean", because selecting > KERNEL_CRYPTO_PCRYPT does not cause all kmod packages to be rebuilt for > the new kernel config: This is what I've seen happen too when changing any kernel related options at all. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH v1 2/3] apm821xx: consolidate apm821xx device trees files
This patch moves the common SoC device tree entries
from the currently four supported platforms into a
common apm82181.dtsi.
Furthermore, this patch also changes the GPIO and INPUT
definitions of the supported platforms to use the defined
dt-bindings MACROs for GPIO_ACTIVE_LOW|HIGH and
KEY_WPS|RESTART|* when it's appropriate.
Signed-off-by: Christian Lamparter
---
target/linux/apm821xx/dts/MR24.dts | 472 +++
target/linux/apm821xx/dts/apm82181.dtsi| 466 +++
target/linux/apm821xx/dts/apollo3g-duo.dts | 19 +
target/linux/apm821xx/dts/apollo3g.dts | 18 -
target/linux/apm821xx/dts/apollo3g.dtsi| 571 --
target/linux/apm821xx/dts/wndr4700.dts | 915 +
6 files changed, 989 insertions(+), 1472 deletions(-)
create mode 100644 target/linux/apm821xx/dts/apm82181.dtsi
diff --git a/target/linux/apm821xx/dts/MR24.dts
b/target/linux/apm821xx/dts/MR24.dts
index 1e186e6..8d20872 100644
--- a/target/linux/apm821xx/dts/MR24.dts
+++ b/target/linux/apm821xx/dts/MR24.dts
@@ -12,422 +12,140 @@
/dts-v1/;
+#include "apm82181.dtsi"
+
/ {
- #address-cells = <2>;
- #size-cells = <1>;
model = "Meraki MR24 Access Point";
compatible = "meraki,ikarem";
- dcr-parent = <&{/cpus/cpu@0}>;
aliases {
- ethernet0 = &EMAC0;
- serial0 = &UART0;
+ serial0 = &UART1;
};
- cpus {
- #address-cells = <1>;
- #size-cells = <0>;
-
- cpu@0 {
- device_type = "cpu";
- model = "PowerPC,apm821xx";
- reg = <0x>;
- clock-frequency = <0>; /* Filled in by U-Boot */
- timebase-frequency = <0>; /* Filled in by U-Boot */
- i-cache-line-size = <32>;
- d-cache-line-size = <32>;
- i-cache-size = <32768>;
- d-cache-size = <32768>;
- dcr-controller;
- dcr-access-method = "native";
- next-level-cache = <&L2C0>;
- };
+ chosen {
+ linux,stdout-path = "/plb/opb/serial@ef600400";
};
- memory {
- device_type = "memory";
- reg = <0x 0x 0x>; /* Filled in by
U-Boot */
- };
+};
- UIC0: interrupt-controller0 {
- compatible = "ibm,uic";
- interrupt-controller;
- cell-index = <0>;
- dcr-reg = <0x0c0 0x009>;
- #address-cells = <0>;
- #size-cells = <0>;
- #interrupt-cells = <2>;
- };
- UIC1: interrupt-controller1 {
- compatible = "ibm,uic";
- interrupt-controller;
- cell-index = <1>;
- dcr-reg = <0x0d0 0x009>;
- #address-cells = <0>;
- #size-cells = <0>;
- #interrupt-cells = <2>;
- interrupts = <0x1e 0x4 0x1f 0x4>; /* cascade */
- interrupt-parent = <&UIC0>;
- };
+&CRYPTO {
+ status = "okay";
+};
- UIC2: interrupt-controller2 {
- compatible = "ibm,uic";
- interrupt-controller;
- cell-index = <2>;
- dcr-reg = <0x0e0 0x009>;
- #address-cells = <0>;
- #size-cells = <0>;
- #interrupt-cells = <2>;
- interrupts = <0xa 0x4 0xb 0x4>; /* cascade */
- interrupt-parent = <&UIC0>;
- };
+&PKA {
+ status = "okay";
+};
- UIC3: interrupt-controller3 {
- compatible = "ibm,uic";
- interrupt-controller;
- cell-index = <3>;
- dcr-reg = <0x0f0 0x009>;
- #address-cells = <0>;
- #size-cells = <0>;
- #interrupt-cells = <2>;
- interrupts = <0x10 0x4 0x11 0x4>; /* cascade */
- interrupt-parent = <&UIC0>;
- };
+&TRNG {
+ status = "okay";
+};
- /* KPH check the following */
- OCM: ocm@40004 {
- compatible = "ibm,ocm";
+&EBC0 {
+ /* Ikarem has 32MB of NAND */
+ ndfc@1,0 {
status = "okay";
- cell-index = <1>;
- /* configured in U-Boot */
- reg = <4 0x0004 0x8000>; /* 32K */
- };
-
- SDR0: sdr {
- compatible = "ibm,sdr-apm821xx";
- dcr-reg = <0x00e 0x002>;
- };
-
- CPR0: cpr {
- compatible = "ibm,cpr-apm821xx";
- dcr-reg = <0x00c 0x002>;
- };
-
- L2C0: l2c {
- compatible = "ibm,l2-cache-apm82181", "ibm,l2-cache";
- dcr-reg = <0x020 0x008
- 0x030 0x008>;
- cache-line-size = <32>;
-
[LEDE-DEV] [PATCH v1 1/3] apm821xx: add amcc, usb-otg-405ex devicetree definition
This patch adds support for the amcc,usb-otg-405ex device
which is found in all APM82181 SoCs.
Note: The system can't use the generic "snps,dwc2" compatible
because of the special ahbcfg configuration. The default
GAHBCFG_HBSTLEN_INCR4 of snps,dwc2 can cause a system hang
when the USB and SATA is used concurrently.
Signed-off-by: Christian Lamparter
---
.../804-usb-dwc2-add-amcc-usb-otg-405ex.patch | 44 ++
1 file changed, 44 insertions(+)
create mode 100644
target/linux/apm821xx/patches-4.4/804-usb-dwc2-add-amcc-usb-otg-405ex.patch
diff --git
a/target/linux/apm821xx/patches-4.4/804-usb-dwc2-add-amcc-usb-otg-405ex.patch
b/target/linux/apm821xx/patches-4.4/804-usb-dwc2-add-amcc-usb-otg-405ex.patch
new file mode 100644
index 000..e081761
--- /dev/null
+++
b/target/linux/apm821xx/patches-4.4/804-usb-dwc2-add-amcc-usb-otg-405ex.patch
@@ -0,0 +1,44 @@
+--- a/drivers/usb/dwc2/platform.c
b/drivers/usb/dwc2/platform.c
+@@ -115,6 +115,37 @@ static const struct dwc2_core_params par
+ .hibernation= -1,
+ };
+
++static const struct dwc2_core_params params_amcc_dwc_otg = {
++ .otg_cap= DWC2_CAP_PARAM_HNP_SRP_CAPABLE,
++ .otg_ver= -1,
++ .dma_enable = -1,
++ .dma_desc_enable= -1,
++ .speed = -1,
++ .enable_dynamic_fifo= -1,
++ .en_multiple_tx_fifo= -1,
++ .host_rx_fifo_size = -1,
++ .host_nperio_tx_fifo_size = -1,
++ .host_perio_tx_fifo_size= -1,
++ .max_transfer_size = -1,
++ .max_packet_count = -1,
++ .host_channels = -1,
++ .phy_type = -1,
++ .phy_utmi_width = -1,
++ .phy_ulpi_ddr = -1,
++ .phy_ulpi_ext_vbus = -1,
++ .i2c_enable = -1,
++ .ulpi_fs_ls = -1,
++ .host_support_fs_ls_low_power = -1,
++ .host_ls_low_power_phy_clk = -1,
++ .ts_dline = -1,
++ .reload_ctl = -1,
++ .ahbcfg = GAHBCFG_HBSTLEN_INCR16 <<
++GAHBCFG_HBSTLEN_SHIFT,
++ .uframe_sched = -1,
++ .external_id_pin_ctl= -1,
++ .hibernation= -1,
++};
++
+ static int __dwc2_lowlevel_hw_enable(struct dwc2_hsotg *hsotg)
+ {
+ struct platform_device *pdev = to_platform_device(hsotg->dev);
+@@ -309,2 +340,3 @@ static int dwc2_driver_remove(struct pla
+ static const struct of_device_id dwc2_of_match_table[] = {
++ { .compatible = "amcc,usb-otg-405ex", .data = ¶ms_amcc_dwc_otg },
+ { .compatible = "brcm,bcm2835-usb", .data = ¶ms_bcm2835 },
--
2.10.2
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH v1 3/3] apm821xx: remove replaced netgear, wndr4700-usb dwc2 definiton
This special dwc2 device definition for the Netgear WNDR4700
has been replaced by amcc,usb-otg-405ex in the apm82181.dtsi.
Signed-off-by: Christian Lamparter
---
.../800-usb-dwc2-add-wndr4700-otg.patch| 48 --
1 file changed, 48 deletions(-)
delete mode 100644
target/linux/apm821xx/patches-4.4/800-usb-dwc2-add-wndr4700-otg.patch
diff --git
a/target/linux/apm821xx/patches-4.4/800-usb-dwc2-add-wndr4700-otg.patch
b/target/linux/apm821xx/patches-4.4/800-usb-dwc2-add-wndr4700-otg.patch
deleted file mode 100644
index eee3fd0..000
--- a/target/linux/apm821xx/patches-4.4/800-usb-dwc2-add-wndr4700-otg.patch
+++ /dev/null
@@ -1,48 +0,0 @@
a/drivers/usb/dwc2/platform.c
-+++ b/drivers/usb/dwc2/platform.c
-@@ -115,6 +115,37 @@ static const struct dwc2_core_params par
- .hibernation= -1,
- };
-
-+static const struct dwc2_core_params params_wndr4700 = {
-+ .otg_cap= DWC2_CAP_PARAM_NO_HNP_SRP_CAPABLE,
-+ .otg_ver= -1,
-+ .dma_enable = -1,
-+ .dma_desc_enable= -1,
-+ .speed = -1,
-+ .enable_dynamic_fifo= -1,
-+ .en_multiple_tx_fifo= -1,
-+ .host_rx_fifo_size = -1,
-+ .host_nperio_tx_fifo_size = -1,
-+ .host_perio_tx_fifo_size= -1,
-+ .max_transfer_size = -1,
-+ .max_packet_count = -1,
-+ .host_channels = -1,
-+ .phy_type = -1,
-+ .phy_utmi_width = -1,
-+ .phy_ulpi_ddr = -1,
-+ .phy_ulpi_ext_vbus = -1,
-+ .i2c_enable = -1,
-+ .ulpi_fs_ls = -1,
-+ .host_support_fs_ls_low_power = -1,
-+ .host_ls_low_power_phy_clk = -1,
-+ .ts_dline = -1,
-+ .reload_ctl = -1,
-+ .ahbcfg = GAHBCFG_HBSTLEN_INCR16 <<
-+GAHBCFG_HBSTLEN_SHIFT,
-+ .uframe_sched = -1,
-+ .external_id_pin_ctl= -1,
-+ .hibernation= -1,
-+};
-+
- static int __dwc2_lowlevel_hw_enable(struct dwc2_hsotg *hsotg)
- {
- struct platform_device *pdev = to_platform_device(hsotg->dev);
-@@ -309,6 +340,7 @@ static int dwc2_driver_remove(struct pla
- static const struct of_device_id dwc2_of_match_table[] = {
- { .compatible = "brcm,bcm2835-usb", .data = ¶ms_bcm2835 },
- { .compatible = "rockchip,rk3066-usb", .data = ¶ms_rk3066 },
-+ { .compatible = "netgear,wndr4700-usb", .data = ¶ms_wndr4700 },
- { .compatible = "snps,dwc2", .data = NULL },
- { .compatible = "samsung,s3c6400-hsotg", .data = NULL},
- {},
--
2.10.2
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] LEDE consider whether to support l7 filter components?
Used for iptables application layer filtering. Earlier openwrt support was later removed. The string module affects overall performance ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: expose configuration for padata
On Thu, Nov 10, 2016 at 04:07:44AM +0100, Jason A. Donenfeld wrote: > The padata API is a powerful framework for doing parallel jobs inside > the kernel, on which various modules in the package feed can depend, > such as WireGuard. There is no item text, so that it does not show up > in menuconfig, as this is only supposed to be an option selected as a > dependency. There as already precedent for this behavior, with > CONFIG_KERNEL_RELAY, on which several packages depend. Looks good to me, I didn't see an increase in kernel size when selecting this option on ar71xx (I looked at the size of "build_dir/target-mips_24kc_musl-1.1.15/linux-ar71xx_generic/linux-4.4.30/vmlinuz") However, I had to do a "make clean", because selecting KERNEL_CRYPTO_PCRYPT does not cause all kmod packages to be rebuilt for the new kernel config: Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-lib-crc-ccitt: * kernel (= 4.4.30-1-288c1d58c9e4426041f1cf660ee89665) * * opkg_install_cmd: Cannot install package kmod-lib-crc-ccitt. … make[2]: *** [package/install] Error 255 make[2]: Leaving directory `/home/bjonglez/lede' make[1]: *** [/home/bjonglez/lede/staging_dir/target-mips_24kc_musl-1.1.15/stamp/.package_install] Error 2 make[1]: Leaving directory `/home/bjonglez/lede' make: *** [world] Error 2 Jow, does this have the potential to break the buildbot setup? Baptiste signature.asc Description: PGP signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices
From: Jaylin Yu OpenMesh devices have often LEDs which are not yet used by OpenWrt. These should still be available as disabled LEDs in the system configuration for easier modification. Signed-off-by: Jaylin Yu [sven.eckelm...@open-mesh.com: Remove LEDs already specified via diag.sh, add wifi/status LEDs] Signed-off-by: Sven Eckelmann --- target/linux/ar71xx/base-files/etc/board.d/01_leds | 27 ++ 1 file changed, 27 insertions(+) diff --git a/target/linux/ar71xx/base-files/etc/board.d/01_leds b/target/linux/ar71xx/base-files/etc/board.d/01_leds index cde3a94..523ba20 100755 --- a/target/linux/ar71xx/base-files/etc/board.d/01_leds +++ b/target/linux/ar71xx/base-files/etc/board.d/01_leds @@ -285,18 +285,31 @@ mr18) ;; mr600) ucidef_set_led_wlan "wlan58" "WLAN58" "$board:green:wlan58" "phy0tpt" + ucidef_set_led_default "wps" "WPS" "mr600:blue:wps" "0" + ;; +mr600v2) + ucidef_set_led_default "wlan24-red" "WLAN 2.4GHz (red)" "mr600:red:wlan24" "0" + ucidef_set_led_default "wlan24-yellow" "WLAN 2.4GHz (yellow)" "mr600:yellow:wlan24" "0" + ucidef_set_led_wlan "wlan24-green" "WLAN 4GHz (green)" "mr600:green:wlan24" "phy1tpt" + ucidef_set_led_default "wlan5-red" "WLAN 5GHz (red)" "mr600:red:wlan58" "0" + ucidef_set_led_default "wlan5-yellow" "WLAN 5GHz (yellow)" "mr600:yellow:wlan58" "0" + ucidef_set_led_wlan "wlan5-green" "WLAN 5GHz (green)" "mr600:green:wlan58" "phy0tpt" ;; mr1750|\ mr1750v2) ucidef_set_led_netdev "lan" "LAN" "mr1750:blue:wan" "eth0" ucidef_set_led_wlan "wlan58" "WLAN58" "mr1750:blue:wlan58" "phy0tpt" ucidef_set_led_wlan "wlan24" "WLAN24" "mr1750:blue:wlan24" "phy1tpt" + ucidef_set_led_default "status-red" "Status (red)" "mr1750:red:wifi" "0" + ucidef_set_led_default "status-green" "Status (green)" "mr1750:green:wifi" "0" ;; mr900|\ mr900v2) ucidef_set_led_netdev "lan" "LAN" "mr900:blue:wan" "eth0" ucidef_set_led_wlan "wlan24" "WLAN24" "mr900:blue:wlan24" "phy0tpt" ucidef_set_led_wlan "wlan58" "WLAN58" "mr900:blue:wlan58" "phy1tpt" + ucidef_set_led_default "status-red" "Status (red)" "mr900:red:wifi" "0" + ucidef_set_led_default "status-green" "Status (green)" "mr900:green:wifi" "0" ;; mynet-n600) ucidef_set_led_netdev "wan" "WAN" "wd:blue:internet" "eth1" @@ -343,15 +356,29 @@ om2p-hsv3|\ om2p-lc) ucidef_set_led_netdev "port1" "port1" "om2p:blue:wan" "eth0" ucidef_set_led_netdev "port2" "port2" "om2p:blue:lan" "eth1" + ucidef_set_led_default "wlan-red" "WLAN (red)" "om2p:red:wifi" "0" + ucidef_set_led_default "wlan-yellow" "WLAN (yellow)" "om2p:yellow:wifi" "0" + ucidef_set_led_default "wlan-green" "WLAN (green)" "om2p:green:wifi" "0" ;; om5p|\ om5p-an) ucidef_set_led_netdev "port1" "port1" "om5p:blue:wan" "eth0" ucidef_set_led_netdev "port2" "port2" "om5p:blue:lan" "eth1" + ucidef_set_led_default "wlan-red" "WLAN (red)" "om5p:red:wifi" "0" + ucidef_set_led_default "wlan-yellow" "WLAN (yellow)" "om5p:yellow:wifi" "0" + ucidef_set_led_default "wlan-green" "WLAN (green)" "om5p:green:wifi" "0" ;; om5p-ac) ucidef_set_led_netdev "port1" "port1" "om5pac:blue:lan" "eth0" ucidef_set_led_netdev "port2" "port2" "om5pac:blue:wan" "eth1" + ucidef_set_led_default "wlan-red" "WLAN (red)" "om5pac:red:wifi" "0" + ucidef_set_led_default "wlan-yellow" "WLAN (yellow)" "om5pac:yellow:wifi" "0" + ucidef_set_led_default "wlan-green" "WLAN (green)" "om5pac:green:wifi" "0" + ;; +om5p-acv2) + ucidef_set_led_default "wlan-red" "WLAN (red)" "om5pac:red:wifi" "0" + ucidef_set_led_default "wlan-yellow" "WLAN (yellow)" "om5pac:yellow:wifi" "0" + ucidef_set_led_default "wlan-green" "WLAN (green)" "om5pac:green:wifi" "0" ;; omy-g1) ucidef_set_led_wlan "wlan" "WLAN" "omy:green:wlan" "phy0tpt" -- 2.10.2 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ext4 / no space left on device / UML
Bastian Bittorf writes: > * Bjørn Mork [11.11.2016 14:58]: >> > in fact there is enough space, but not useable. >> >> And "df -i" says? > > this seems not supported by the busybox applet, but > on the host i can see this: > > bastian@LEDE:/home/bastian/ledebot/source$ tune2fs -l > bin/targets/uml/generic/lede-uml-ext4.img > tune2fs 1.42.13 (17-May-2015) > Filesystem volume name: > Last mounted on: / > Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b > Filesystem magic number: 0xEF53 > Filesystem revision #:1 (dynamic) > Filesystem features: ext_attr resize_inode filetype extent > sparse_super large_file uninit_bg > Filesystem flags: unsigned_directory_hash > Default mount options:(none) > Filesystem state: clean > Errors behavior: Remount read-only > Filesystem OS type: Linux > Inode count: 1024 > Block count: 4096 > Reserved block count: 0 > Free blocks: 875 > Free inodes: 0 > First block: 0 > Block size: 4096 > Fragment size:4096 > Reserved GDT blocks: 7 > Blocks per group: 32768 > Fragments per group: 32768 > Inodes per group: 1024 > Inode blocks per group: 64 > Last mount time: Fri Nov 11 14:43:21 2016 > Last write time: Fri Nov 11 14:43:04 2016 > Mount count: 1 > Maximum mount count: -1 > Last checked: Fri Nov 11 14:43:04 2016 > Check interval: 0 () > Lifetime writes: 652 kB > Reserved blocks uid: 0 (user root) > Reserved blocks gid: 0 (group root) > First inode: 11 > Inode size: 256 > Required extra isize: 28 > Desired extra isize: 28 > Default directory hash: tea > Journal backup: inode blocks > > can you read something interesting? Sure. "Free inodes: 0" is not good. And what was I suspected. We've all been there in the past ;) Can you reduce the number of small files on this file system somehow? If not, then you need to recreate it. AFAIK there is no way to adjust the inode count of an existing file system. Bjørn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ext4 / no space left on device / UML
* Bjørn Mork [11.11.2016 14:58]: > > in fact there is enough space, but not useable. > > And "df -i" says? this seems not supported by the busybox applet, but on the host i can see this: bastian@LEDE:/home/bastian/ledebot/source$ tune2fs -l bin/targets/uml/generic/lede-uml-ext4.img tune2fs 1.42.13 (17-May-2015) Filesystem volume name: Last mounted on: / Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: ext_attr resize_inode filetype extent sparse_super large_file uninit_bg Filesystem flags: unsigned_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Remount read-only Filesystem OS type: Linux Inode count: 1024 Block count: 4096 Reserved block count: 0 Free blocks: 875 Free inodes: 0 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 7 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 1024 Inode blocks per group: 64 Last mount time: Fri Nov 11 14:43:21 2016 Last write time: Fri Nov 11 14:43:04 2016 Mount count: 1 Maximum mount count: -1 Last checked: Fri Nov 11 14:43:04 2016 Check interval: 0 () Lifetime writes: 652 kB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Default directory hash: tea Journal backup: inode blocks can you read something interesting? bye, bastian ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ext4 / no space left on device / UML
Bastian Bittorf writes: > i'am using LEDE with target UML and rr2155 and has this problem: > > root@uml:/ df -h > FilesystemSize Used Available Use% Mounted on > /dev/root15.7M 12.3M 3.1M 80% / > tmpfs12.5M320.0K 12.2M 3% /tmp > tmpfs 512.0K 0512.0K 0% /dev > tmpfs 128.0K 0128.0K 0% /coredumps > > root@uml:/ touch /etc/config/test > touch: /etc/config/test: No space left on device > > > in fact there is enough space, but not useable. And "df -i" says? Bjørn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] ext4 / no space left on device / UML
i'am using LEDE with target UML and rr2155 and has this problem: root@uml:/ df -h FilesystemSize Used Available Use% Mounted on /dev/root15.7M 12.3M 3.1M 80% / tmpfs12.5M320.0K 12.2M 3% /tmp tmpfs 512.0K 0512.0K 0% /dev tmpfs 128.0K 0128.0K 0% /coredumps root@uml:/ touch /etc/config/test touch: /etc/config/test: No space left on device in fact there is enough space, but not useable. it seems this is the culprit: https://blog.merovius.de/2013/10/20/ext4-mysterious-no-space-left-on.html did we changed something with ext4? maybe this is even a problem on real disks. btw: can we link the bugtracker on the main page? bye, bastian ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt] rpcd-mod-nosql - prpl funding proposal
On Thu, Nov 10, 2016 at 11:34:48AM +0100, Luka Perkov wrote: > can you define the session namespace and how this existing feature can > be used? The team has looked in into it and the session object from rpcd providing get and set support looks like a good start, but I don't see it fulfilling the use cases like we mentioned in the document, where data is not associated with any user login or session. For example, in the proposal we mention system-level data storage like DSL statistics or connected device histories. The way I see with the session object would be to attach all such data to the unauthenticated session, but this way there's no access control, so that's not convenient for more sensitive data. Also, we would like to put some additional control level such as, allow to be a maximum of 100 entries in one "key" and flush out the oldest entries one when new entries are pushed. That way the rpcd-mod-nosql would handle part of the logic and we can avoid doing that in scripts or daemons. This is both a community and industry feature. For example in LuCI when you login to the statistics page it starts showing data from that moment. With this it can have back-end to pull the date from the database and show graphs for the last X seconds right away. Luka ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
