Re: [LEDE-DEV] QCA Dakota support

2016-11-12 Thread Ben Greear 

Have you tried the ath10k-ct driver?  I think it should at least
support the radios if you put on the right firmware.  Not sure about the rest 
of the board.

Thanks,
Ben

On 11/12/2016 09:42 AM, Matthew McClintock wrote:

On Fri, Nov 11, 2016 at 5:03 PM, Christian Mehlis  wrote:

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.


I can't help much, since QCA declined to give me a board. Did you try
regenerating the compat-wireless against the newer kernel? I never did
much on the wifi side, was alway doing everything else.

If you compare the ChromeOS tree I shared it's a backport to 3.18, so
some subset of patches in that list will backport to 4.4 pretty
easily.

-M

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev



--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] QCA Dakota support

2016-11-12 Thread Matthew McClintock 
On Fri, Nov 11, 2016 at 5:03 PM, Christian Mehlis  wrote:
> 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.

I can't help much, since QCA declined to give me a board. Did you try
regenerating the compat-wireless against the newer kernel? I never did
much on the wifi side, was alway doing everything else.

If you compare the ChromeOS tree I shared it's a backport to 3.18, so
some subset of patches in that list will backport to 4.4 pretty
easily.

-M

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.31

2016-11-12 Thread Koen Vandeputte 
+ Refresh patches
compile/run-tested on cns3xxx & imx6.

Signed-off-by: Koen Vandeputte 
---
 include/kernel-version.mk  |  4 ++--
 ...-override-creds-with-the-ones-from-the-superblock.patch |  6 +++---
 .../patches-4.4/052-01-ubifs-Implement-O_TMPFILE.patch |  2 +-
 .../052-02-ubifs-Implement-RENAME_WHITEOUT.patch   | 14 +++---
 .../052-03-ubifs-Implement-RENAME_EXCHANGE.patch   |  6 +++---
 ...ac-stop-clearing-DMA-receive-control-register-rig.patch |  9 ++---
 .../linux/generic/patches-4.4/201-extra_optimization.patch |  4 ++--
 7 files changed, 20 insertions(+), 25 deletions(-)

diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index f406719..13d39fb 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -4,11 +4,11 @@ LINUX_RELEASE?=1
 
 LINUX_VERSION-3.18 = .43
 LINUX_VERSION-4.1 = .34
-LINUX_VERSION-4.4 = .30
+LINUX_VERSION-4.4 = .31
 
 LINUX_KERNEL_MD5SUM-3.18.43 = b1faeb4a2e1e70ffe061bdbb3452840a
 LINUX_KERNEL_MD5SUM-4.1.34 = fba99f0f4765ebf01033e69518740a3c
-LINUX_KERNEL_MD5SUM-4.4.30 = 
9d249133bd12dde04f434bb4a5a4a23dd42ead721803c0ba4b5742efd239995c
+LINUX_KERNEL_MD5SUM-4.4.31 = 29d9b0b1aa4dec3eb1a9edf1b84e79c5
 
 ifdef KERNEL_PATCHVER
   LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git 
a/target/linux/generic/patches-4.4/051-0002-ovl-override-creds-with-the-ones-from-the-superblock.patch
 
b/target/linux/generic/patches-4.4/051-0002-ovl-override-creds-with-the-ones-from-the-superblock.patch
index eed7bb2..208bc61 100644
--- 
a/target/linux/generic/patches-4.4/051-0002-ovl-override-creds-with-the-ones-from-the-superblock.patch
+++ 
b/target/linux/generic/patches-4.4/051-0002-ovl-override-creds-with-the-ones-from-the-superblock.patch
@@ -58,7 +58,7 @@ Signed-off-by: Miklos Szeredi 
 
 --- a/fs/overlayfs/copy_up.c
 +++ b/fs/overlayfs/copy_up.c
-@@ -315,7 +315,6 @@ int ovl_copy_up_one(struct dentry *paren
+@@ -317,7 +317,6 @@ int ovl_copy_up_one(struct dentry *paren
struct dentry *upperdir;
struct dentry *upperdentry;
const struct cred *old_cred;
@@ -66,7 +66,7 @@ Signed-off-by: Miklos Szeredi 
char *link = NULL;
  
if (WARN_ON(!workdir))
-@@ -334,28 +333,7 @@ int ovl_copy_up_one(struct dentry *paren
+@@ -336,28 +335,7 @@ int ovl_copy_up_one(struct dentry *paren
return PTR_ERR(link);
}
  
@@ -96,7 +96,7 @@ Signed-off-by: Miklos Szeredi 
  
err = -EIO;
if (lock_rename(workdir, upperdir) != NULL) {
-@@ -378,9 +356,7 @@ int ovl_copy_up_one(struct dentry *paren
+@@ -380,9 +358,7 @@ int ovl_copy_up_one(struct dentry *paren
  out_unlock:
unlock_rename(workdir, upperdir);
revert_creds(old_cred);
diff --git 
a/target/linux/generic/patches-4.4/052-01-ubifs-Implement-O_TMPFILE.patch 
b/target/linux/generic/patches-4.4/052-01-ubifs-Implement-O_TMPFILE.patch
index 957935c..1c55a89 100644
--- a/target/linux/generic/patches-4.4/052-01-ubifs-Implement-O_TMPFILE.patch
+++ b/target/linux/generic/patches-4.4/052-01-ubifs-Implement-O_TMPFILE.patch
@@ -89,7 +89,7 @@ Signed-off-by: Richard Weinberger 
  /**
   * vfs_dent_type - get VFS directory entry type.
   * @type: UBIFS directory entry type
-@@ -1189,6 +1259,7 @@ const struct inode_operations ubifs_dir_
+@@ -1195,6 +1265,7 @@ const struct inode_operations ubifs_dir_
  #ifdef CONFIG_UBIFS_ATIME_SUPPORT
.update_time = ubifs_update_time,
  #endif
diff --git 
a/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch 
b/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
index dd75ef4..c2ec904 100644
--- 
a/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
+++ 
b/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
@@ -65,7 +65,7 @@ Signed-off-by: Richard Weinberger 
  /**
   * vfs_dent_type - get VFS directory entry type.
   * @type: UBIFS directory entry type
-@@ -997,37 +1016,43 @@ out_budg:
+@@ -1003,37 +1022,43 @@ out_budg:
  }
  
  /**
@@ -116,7 +116,7 @@ Signed-off-by: Richard Weinberger 
if (inode3)
mutex_unlock(_inode(inode3)->ui_mutex);
if (inode1 != inode2)
-@@ -1036,12 +1061,15 @@ static void unlock_3_inodes(struct inode
+@@ -1042,12 +1067,15 @@ static void unlock_3_inodes(struct inode
  }
  
  static int ubifs_rename(struct inode *old_dir, struct dentry *old_dentry,
@@ -133,7 +133,7 @@ Signed-off-by: Richard Weinberger 
int err, release, sync = 0, move = (new_dir != old_dir);
int is_dir = S_ISDIR(old_inode->i_mode);
int unlink = !!new_inode;
-@@ -1063,9 +1091,13 @@ static int ubifs_rename(struct inode *ol
+@@ -1069,9 +1097,13 @@ static int ubifs_rename(struct inode *ol
 * separately.

[LEDE-DEV] [PATCH v2 2/3] apm821xx: consolidate apm821xx device trees files

2016-11-12 Thread Christian Lamparter 
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, IRQ and
input definitions of the supported platforms to use the
defined dt-bindings macros for GPIO_ACTIVE_LOW|HIGH,
KEY_WPS|RESTART|*, IRQ_TYPE_* when it's appropriate.

Signed-off-by: Christian Lamparter 
---
v1->v2:
- also converted IRQ_TYPEs
- rebased on LEDE's current HEAD
- drop default LED triggers for the MBL
  (except for the panic indicators. They have to work as soon
  as possible. So they can indicate if the rootfs on the HDD
  is damaged, etc...)
---
 target/linux/apm821xx/dts/MR24.dts | 472 +++
 target/linux/apm821xx/dts/apm82181.dtsi| 470 +++
 target/linux/apm821xx/dts/apollo3g-duo.dts |  19 +
 target/linux/apm821xx/dts/apollo3g.dts |  18 -
 target/linux/apm821xx/dts/apollo3g.dtsi| 569 --
 target/linux/apm821xx/dts/wndr4700.dts | 914 +
 6 files changed, 990 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 = 
-   serial0 = 
+   serial0 = 
};
 
-   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 = <>;
-   };
+   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 = <>;
-   };
+ {
+   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 = <>;
-   };
+ {
+   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 = <>;
-   };
+ {
+   status = "okay";
+};
 
-   /* KPH check the following */
-   OCM: ocm@40004 {
-   compatible = "ibm,ocm";
+ {
+   /* 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";
-

[LEDE-DEV] [PATCH v2 1/3] apm821xx: add amcc, usb-otg-405ex devicetree definition

2016-11-12 Thread Christian Lamparter 
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 = _amcc_dwc_otg },
+   { .compatible = "brcm,bcm2835-usb", .data = _bcm2835 },
-- 
2.10.2


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH v2 3/3] apm821xx: remove replaced netgear, wndr4700-usb dwc2 definiton

2016-11-12 Thread Christian Lamparter 
This special dwc2 device definition for the Netgear WNDR4700
has been replaced by amcc,usb-otg-405ex.

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 = _bcm2835 },
-   { .compatible = "rockchip,rk3066-usb", .data = _rk3066 },
-+  { .compatible = "netgear,wndr4700-usb", .data = _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

Re: [LEDE-DEV] [PATCH v1 2/3] apm821xx: consolidate apm821xx device trees files

2016-11-12 Thread Christian Lamparter 
On Saturday, November 12, 2016 9:53:19 AM CET Mathias Kresin wrote:
> 11.11.2016 18:08, Christian Lamparter:
> > diff --git a/target/linux/apm821xx/dts/apollo3g.dtsi 
> > b/target/linux/apm821xx/dts/apollo3g.dtsi
> > index 30a4dfe..853757b 100644
> > --- a/target/linux/apm821xx/dts/apollo3g.dtsi
> > +++ b/target/linux/apm821xx/dts/apollo3g.dtsi
> 
> 
> 
> > +   gpio-leds {
> > +   compatible = "gpio-leds";
> >
> > -   SATA1: sata@bffd1800 {
> > -   compatible = "amcc,sata-460ex";
> > -   reg = <4 0xbffd1800 0x800>;
> > -   interrupt-parent = <>;
> > -   interrupts = <27 4>;
> > -   dmas = < 1 0 2>;
> > -   dma-names = "sata-dma";
> > +   power-red {
> > +   label = "mbl:red:power";
> > +   gpios = < 4 0>;
> > +   linux,default-trigger = "panic";
> > };
> >
> > -
> > -   USBOTG0: usbotg@bff8 {
> > -   compatible = "snps,dwc2";
> > -   reg = <4 0xbff8 0x1>;
> > -   interrupt-parent = <>;
> > -   interrupts = <0 1 2>;
> > -   #interrupt-cells = <1>;
> > -   #address-cells = <0>;
> > -   #size-cells = <0>;
> > -   interrupt-map =  > -/* HIGH-POWER */ 1  0x1a 8
> > -/* DMA */ 2  0xc 4>;
> > -   dr_mode = "host";
> > +   power-green {
> > +   label = "mbl:green:power";
> > +   gpios = < 5 0>;
> > +   linux,default-trigger = "default-on";
> 
> This one look wrong to me. Would you please fix this and use 
> default-state = "on" here[0].
Thanks. I removed it, these triggers came from a debian testing
dts. Since LEDE has out-of-the-box support for platform LEDs, 
these are not needed, since "mbl:green:power" is used as the
status LED.

> > -   gpio-leds {
> > -   compatible = "gpio-leds";
> > -   power-red {
> > -   label = "mbl:red:power";
> > -   gpios = < 4 0>;
> > -   linux,default-trigger = "panic";
> > -   };
> > -   power-green {
> > -   label = "mbl:green:power";
> > -   gpios = < 5 0>;
> > -   linux,default-trigger = "default-on";
> > -   };
> > -   power-blue {
> > -   label = "mbl:blue:power";
> > -   gpios = < 6 0>;
> > -   linux,default-trigger = "disk-activity";
> 
> The patch fails do apply at this line. The default trigger is "cpu0" in 
> HEAD.
I removed this as well. The only default-trigger I left is the
panic LED. Ideally, this can be done via the panic-indicator
property [1]. however, there's no support for it in 4.4.

> Would you please send a patch based on HEAD without local modifications.
Yes, I'll submit v2 shortly.

Thanks,
Christian
 
> [0] 
> https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/leds-gpio.txt
[1] 



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Documentation for router support means the famous Table of Hardware

2016-11-12 Thread Paul Oranje 
l.s.

For a heritage wiki that I helped set-up a few years ago 
(www.culturalheritageconnections.org) a combination of structured data and 
“normal” unstructured information was used.

This set-up deploys semantic extensions to mediawiki where the structured data 
is captured in semantic properties and edited by means of semantic forms that 
ensure that certain information is automatically assigned to the semantic 
properties. Most if not all structured data is shown on the pages in so-called 
info boxes (like in wilipedia), and the information can be searched by 
properties, by category (really also a property) and also semantic query forms. 
An initial set of such pages can be generated from data contained in an SQL 
database.

In short: a wiki that combines structured data with more or less unstructured 
information is very well possible and the existing dataset can be used as a 
start where all structured data is converted into semantic properties.

Regards,
-- 
Paul Oranje


> Op 14 sep. 2016, om 00:57 heeft Jo-Philipp Wich  het volgende 
> geschreven:
> 
> Hi Tarek,
> 
> Thomas Endt and others invested a lot of time to implement a structured
> table of hardware in the OpenWrt wiki, which means that a lot of detail
> information is accessible in a SQLite3 database file which should make
> it easy to generate hardware documentation pages with a little script
> and a few self-join queries.
> 
> I also think that such a model would be a viable option for the future:
> have a structured data entry dialog in the wiki which fills a database,
> have all the surrounding wiki capabilities for free text information and
> use the resulting database backend data to provide other, non-wiki
> services like a vendor/model search to to download link redirection.
> 
> 
> Imho a well maintained hardware database is a very important topic for
> LEDE, OpenWrt and other associated projects but we need to find a sane
> middle ground that does not upset too many potential contributors but
> still yields a reasonable data quality...
> 
> On a related note I wonder if anyone ever thought about joining forces
> with WikiDevi? It seems like a perfectly reasonable thing to do but I
> recall that the site operators are rather hard to contact.
> 
> 
> Just my two cents :)
> 
> Regards,
> Jo
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev




___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [RFC] ADSL Modem Allnet All0333CJ Rev.C / Amazon-SE SoC

2016-11-12 Thread Tino Reichardt 
* Mathias Kresin  wrote:
> 07.11.2016 19:02, Tino Reichardt:
> > Now I have to check, how to start the init...
> >
> > Is there currently any golden way, how the init should be done on these
> > devices, with very small flash memory?
> >
> > I also modify the .config, to fit the drivers of the allnet ;)
> 
> In menuconfig => "Target Images" you can select the ramdisk option.
> 
> This will create kernel + initramfs. The resulting binary can be loaded 
> with tftpboot and should boot to a prompt without relying on 
> flash/filesystem support.

Hm... hello Mathias, thanks for your reply, I have tried this and it
seems not to work currently. I have no idea why.

But I have prepared a small temporary site, which I will use for this
stuff ...

It contains the current patch against lede-project.git and some
logfiles with .config's of lede + linux kernel:

http://internethauptknotenpunkt.de/all0333/

The Amazon-SE code from kernel seems to work, I think it's my false
currently...

PS: And I found the reason, why I had to give mem=16M to the kernel
commandline, the amazonse.dtsi missed these definition:

+   memory@0 {
+   device_type = "memory";
+   };
+

-- 
Best regards, TR

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] include: image.mk: ext4: double the default inode counter

2016-11-12 Thread Bastian Bittorf 
* Bastian Bittorf  [12.11.2016 09:54]:
> +# doubles the default inode amount
> +INODES=$(shell echo $$(($(CONFIG_TARGET_ROOTFS_PARTSIZE)*64*2)))
>  E2SIZE=$(shell echo $$(($(CONFIG_TARGET_ROOTFS_PARTSIZE)*1024*1024)))

bye the way:
i mimic'ed the existing style, but is'nt this too much?
can't this be expressed like this:

INODES=$(( $(CONFIG_TARGET_ROOTFS_PARTSIZE)*64*2 ))

(instead of explicitely calling the shell)

bye, bastian

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] ar71xx: swconfig does not reflect changes

2016-11-12 Thread Bastian Bittorf 
* mil...@betternet.co  [12.11.2016 09:54]:
> I own an ar71xx bboard (GL-6416 to be exact). Whether the ethernet
> cable is connected to WAN port or not, running `swconfig dev switch0
> show` returns the following:

your WAN is a MII-style device, which is not "supported" from swconfig.

try this:
devstatus "$WANDEV" | grep '"speed": '

bye, bastian

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH v1 2/3] apm821xx: consolidate apm821xx device trees files

2016-11-12 Thread Mathias Kresin 

11.11.2016 18:08, Christian Lamparter:

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/apollo3g.dtsi 
b/target/linux/apm821xx/dts/apollo3g.dtsi
index 30a4dfe..853757b 100644
--- a/target/linux/apm821xx/dts/apollo3g.dtsi
+++ b/target/linux/apm821xx/dts/apollo3g.dtsi





+   gpio-leds {
+   compatible = "gpio-leds";

-   SATA1: sata@bffd1800 {
-   compatible = "amcc,sata-460ex";
-   reg = <4 0xbffd1800 0x800>;
-   interrupt-parent = <>;
-   interrupts = <27 4>;
-   dmas = < 1 0 2>;
-   dma-names = "sata-dma";
+   power-red {
+   label = "mbl:red:power";
+   gpios = < 4 0>;
+   linux,default-trigger = "panic";
};

-
-   USBOTG0: usbotg@bff8 {
-   compatible = "snps,dwc2";
-   reg = <4 0xbff8 0x1>;
-   interrupt-parent = <>;
-   interrupts = <0 1 2>;
-   #interrupt-cells = <1>;
-   #address-cells = <0>;
-   #size-cells = <0>;
-   interrupt-map = ;
-   dr_mode = "host";
+   power-green {
+   label = "mbl:green:power";
+   gpios = < 5 0>;
+   linux,default-trigger = "default-on";


This one look wrong to me. Would you please fix this and use 
default-state = "on" here[0].



-   gpio-leds {
-   compatible = "gpio-leds";
-   power-red {
-   label = "mbl:red:power";
-   gpios = < 4 0>;
-   linux,default-trigger = "panic";
-   };
-   power-green {
-   label = "mbl:green:power";
-   gpios = < 5 0>;
-   linux,default-trigger = "default-on";
-   };
-   power-blue {
-   label = "mbl:blue:power";
-   gpios = < 6 0>;
-   linux,default-trigger = "disk-activity";


The patch fails do apply at this line. The default trigger is "cpu0" in 
HEAD.


Would you please send a patch based on HEAD without local modifications.

Mathias

[0] 
https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/leds-gpio.txt


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] ar71xx: swconfig does not reflect changes

2016-11-12 Thread Cezary Jackiewicz 
Dnia 2016-11-12, o godz. 12:07:44
mil...@betternet.co napisał(a):

> I own an ar71xx bboard (GL-6416 to be exact). Whether the ethernet cable 
> is connected to WAN port or not, running `swconfig dev switch0 show` 
> returns the following:
[...]
> Is it usual behavior? I suppose not, since my other router (mt762a) 
> works as expected, that is it reflects the changes for the WAN port.

Because wan is eth1 (not eth0 - switch)?

-- 
Pozdrawiam,
 Cezary Jackiewicz

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] ar71xx: swconfig does not reflect changes

2016-11-12 Thread milani 
I own an ar71xx bboard (GL-6416 to be exact). Whether the ethernet cable 
is connected to WAN port or not, running `swconfig dev switch0 show` 
returns the following:


```
Global attributes:
enable_vlan: 0
Port 0:
pvid: 0
link: port:0 link:up speed:1000baseT full-duplex txflow rxflow
Port 1:
pvid: 0
link: port:1 link:down
Port 2:
pvid: 0
link: port:2 link:down
Port 3:
pvid: 0
link: port:3 link:down
Port 4:
pvid: 0
link: port:4 link:down
VLAN 0:
vid: 0
ports: 0 1 2 3 4
```

But if I connect the cable to the LAN port, the result is:

```
Global attributes:
enable_vlan: 0
Port 0:
pvid: 0
link: port:0 link:up speed:1000baseT full-duplex txflow rxflow
Port 1:
pvid: 0
link: port:1 link:up speed:100baseT full-duplex auto
Port 2:
pvid: 0
link: port:2 link:down
Port 3:
pvid: 0
link: port:3 link:down
Port 4:
pvid: 0
link: port:4 link:down
VLAN 0:
vid: 0
ports: 0 1 2 3 4
```

Is it usual behavior? I suppose not, since my other router (mt762a) 
works as expected, that is it reflects the changes for the WAN port.


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] include: image.mk: ext4: double the default inode counter

2016-11-12 Thread Bastian Bittorf 
A rootfs typically has lots of small files, so the default
counter with 1024 inodes for 16 megabytes partition size can
be too restrictive and leads to e.g.

root@box:/ touch /etc/config/test
touch: /etc/config/test: No space left on device

the solution is to just double the amount of inodes
during image creation, so a 16mb part has 2048 inodes.

see also:
http://lists.infradead.org/pipermail/lede-dev/2016-November/003977.html

Signed-off-by: Bastian Bittorf 
---
 include/image.mk | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/include/image.mk b/include/image.mk
index 8b183ab..e74a71d 100644
--- a/include/image.mk
+++ b/include/image.mk
@@ -239,11 +239,13 @@ define Image/mkfs/ubifs
-o $@ -d $(call mkfs_target_dir,$(1))
 endef
 
+# doubles the default inode amount
+INODES=$(shell echo $$(($(CONFIG_TARGET_ROOTFS_PARTSIZE)*64*2)))
 E2SIZE=$(shell echo $$(($(CONFIG_TARGET_ROOTFS_PARTSIZE)*1024*1024)))
 
 define Image/mkfs/ext4
$(STAGING_DIR_HOST)/bin/make_ext4fs \
-   -l $(E2SIZE) -b $(CONFIG_TARGET_EXT4_BLOCKSIZE) \
+   -l $(E2SIZE) -i $(INODES) -b $(CONFIG_TARGET_EXT4_BLOCKSIZE) \
$(if $(CONFIG_TARGET_EXT4_RESERVED_PCT),-m 
$(CONFIG_TARGET_EXT4_RESERVED_PCT)) \
$(if $(CONFIG_TARGET_EXT4_JOURNAL),,-J) \
$(if $(SOURCE_DATE_EPOCH),-T $(SOURCE_DATE_EPOCH)) \
-- 
1.9.1


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] Use printf instead of echo.

2016-11-12 Thread Bastian Bittorf 
* Felix Fietkau  [23.08.2016 13:59]:
> > For now, the change I submitted is whats needed to fix breakage on my 
> > system. For others, I will send patches if no one takes it up in a few days.
> Actually, you might be able to simplify the change even more by forcing
> the hostapd build shell to bash (some other packages do this as well).

this look simple, but in the long run...

# "Stick to portable constructs where possible, and
#  you will make somebody's life easier in the future.
#  Maybe your own."

so using /bin/sh with 'printf' is safe.
(no matter which underlying shell-interpreter we use)

bye, bastian

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev