Re: [OpenWrt-Devel] openwrt gpsd compilation fail

2015-11-17 Thread Dirk Neukirchen 
On 12.11.2015 20:41, Pushpal Sidhu wrote:
> Hi Luigi,
> 
> On Thu, Nov 12, 2015 at 9:27 AM, luigi findanno  wrote:
>>
>> Hi, I'm trying to compile openwrt for raspberry pi but I found this error:
>>
>> http://pastebin.com/yQFhza8Y
>>
>> I don't know how to go on. I found your email in the Makefile and I'll be 
>> happy if you can help me.
>> Regards
>> Luigi Findanno
> 
> 
> I just pulled down the latest openwrt and latest packages and built
> gpsd, gpsd-clients, and libgps for an arm cortex-a9. I then selected
> the Raspberry Pi 2 Model B target and built just fine, so I'm not
> totally sure what you're seeing. Can you run a 'strip --version' and
> give me that info please? I imagine that your tool needs to be
> updated.
> 
> - Pushpal
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 

This patch should fix this issue (it seems an option name was changed)
feel free to use/push to github packages repo

gpsd: fix strip in build

current SConstruct file contains a "nostrip" option

Signed-off-by: Dirk Neukirchen 
---
 utils/gpsd/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/utils/gpsd/Makefile b/utils/gpsd/Makefile
index df67cf8..2351f71 100644
--- a/utils/gpsd/Makefile
+++ b/utils/gpsd/Makefile
@@ -97,7 +97,7 @@ SCONS_OPTIONS += \
libgpsmm=no \
libQgpsmm=no \
bluez=no \
-   strip=no \
+   nostrip=yes \
python=no \
implicit_link=no \
chrpath=no
-- 
2.6.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] mac80211: Add dependency on ip (iproute2) to cfg80211

2015-11-17 Thread Luiz Angelo Daros de Luca 
Is there a way to add "provides" to a package? In RPM, I would solve this
adding "Provides: ip" to busybox.

This could also help when a kern module gets built-in. Kernel package could
provide the incorporated kmod-xxx module. It would be better if both kernel
and kmod-xxx could automatically provide every single module it provides,
so packages could requires modules and not their packages, whether it is
built-in or loadable module.

Just like the case of busybox, if someone changes a module to not be
built-in (a configuration), it will require a code (makefile) change in
order to fix broken deps.

Luiz

Em ter, 17 de nov de 2015 06:11, Cristian Morales Vega <
crist...@samknows.com> escreveu:

> On 16 November 2015 at 23:40, Felix Fietkau  wrote:
> > On 2015-11-16 20:28, Ted Hess wrote:
> >> Changes to netifd/wireless/mac80211.sh in r46832 invoke 'ip' when making
> >> a client association. 'ip' is not automatically included with cfg80211
> >> custom builds -- association fails.
> >>
> >> Signed-off-by: Ted Hess 
> > NACK. These changes were added because the busybox ip applet was enabled
> > by default recently.
>
> So there is a dependency (ip package OR ip support in Busybox), but no
> way to express it?
>
> Not that it would make sense for anybody to disable the new default in
> busybox without enabling the ip package at the same time. Just
> curious.
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
-- 

Luiz Angelo Daros de Luca
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v5] linux: add support of Synopsys ARC770-based boards

2015-11-17 Thread Alexey Brodkin 
Hi Felix, Jonas,

On Fri, 2015-11-13 at 21:39 +0300, Alexey Brodkin wrote:
> This patch introduces support of new boards with ARC cores.
> 
>  [1] Synopsys SDP board
>  This is a new-generation development board from Synopsys that
>  consists of base-board and CPU tile-board (which might have a real
>  ASIC or FPGA with CPU image).
>  It sports a lot of DesignWare peripherals like GMAC, USB, SPI, I2C
>  etc and is intended to be used for early development of ARC-based
>  products.
> 
>  [2] nSIM
>  This is a virtual board implemented in Synopsys proprietary
>  software simulator (even though available for free for open source
>  community). This board has only serial port as a peripheral and so
>  it is meant to be used for runtime testing which is especially
>  useful during bring-up of new tools and platforms.
>  What's also important ARC cores are very configurable so there're
>  many variations of options like cache sizes, their line lengths,
>  additional hardware blocks like multipliers, dividers etc. And this
>  board could be used to make sure built software still runs on
>  different HW configurations.
> 
> Cc: Felix Fietkau 
> Cc: Jo-Philipp Wich 
> Cc: Jonas Gorski 
> Signed-off-by: Alexey Brodkin 
> ---
> Changes compared to v4:
>  * Removed DTS variable from profile descriptions in
>target/linux/arc770/generic/profiles/0x-yyy
>  * Reworked board type detection in base-files/lib/arc.sh
>Now looking for a full match of "compatible" property.
> 
> Changes compared to v3:
>  * Accomodate new KERNEL_INITRAMFS_NAME variable for building .elfs
>  * Add and use "model" property in device tree description
>  * Remove extra console from kernel command line
>  * Use new buildsystem for resulting images
>  * Nuked ARC-specific inittab, use default one instead
>  * Linux kernel config is passed through "make kernel_oldconfig"
>  * eth0 is now LAN instead of WAN
> 
> Changes compared to v2:
>  * Fixed copyright dates
>  * Cleaned-up init scripts
> 
> Changes compared to v1:
>  * Switched to SoC-centered design. Now instead of common ARC700
>support we claim support of boards based on ARC770D.
>This allows to use the same one build of kernel binary for both
>boards.
>  * Implemented run-time scripts that parse Device Tree compatible
>tag and according to it do configuration of serial port and network.
>  * Implemented ability to patch in built Linux kernel external .dtb
>  * Linux kernel switched from 4.1 to 4.3
>  * Rebased on current master

Any comments on this one or there's a chance it could be applied?

-Alexey
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH v3 2/2] pinctrl/lantiq: adapt devicetrees to new tables

2015-11-17 Thread Martin Schiller 
This patch adapts the "pinctrl-xway" and "pinctrl-xr9" settings in the
dts files into dedicated "pinctrl-ase", "pinctrl-danube", "pinctrl-xrx100"
and "pinctrl-xrx200" settings.

Signed-off-by: Martin Schiller 
---
 target/linux/lantiq/dts/BTHOMEHUBV2B.dts | 2 +-
 target/linux/lantiq/dts/BTHOMEHUBV3A.dts | 2 +-
 target/linux/lantiq/dts/EASY50712.dts| 2 +-
 target/linux/lantiq/dts/EASY50810.dts| 2 +-
 target/linux/lantiq/dts/EASY80920.dtsi   | 2 +-
 target/linux/lantiq/dts/GR7000.dts   | 2 +-
 target/linux/lantiq/dts/P2601HNFX.dts| 2 +-
 target/linux/lantiq/dts/P2812HNUFX.dtsi  | 2 +-
 target/linux/lantiq/dts/VGV7519.dtsi | 2 +-
 target/linux/lantiq/dts/ar9.dtsi | 2 +-
 target/linux/lantiq/dts/danube.dtsi  | 2 +-
 target/linux/lantiq/dts/vr9.dtsi | 2 +-
 12 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/target/linux/lantiq/dts/BTHOMEHUBV2B.dts 
b/target/linux/lantiq/dts/BTHOMEHUBV2B.dts
index 9b3180c..e2d713e 100644
--- a/target/linux/lantiq/dts/BTHOMEHUBV2B.dts
+++ b/target/linux/lantiq/dts/BTHOMEHUBV2B.dts
@@ -102,7 +102,7 @@
};
 
gpio: pinmux@E100B10 {
-   compatible = "lantiq,pinctrl-xway";
+   compatible = "lantiq,pinctrl-danube";
pinctrl-names = "default";
pinctrl-0 = <_default>;
 
diff --git a/target/linux/lantiq/dts/BTHOMEHUBV3A.dts 
b/target/linux/lantiq/dts/BTHOMEHUBV3A.dts
index 1ae9840..9383498 100644
--- a/target/linux/lantiq/dts/BTHOMEHUBV3A.dts
+++ b/target/linux/lantiq/dts/BTHOMEHUBV3A.dts
@@ -79,7 +79,7 @@
};
 
gpio: pinmux@E100B10 {
-   compatible = "lantiq,pinctrl-xr9";
+   compatible = "lantiq,pinctrl-xrx100";
pinctrl-names = "default";
pinctrl-0 = <_default>;
 
diff --git a/target/linux/lantiq/dts/EASY50712.dts 
b/target/linux/lantiq/dts/EASY50712.dts
index e44267a..e0d5ed1 100644
--- a/target/linux/lantiq/dts/EASY50712.dts
+++ b/target/linux/lantiq/dts/EASY50712.dts
@@ -51,7 +51,7 @@
};
 
gpio: pinmux@E100B10 {
-   compatible = "lantiq,pinctrl-xway";
+   compatible = "lantiq,pinctrl-danube";
pinctrl-names = "default";
pinctrl-0 = <_default>;
 
diff --git a/target/linux/lantiq/dts/EASY50810.dts 
b/target/linux/lantiq/dts/EASY50810.dts
index 5f4b733..73f31ea 100644
--- a/target/linux/lantiq/dts/EASY50810.dts
+++ b/target/linux/lantiq/dts/EASY50810.dts
@@ -51,7 +51,7 @@
};
 
gpio: pinmux@E100B10 {
-   compatible = "lantiq,pinctrl-xr9";
+   compatible = "lantiq,pinctrl-xrx100";
pinctrl-names = "default";
pinctrl-0 = <_default>;
 
diff --git a/target/linux/lantiq/dts/EASY80920.dtsi 
b/target/linux/lantiq/dts/EASY80920.dtsi
index 4013610..0600d36 100644
--- a/target/linux/lantiq/dts/EASY80920.dtsi
+++ b/target/linux/lantiq/dts/EASY80920.dtsi
@@ -71,7 +71,7 @@
};
 
gpio: pinmux@E100B10 {
-   compatible = "lantiq,pinctrl-xr9";
+   compatible = "lantiq,pinctrl-xrx200";
pinctrl-names = "default";
pinctrl-0 = <_default>;
 
diff --git a/target/linux/lantiq/dts/GR7000.dts 
b/target/linux/lantiq/dts/GR7000.dts
index fcc27eb..bc95f1f 100644
--- a/target/linux/lantiq/dts/GR7000.dts
+++ b/target/linux/lantiq/dts/GR7000.dts
@@ -42,7 +42,7 @@
};
 
gpio: pinmux@E100B10 {
-   compatible = "lantiq,pinctrl-xr9";
+   compatible = "lantiq,pinctrl-xrx100";
pinctrl-names = "default";
pinctrl-0 = <_default>;
 
diff --git a/target/linux/lantiq/dts/P2601HNFX.dts 
b/target/linux/lantiq/dts/P2601HNFX.dts
index bb9193e..c22c547 100644
--- a/target/linux/lantiq/dts/P2601HNFX.dts
+++ b/target/linux/lantiq/dts/P2601HNFX.dts
@@ -50,7 +50,7 @@
};
 
gpio: pinmux@E100B10 {
-   compatible = "lantiq,pinctrl-xr9";
+   compatible = "lantiq,pinctrl-xrx100";
pinctrl-names = "default";
pinctrl-0 = <_default>;
 
diff --git a/target/linux/lantiq/dts/P2812HNUFX.dtsi 
b/target/linux/lantiq/dts/P2812HNUFX.dtsi
index d93e862..1dd13ac 100644
--- a/target/linux/lantiq/dts/P2812HNUFX.dtsi
+++ b/target/linux/lantiq/dts/P2812HNUFX.dtsi
@@ -25,7 +25,7 @@
};
 
gpio: pinmux@E100B10 {
-   compatible = "lantiq,pinctrl-xr9";
+   compatible = "lantiq,pinctrl-xrx200";
pinctrl-names = "default";
pinctrl-0 = <_default>;

Re: [OpenWrt-Devel] [PATCH] mac80211: Add dependency on ip (iproute2) to cfg80211

2015-11-17 Thread Felix Fietkau 
On 2015-11-17 12:59, Luiz Angelo Daros de Luca wrote:
> Is there a way to add "provides" to a package? In RPM, I would solve
> this adding "Provides: ip" to busybox.
> 
> This could also help when a kern module gets built-in. Kernel package
> could provide the incorporated kmod-xxx module. It would be better if
> both kernel and kmod-xxx could automatically provide every single module
> it provides, so packages could requires modules and not their packages,
> whether it is built-in or loadable module.
> 
> Just like the case of busybox, if someone changes a module to not be
> built-in (a configuration), it will require a code (makefile) change in
> order to fix broken deps.
I personally think changing package metadata for this this is a waste of
time. There are so many different ways in which you can screw up a build
by customizing the busybox configuration, and it would be a futile
effort to try to add checks for them all.

People that customize their busybox config should just check the output
of ./scripts/diffconfig.sh for any missing options if they run into any
issues. Problematic changes are typically very easily visible there,
since the output contains very few items aside from changes directly
made by the user or options that went out of sync with the default
configuration.

- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] [ramips] mt7621: fix nand driver

2015-11-17 Thread Daniel Golle 
On Sat, Nov 14, 2015 at 04:39:51PM +0900, YounJaeRho wrote:
> This patch fix mt7621 nand driver for linux-3.18 kernel.mt7621 share PIN 
> between NAND,SDXC,SPI.so you should pinctrl in dts file that only one of them 
> is used at a time.
> SQUASH supportJFFS2 support (no hardware ECC support which is disabled by 
> `CONFIG_TARGET_ROOTFS_JFFS2` )

Using JFFS2 on NAND is a bit whacky, you should probably use UBI.
If the bootloader doesn't support UBI, you should have a seperate
kernel partition and store both, rootfs and overlayfs in UBI.
See
https://dev.openwrt.org/browser/trunk/target/linux/lantiq/image/Makefile
for a bunch of good examples.

> 
> Signed-off-by: YounJae Rho -- 
> a/drivers/mtd/nand/mtk_nand.c
> +++ b/drivers/mtd/nand/mtk_nand.c
> @@ -42,6 +42,9 @@
>  #include "bmt.h"
>  #include "partition.h"
>  
> +#define NAND_MAX_OOBSIZE 640
> +#define NAND_MAX_PAGESIZE8192
> +
>  unsigned int CFG_BLOCKSIZE;
>  
>  static int shift_on_bbt = 0;
> @@ -1422,9 +1425,7 @@ mtk_nand_erase_hw(struct mtd_info *mtd,
>  {
>   struct nand_chip *chip = (struct nand_chip *)mtd->priv;
>  
> - chip->erase_cmd(mtd, page);
> -
> - return chip->waitfunc(mtd, chip);
> + return chip->erase(mtd, chip);
>  }
>  
>  static int
> @@ -2092,7 +2093,11 @@ mtk_nand_probe(struct platform_device *p
>  
>   // For BMT, we need to revise driver architecture
>   nand_chip->write_page = mtk_nand_write_page;
> + #if defined(CONFIG_TARGET_ROOTFS_JFFS2)
> + nand_chip->ecc.write_oob = NULL;
> + #else
>   nand_chip->ecc.write_oob = mtk_nand_write_oob;
> + #endif
>   nand_chip->block_markbad = mtk_nand_block_markbad;   // need to add 
> nand_get_device()/nand_release_device().
>   //  nand_chip->erase = mtk_nand_erase;  
>   //nand_chip->read_page = mtk_nand_read_page;
> @@ -2175,7 +2180,7 @@ mtk_nand_probe(struct platform_device *p
>   nand_chip->pagemask = (nand_chip->chipsize >> nand_chip->page_shift) - 
> 1;
>   nand_chip->phys_erase_shift = ffs(mtd->erasesize) - 1;
>   nand_chip->chip_shift = ffs(nand_chip->chipsize) - 
> 1;//0x1C;//ffs(nand_chip->chipsize) - 1;
> - nand_chip->oob_poi = nand_chip->buffers->databuf + mtd->writesize;
> + nand_chip->oob_poi = NULL;
>   nand_chip->badblockpos = 0;
>  
>   if (devinfo.pagesize == 4096)
>   
>   

> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] gdb: use separate patches for upstream and ARC gdb

2015-11-17 Thread Alexey Brodkin 
With bump of upstream GDB from 7.9 to 7.10 at least
100-no_extern_inline.patch became incompatible with
ARC gdb (which is still based on upstream 7.9 branch).

So until ARC support is not completely upstreamed
(which we expect to happen in coming months) we'll need to have
separate patches for ARC gdb.

This time clean build-tested for Netgear WNDRMAC & AXS101.

Signed-off-by: Alexey Brodkin 
Cc: Felix Fietkau 
Cc: John Crispin 
Cc: Jonas Gorski 
---
 toolchain/gdb/Makefile |  2 ++
 toolchain/gdb/patches/100-no_extern_inline.patch   | 32 --
 toolchain/gdb/patches/110-no_testsuite.patch   | 21 --
 .../patches/120-fix-compile-flag-mismatch.patch| 11 
 .../gdb/patches/7.10/100-no_extern_inline.patch| 32 ++
 toolchain/gdb/patches/7.10/110-no_testsuite.patch  | 21 ++
 .../7.10/120-fix-compile-flag-mismatch.patch   | 11 
 .../arc-2015.06-gdb/100-no_extern_inline.patch | 32 ++
 .../patches/arc-2015.06-gdb/110-no_testsuite.patch | 21 ++
 .../120-fix-compile-flag-mismatch.patch| 11 
 10 files changed, 130 insertions(+), 64 deletions(-)
 delete mode 100644 toolchain/gdb/patches/100-no_extern_inline.patch
 delete mode 100644 toolchain/gdb/patches/110-no_testsuite.patch
 delete mode 100644 toolchain/gdb/patches/120-fix-compile-flag-mismatch.patch
 create mode 100644 toolchain/gdb/patches/7.10/100-no_extern_inline.patch
 create mode 100644 toolchain/gdb/patches/7.10/110-no_testsuite.patch
 create mode 100644 
toolchain/gdb/patches/7.10/120-fix-compile-flag-mismatch.patch
 create mode 100644 
toolchain/gdb/patches/arc-2015.06-gdb/100-no_extern_inline.patch
 create mode 100644 toolchain/gdb/patches/arc-2015.06-gdb/110-no_testsuite.patch
 create mode 100644 
toolchain/gdb/patches/arc-2015.06-gdb/120-fix-compile-flag-mismatch.patch

diff --git a/toolchain/gdb/Makefile b/toolchain/gdb/Makefile
index 38ffb0b..f74b64e 100644
--- a/toolchain/gdb/Makefile
+++ b/toolchain/gdb/Makefile
@@ -24,6 +24,8 @@ PKG_MD5SUM:=2a35bac41fa8e10bf04f3a0dd7f7f363
 GDB_DIR:=$(PKG_NAME)-$(PKG_VERSION)
 endif
 
+PATCH_DIR:=./patches/$(PKG_VERSION)
+
 HOST_BUILD_DIR:=$(BUILD_DIR_TOOLCHAIN)/$(GDB_DIR)
 
 HOST_BUILD_PARALLEL:=1
diff --git a/toolchain/gdb/patches/100-no_extern_inline.patch 
b/toolchain/gdb/patches/100-no_extern_inline.patch
deleted file mode 100644
index 8c18c6e..000
--- a/toolchain/gdb/patches/100-no_extern_inline.patch
+++ /dev/null
@@ -1,32 +0,0 @@
 a/sim/common/sim-arange.c
-+++ b/sim/common/sim-arange.c
-@@ -280,11 +280,7 @@ sim_addr_range_delete (ADDR_RANGE *ar, a
-   build_search_tree (ar);
- }
- 
--#endif /* DEFINE_NON_INLINE_P */
--
--#if DEFINE_INLINE_P
--
--SIM_ARANGE_INLINE int
-+int
- sim_addr_range_hit_p (ADDR_RANGE *ar, address_word addr)
- {
-   ADDR_RANGE_TREE *t = ar->range_tree;
-@@ -301,4 +297,4 @@ sim_addr_range_hit_p (ADDR_RANGE *ar, ad
-   return 0;
- }
- 
--#endif /* DEFINE_INLINE_P */
-+#endif /* DEFINE_NON_INLINE_P */
 a/sim/common/sim-arange.h
-+++ b/sim/common/sim-arange.h
-@@ -73,7 +73,7 @@ extern void sim_addr_range_delete (ADDR_
- 
- /* Return non-zero if ADDR is in range AR, traversing the entire tree.
-If no range is specified, that is defined to mean "everything".  */
--SIM_ARANGE_INLINE int
-+extern int
- sim_addr_range_hit_p (ADDR_RANGE * /*ar*/, address_word /*addr*/);
- #define ADDR_RANGE_HIT_P(ar, addr) \
-   ((ar)->range_tree == NULL || sim_addr_range_hit_p ((ar), (addr)))
diff --git a/toolchain/gdb/patches/110-no_testsuite.patch 
b/toolchain/gdb/patches/110-no_testsuite.patch
deleted file mode 100644
index 1b284ea..000
--- a/toolchain/gdb/patches/110-no_testsuite.patch
+++ /dev/null
@@ -1,21 +0,0 @@
 a/gdb/configure
-+++ b/gdb/configure
-@@ -870,8 +870,7 @@ MAKEINFOFLAGS
- YACC
- YFLAGS
- XMKMF'
--ac_subdirs_all='testsuite
--gdbtk
-+ac_subdirs_all='gdbtk
- multi-ice
- gdbserver'
- 
-@@ -5610,7 +5610,7 @@ $as_echo "$with_auto_load_safe_path" >&6
- 
- 
- 
--subdirs="$subdirs testsuite"
-+subdirs="$subdirs"
- 
- 
- # Check whether to support alternative target configurations
diff --git a/toolchain/gdb/patches/120-fix-compile-flag-mismatch.patch 
b/toolchain/gdb/patches/120-fix-compile-flag-mismatch.patch
deleted file mode 100644
index c8b41f2..000
--- a/toolchain/gdb/patches/120-fix-compile-flag-mismatch.patch
+++ /dev/null
@@ -1,11 +0,0 @@
 a/gdb/gdbserver/configure
-+++ b/gdb/gdbserver/configure
-@@ -2468,7 +2468,7 @@ $as_echo "$as_me: error: \`$ac_var' was
-   ac_cache_corrupted=: ;;
- ,);;
- *)
--  if test "x$ac_old_val" != "x$ac_new_val"; then
-+  if test "`echo x$ac_old_val`" != "`echo x$ac_new_val`"; then
-   # differences in whitespace do not lead to failure.
-   ac_old_val_w=`echo x $ac_old_val`
-   ac_new_val_w=`echo x $ac_new_val`
diff --git

[OpenWrt-Devel] [PATCH v3 1/2] pinctrl/lantiq: introduce new dedicated tables

2015-11-17 Thread Martin Schiller 
This patch introduces new dedicated "pinctrl-ase", "pinctrl-danube",
"pinctrl-xrx100" and "pinctrl-xrx200" configuration tables.

Based on the newest Lantiq Hardware Description it turend out, that there are
some differences in the GPIO alternative functions of the Danube, xRX100 and
xRX200 families, which makes it impossible to use only one xway_mfp table.

This patch is also the first step to add support for the xRX300 family.

Signed-off-by: Martin Schiller 
---
 .../patches-3.18/0150-lantiq-pinctrl-xway.patch| 1118 +++-
 .../patches-4.1/0150-lantiq-pinctrl-xway.patch | 1118 +++-
 2 files changed, 2214 insertions(+), 22 deletions(-)

diff --git a/target/linux/lantiq/patches-3.18/0150-lantiq-pinctrl-xway.patch 
b/target/linux/lantiq/patches-3.18/0150-lantiq-pinctrl-xway.patch
index 84adbe6..871cebb 100644
--- a/target/linux/lantiq/patches-3.18/0150-lantiq-pinctrl-xway.patch
+++ b/target/linux/lantiq/patches-3.18/0150-lantiq-pinctrl-xway.patch
@@ -1,15 +1, @@
 --- a/drivers/pinctrl/pinctrl-xway.c
 +++ b/drivers/pinctrl/pinctrl-xway.c
-@@ -152,10 +152,10 @@ static const struct ltq_mfp_pin xway_mfp
-   MFP_XWAY(GPIO41, GPIO,  NONE,   NONE,   NONE),
-   MFP_XWAY(GPIO42, GPIO,  MDIO,   NONE,   NONE),
-   MFP_XWAY(GPIO43, GPIO,  MDIO,   NONE,   NONE),
--  MFP_XWAY(GPIO44, GPIO,  NONE,   GPHY,   SIN),
+@@ -7,6 +7,7 @@
+  *  publishhed by the Free Software Foundation.
+  *
+  *  Copyright (C) 2012 John Crispin 
++ *  Copyright (C) 2015 Martin Schiller 
+  */
+ 
+ #include 
+@@ -80,17 +81,18 @@
+ #define FUNC_MUX(f, m)\
+   { .func = f, .mux = XWAY_MUX_##m, }
+ 
+-#define XWAY_MAX_PIN  32
+-#define XR9_MAX_PIN   56
+-
+ enum xway_mux {
+   XWAY_MUX_GPIO = 0,
+   XWAY_MUX_SPI,
+   XWAY_MUX_ASC,
++  XWAY_MUX_USIF,
+   XWAY_MUX_PCI,
++  XWAY_MUX_CBUS,
+   XWAY_MUX_CGU,
+   XWAY_MUX_EBU,
++  XWAY_MUX_EBU2,
+   XWAY_MUX_JTAG,
++  XWAY_MUX_MCD,
+   XWAY_MUX_EXIN,
+   XWAY_MUX_TDM,
+   XWAY_MUX_STP,
+@@ -103,9 +105,15 @@ enum xway_mux {
+   XWAY_MUX_DFE,
+   XWAY_MUX_SDIO,
+   XWAY_MUX_GPHY,
++  XWAY_MUX_SSI,
+   XWAY_MUX_NONE = 0x,
+ };
+ 
++/* -  DEPRECATED: xway/xr9 related code - */
++/* -  use danube/xrx100/xrx200 instead  - */
++#define XWAY_MAX_PIN  32
++#define XR9_MAX_PIN   56
++
+ static const struct ltq_mfp_pin xway_mfp[] = {
+   /*   pinf0  f1  f2  f3   */
+   MFP_XWAY(GPIO0, GPIO,   EXIN,   NONE,   TDM),
+@@ -166,42 +174,6 @@ static const struct ltq_mfp_pin xway_mfp
+   MFP_XWAY(GPIO55, GPIO,  NONE,   NONE,   NONE),
+ };
+ 
+-static const struct ltq_mfp_pin ase_mfp[] = {
+-  /*   pinf0  f1  f2  f3   */
+-  MFP_XWAY(GPIO0, GPIO,   EXIN,   MII,TDM),
+-  MFP_XWAY(GPIO1, GPIO,   STP,DFE,EBU),
+-  MFP_XWAY(GPIO2, GPIO,   STP,DFE,EPHY),
+-  MFP_XWAY(GPIO3, GPIO,   STP,EPHY,   EBU),
+-  MFP_XWAY(GPIO4, GPIO,   GPT,EPHY,   MII),
+-  MFP_XWAY(GPIO5, GPIO,   MII,ASC,GPT),
+-  MFP_XWAY(GPIO6, GPIO,   MII,ASC,EXIN),
+-  MFP_XWAY(GPIO7, GPIO,   SPI,MII,JTAG),
+-  MFP_XWAY(GPIO8, GPIO,   SPI,MII,JTAG),
+-  MFP_XWAY(GPIO9, GPIO,   SPI,MII,JTAG),
+-  MFP_XWAY(GPIO10, GPIO,  SPI,MII,JTAG),
+-  MFP_XWAY(GPIO11, GPIO,  EBU,CGU,JTAG),
+-  MFP_XWAY(GPIO12, GPIO,  EBU,MII,SDIO),
+-  MFP_XWAY(GPIO13, GPIO,  EBU,MII,CGU),
+-  MFP_XWAY(GPIO14, GPIO,  EBU,SPI,CGU),
+-  MFP_XWAY(GPIO15, GPIO,  EBU,SPI,SDIO),
+-  MFP_XWAY(GPIO16, GPIO,  NONE,   NONE,   NONE),
+-  MFP_XWAY(GPIO17, GPIO,  NONE,   NONE,   NONE),
+-  MFP_XWAY(GPIO18, GPIO,  NONE,   NONE,   NONE),
+-  MFP_XWAY(GPIO19, GPIO,  EBU,MII,SDIO),
+-  MFP_XWAY(GPIO20, GPIO,  EBU,MII,SDIO),
+-  MFP_XWAY(GPIO21, GPIO,  EBU,MII,SDIO),
+-  MFP_XWAY(GPIO22, GPIO,  EBU,MII,CGU),
+-  MFP_XWAY(GPIO23, GPIO,  EBU,MII,CGU),
+-  MFP_XWAY(GPIO24, GPIO,  EBU,NONE,   MII),
+-  MFP_XWAY(GPIO25, GPIO,  EBU,MII,GPT),
+-  MFP_XWAY(GPIO26, GPIO,  EBU,MII,SDIO),
+-  MFP_XWAY(GPIO27, GPIO,  EBU,NONE,   MII),
+-  MFP_XWAY(GPIO28, GPIO,  MII,EBU,SDIO),
+-  MFP_XWAY(GPIO29, GPIO,  EBU,MII,EXIN),
+-  MFP_XWAY(GPIO30, GPIO,  NONE,   NONE,   NONE),
+-  MFP_XWAY(GPIO31, GPIO,  NONE,   NONE,   NONE),
+-};
+-
+ static const unsigned pins_jtag[] = {GPIO15, GPIO16, GPIO17, GPIO19, GPIO35};
+ static const unsigned pins_asc0[] = {GPIO11, GPIO12};
+ static const unsigned pins_asc0_cts_rts[] = {GPIO9, GPIO10};
+@@ -231,6 +203,8 @@ static const unsigned pins_nand_cle[] =
+ static const unsigned pins_nand_rdy[] = {GPIO48};
+ static const unsigned pins_nand_rd[] =

Re: [OpenWrt-Devel] [PATCH v3 1/2] pinctrl/lantiq: introduce new dedicated tables

2015-11-17 Thread John Crispin 


On 17/11/2015 16:06, Daniel Schwierzeck wrote:
> 2015-11-17 13:48 GMT+01:00 Martin Schiller :
>> This patch introduces new dedicated "pinctrl-ase", "pinctrl-danube",
>> "pinctrl-xrx100" and "pinctrl-xrx200" configuration tables.
>>
>> Based on the newest Lantiq Hardware Description it turend out, that there are
>> some differences in the GPIO alternative functions of the Danube, xRX100 and
>> xRX200 families, which makes it impossible to use only one xway_mfp table.
>>
>> This patch is also the first step to add support for the xRX300 family.
>>
>> Signed-off-by: Martin Schiller 
>> ---
>>  .../patches-3.18/0150-lantiq-pinctrl-xway.patch| 1118 
>> +++-
>>  .../patches-4.1/0150-lantiq-pinctrl-xway.patch | 1118 
>> +++-
>>  2 files changed, 2214 insertions(+), 22 deletions(-)
>>
> 
>> ++
>> ++static const unsigned xrx200_pins_usif_spi[] = {GPIO11, GPIO12, GPIO38};
>> ++static const unsigned xrx200_pins_usif_spi_cs0[] = {GPIO37};
>> ++static const unsigned xrx200_pins_usif_spi_cs1[] = {GPIO39};
>> ++static const unsigned xrx200_pins_usif_spi_cs2[] = {GPIO14};
>> ++
> 
>> ++
>> ++static const unsigned xrx200_pins_spi[] = {GPIO16, GPIO17, GPIO18};
>> ++static const unsigned xrx200_pins_spi_cs1[] = {GPIO15};
>> ++static const unsigned xrx200_pins_spi_cs2[] = {GPIO22};
>> ++static const unsigned xrx200_pins_spi_cs3[] = {GPIO13};
>> ++static const unsigned xrx200_pins_spi_cs4[] = {GPIO10};
>> ++static const unsigned xrx200_pins_spi_cs5[] = {GPIO9};
>> ++static const unsigned xrx200_pins_spi_cs6[] = {GPIO11};
>> ++
> 
> while you are at it, could you also add dedicated controls for the SPI
> and USIF-SPI pins for all SoC's like:
> 
> static const unsigned xrx200_pins_usif_spi_di[] = {GPIO11};
> static const unsigned xrx200_pins_usif_spi_do[] = {GPIO12};
> static const unsigned xrx200_pins_usif_spi_clk[] = {GPIO38};
> 
> static const unsigned xrx200_pins_spi_di[] = {GPIO16};
> static const unsigned xrx200_pins_spi_do[] = {GPIO17};
> static const unsigned xrx200_pins_spi_clk[] = {GPIO18};
> 
> I have SPI and USIF-SPI drivers which are mostly ready for upstream
> submission and their DT bindings depend on dedicated pin controls.
> 
> Thanks,
> Daniel

there are also some fixes for mux functions inside ugw6.1.1. you might
want to look at those and merge them.

John


> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v3 1/2] pinctrl/lantiq: introduce new dedicated tables

2015-11-17 Thread Daniel Schwierzeck 
2015-11-17 13:48 GMT+01:00 Martin Schiller :
> This patch introduces new dedicated "pinctrl-ase", "pinctrl-danube",
> "pinctrl-xrx100" and "pinctrl-xrx200" configuration tables.
>
> Based on the newest Lantiq Hardware Description it turend out, that there are
> some differences in the GPIO alternative functions of the Danube, xRX100 and
> xRX200 families, which makes it impossible to use only one xway_mfp table.
>
> This patch is also the first step to add support for the xRX300 family.
>
> Signed-off-by: Martin Schiller 
> ---
>  .../patches-3.18/0150-lantiq-pinctrl-xway.patch| 1118 
> +++-
>  .../patches-4.1/0150-lantiq-pinctrl-xway.patch | 1118 
> +++-
>  2 files changed, 2214 insertions(+), 22 deletions(-)
>

> ++
> ++static const unsigned xrx200_pins_usif_spi[] = {GPIO11, GPIO12, GPIO38};
> ++static const unsigned xrx200_pins_usif_spi_cs0[] = {GPIO37};
> ++static const unsigned xrx200_pins_usif_spi_cs1[] = {GPIO39};
> ++static const unsigned xrx200_pins_usif_spi_cs2[] = {GPIO14};
> ++

> ++
> ++static const unsigned xrx200_pins_spi[] = {GPIO16, GPIO17, GPIO18};
> ++static const unsigned xrx200_pins_spi_cs1[] = {GPIO15};
> ++static const unsigned xrx200_pins_spi_cs2[] = {GPIO22};
> ++static const unsigned xrx200_pins_spi_cs3[] = {GPIO13};
> ++static const unsigned xrx200_pins_spi_cs4[] = {GPIO10};
> ++static const unsigned xrx200_pins_spi_cs5[] = {GPIO9};
> ++static const unsigned xrx200_pins_spi_cs6[] = {GPIO11};
> ++

while you are at it, could you also add dedicated controls for the SPI
and USIF-SPI pins for all SoC's like:

static const unsigned xrx200_pins_usif_spi_di[] = {GPIO11};
static const unsigned xrx200_pins_usif_spi_do[] = {GPIO12};
static const unsigned xrx200_pins_usif_spi_clk[] = {GPIO38};

static const unsigned xrx200_pins_spi_di[] = {GPIO16};
static const unsigned xrx200_pins_spi_do[] = {GPIO17};
static const unsigned xrx200_pins_spi_clk[] = {GPIO18};

I have SPI and USIF-SPI drivers which are mostly ready for upstream
submission and their DT bindings depend on dedicated pin controls.

Thanks,
Daniel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] kernel: mtd: Backport GD25Q128B support to 3.18

2015-11-17 Thread Srdjan Rosic 
Support is present in 3.19 and above as kernel commit:
fcc87a95195236b0935183361a72e4a98bf577d8

Changes to other existing patches are a result of "make target/linux/refresh".

Signed-off-by: Srdjan Rosic 
Signed-off-by: Srdjan Rosic 
---
 .../043-mtd_GD25Q128B_support_backport_from_3.19.patch| 15 +++
 .../091-mtd-spi-nor-add-support-Spansion_S25FL164K|  2 +-
 ...-mtd-m25p80-add-support-for-Winbond-W25X05-flash.patch |  2 +-
 ...spi-nor-add-support-for-the-Macronix-MX25L512E-S.patch |  2 +-
 ...spi-nor-add-support-for-the-ISSI-SI25CD512-SPI-f.patch |  2 +-
 5 files changed, 19 insertions(+), 4 deletions(-)
 create mode 100644 
target/linux/generic/patches-3.18/043-mtd_GD25Q128B_support_backport_from_3.19.patch

diff --git 
a/target/linux/generic/patches-3.18/043-mtd_GD25Q128B_support_backport_from_3.19.patch
 
b/target/linux/generic/patches-3.18/043-mtd_GD25Q128B_support_backport_from_3.19.patch
new file mode 100644
index 000..b7bae34
--- /dev/null
+++ 
b/target/linux/generic/patches-3.18/043-mtd_GD25Q128B_support_backport_from_3.19.patch
@@ -0,0 +1,15 @@
+mtd: spi-nor: support for (GigaDevice) GD25Q128B
+
+Signed-off-by: Rafał Miłecki 
+Signed-off-by: Brian Norris 
+
+--- a/drivers/mtd/spi-nor/spi-nor.c
 b/drivers/mtd/spi-nor/spi-nor.c
+@@ -510,6 +510,7 @@ static const struct spi_device_id spi_no
+   /* GigaDevice */
+   { "gd25q32", INFO(0xc84016, 0, 64 * 1024,  64, SECT_4K) },
+   { "gd25q64", INFO(0xc84017, 0, 64 * 1024, 128, SECT_4K) },
++  { "gd25q128", INFO(0xc84018, 0, 64 * 1024, 256, SECT_4K) },
+ 
+   /* Intel/Numonyx -- xxxs33b */
+   { "160s33b",  INFO(0x898911, 0, 64 * 1024,  32, 0) },
diff --git 
a/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-Spansion_S25FL164K
 
b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-Spansion_S25FL164K
index d9831f4..24aa075 100644
--- 
a/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-Spansion_S25FL164K
+++ 
b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-Spansion_S25FL164K
@@ -1,6 +1,6 @@
 --- a/drivers/mtd/spi-nor/spi-nor.c
 +++ b/drivers/mtd/spi-nor/spi-nor.c
-@@ -566,6 +566,7 @@ static const struct spi_device_id spi_no
+@@ -567,6 +567,7 @@ static const struct spi_device_id spi_no
{ "s25fl008k",  INFO(0xef4014,  0,  64 * 1024,  16, SECT_4K) },
{ "s25fl016k",  INFO(0xef4015,  0,  64 * 1024,  32, SECT_4K) },
{ "s25fl064k",  INFO(0xef4017,  0,  64 * 1024, 128, SECT_4K) },
diff --git 
a/target/linux/generic/patches-3.18/472-mtd-m25p80-add-support-for-Winbond-W25X05-flash.patch
 
b/target/linux/generic/patches-3.18/472-mtd-m25p80-add-support-for-Winbond-W25X05-flash.patch
index dca6895..f059aa7 100644
--- 
a/target/linux/generic/patches-3.18/472-mtd-m25p80-add-support-for-Winbond-W25X05-flash.patch
+++ 
b/target/linux/generic/patches-3.18/472-mtd-m25p80-add-support-for-Winbond-W25X05-flash.patch
@@ -10,7 +10,7 @@ Signed-off-by: Gabor Juhos 
 
 --- a/drivers/mtd/spi-nor/spi-nor.c
 +++ b/drivers/mtd/spi-nor/spi-nor.c
-@@ -617,6 +617,7 @@ static const struct spi_device_id spi_no
+@@ -618,6 +618,7 @@ static const struct spi_device_id spi_no
{ "m25px80",INFO(0x207114,  0, 64 * 1024, 16, 0) },
  
/* Winbond -- w25x "blocks" are 64K, "sectors" are 4KiB */
diff --git 
a/target/linux/generic/patches-3.18/473-mtd-spi-nor-add-support-for-the-Macronix-MX25L512E-S.patch
 
b/target/linux/generic/patches-3.18/473-mtd-spi-nor-add-support-for-the-Macronix-MX25L512E-S.patch
index 8082fa6..9ba7a4a 100644
--- 
a/target/linux/generic/patches-3.18/473-mtd-spi-nor-add-support-for-the-Macronix-MX25L512E-S.patch
+++ 
b/target/linux/generic/patches-3.18/473-mtd-spi-nor-add-support-for-the-Macronix-MX25L512E-S.patch
@@ -11,7 +11,7 @@ Signed-off-by: Gabor Juhos 
 
 --- a/drivers/mtd/spi-nor/spi-nor.c
 +++ b/drivers/mtd/spi-nor/spi-nor.c
-@@ -517,6 +517,7 @@ static const struct spi_device_id spi_no
+@@ -518,6 +518,7 @@ static const struct spi_device_id spi_no
{ "640s33b",  INFO(0x898913, 0, 64 * 1024, 128, 0) },
  
/* Macronix */
diff --git 
a/target/linux/generic/patches-3.18/474-mtd-spi-nor-add-support-for-the-ISSI-SI25CD512-SPI-f.patch
 
b/target/linux/generic/patches-3.18/474-mtd-spi-nor-add-support-for-the-ISSI-SI25CD512-SPI-f.patch
index f572237..b06ac73 100644
--- 
a/target/linux/generic/patches-3.18/474-mtd-spi-nor-add-support-for-the-ISSI-SI25CD512-SPI-f.patch
+++ 
b/target/linux/generic/patches-3.18/474-mtd-spi-nor-add-support-for-the-ISSI-SI25CD512-SPI-f.patch
@@ -10,7 +10,7 @@ Signed-off-by: Gabor Juhos 
 
 --- a/drivers/mtd/spi-nor/spi-nor.c
 +++ b/drivers/mtd/spi-nor/spi-nor.c
-@@ -516,6 +516,9 @@ static const struct spi_device_id spi_no
+@@ -517,6 +517,9 @@ static const struct spi_device_id spi_no
{ "320s33b",  INFO(0x898912, 0, 64 *

[OpenWrt-Devel] [PATCH] netifd: Request DHCP option 121 (classless route) by default

2015-11-17 Thread Baptiste Jonglez 
From: Baptiste Jonglez 

This option is very useful when the gateway configured by DHCP cannot
be in the same subnet as the client.  This happens, for instance, when
using DHCP to hand out addresses in /32 subnets.

Signed-off-by: Baptiste Jonglez 
---
 package/network/config/netifd/files/lib/netifd/proto/dhcp.sh | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh 
b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh
index 0e88af9..1eb8010 100755
--- a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh
+++ b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh
@@ -38,6 +38,8 @@ proto_dhcp_setup() {
append dhcpopts "-x $opt"
done
 
+   # Classless route option, see RFC 3442
+   append dhcpopts "-O 121"
[ "$broadcast" = 1 ] && broadcast="-B" || broadcast=
[ -n "$clientid" ] && clientid="-x 0x3d:${clientid//:/}" || 
clientid="-C"
[ -n "$iface6rd" ] && proto_export "IFACE6RD=$iface6rd"
-- 
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] [001/001] TL-WR710N: create image for v2.1

2015-11-17 Thread Norbert Wegener 
This patch just extends target/linux/ar71xx/image/Makefile to build
images also for version 2.1 of TL-WR710N

diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index 013a215..da2e7d4 100644
--- a/target/linux/ar71xx/image/Makefile
+++ b/target/linux/ar71xx/image/Makefile
@@ -476,6 +476,15 @@ define Device/tl-wr710n-v2
 CONSOLE := ttyATH0,115200
 endef
 
+define Device/tl-wr710n-v2.1
+$(Device/tplink-8mlzma)
+BOARDNAME := TL-WR710N
+DEVICE_PROFILE := TLWR710
+TPLINK_HWID := 0x0712
+TPLINK_HWREV := 0x0002
+CONSOLE := ttyATH0,115200
+endef
+
 define Device/tl-wr720n-v3
 $(Device/tplink-4mlzma)
 BOARDNAME := TL-WR720N-v3
@@ -491,7 +500,7 @@ define Device/tl-wr720n-v4
 TPLINK_HWID := 0x07200104
 CONSOLE := ttyATH0,115200
 endef
-TARGET_DEVICES += tl-wr703n-v1 tl-wr710n-v1 tl-wr710n-v2 tl-wr720n-v3
tl-wr720n-v4
+TARGET_DEVICES += tl-wr703n-v1 tl-wr710n-v1 tl-wr710n-v2 tl-wr710n-v2.1
tl-wr720n-v3 tl-wr720n-v4
 
 define Device/tl-wr74:0n-v4
 $(Device/tplink-4mlzma)

Signed off by: Norbert Wegener 



0xC544527E.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] mac80211: Add dependency on ip (iproute2) to cfg80211

2015-11-17 Thread Cristian Morales Vega 
On 16 November 2015 at 23:40, Felix Fietkau  wrote:
> On 2015-11-16 20:28, Ted Hess wrote:
>> Changes to netifd/wireless/mac80211.sh in r46832 invoke 'ip' when making
>> a client association. 'ip' is not automatically included with cfg80211
>> custom builds -- association fails.
>>
>> Signed-off-by: Ted Hess 
> NACK. These changes were added because the busybox ip applet was enabled
> by default recently.

So there is a dependency (ip package OR ip support in Busybox), but no
way to express it?

Not that it would make sense for anybody to disable the new default in
busybox without enabling the ip package at the same time. Just
curious.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel