date:20171015

Re: [LEDE-DEV] [PATCH 0/4] ar71xx: add support for kernel 4.9

2017-10-15 Thread Sven Schönhoff

Hi Hauke,

I've tested a TP-Link TL-WR1043ND v2 and a TP-Link Archer C7 in the
meantime and everything works too. I couldn't notice any performance
regessions on these devices with my 200mbit internet connection but
they have a better hardware than the 1043ND v1.


Best regards
Sven

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

Re: [LEDE-DEV] test omap target with kernel 4.9

2017-10-15 Thread Lucian Cristian


On 16.10.2017 03:30, Alexander Couzens wrote:

Hi Hauke,

I've tested your tree.

panda-board a3 - works, but no network, but master/4.4 doesn't have network 
either.
panda-board-a4 - u-boot SPL refuse to boot.
beaglebone-black - works

beagle-board - usb attached network doesn't come up and I doesn't have a serial 
around.
beagle-board-xm - ToDo: image code is missing.

However, I like to merge it. I'll fix the problems later.

Acked-by: Alexander Couzens 

Best,
lynxis


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


does ubisf/squashfs image works on your beaglebone-black  ? it didn't 
work for me on 4.4 either


Regards

Lucian

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

Re: [LEDE-DEV] test omap target with kernel 4.9

2017-10-15 Thread Alexander Couzens

Hi Hauke,

I've tested your tree.

panda-board a3 - works, but no network, but master/4.4 doesn't have network 
either.
panda-board-a4 - u-boot SPL refuse to boot.
beaglebone-black - works

beagle-board - usb attached network doesn't come up and I doesn't have a serial 
around.
beagle-board-xm - ToDo: image code is missing.

However, I like to merge it. I'll fix the problems later.

Acked-by: Alexander Couzens 

Best,
lynxis
-- 
Alexander Couzens

mail: lyn...@fe80.eu
jabber: lyn...@fe80.eu
mobile: +4915123277221
gpg: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF 8604


pgpCMEuXvIqJS.pgp
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH 2/2] ixp4xx: drop the jumbo frame support

2017-10-15 Thread Sergey Ryazanov

Current jumbo frame support code allocates rxbuffers of the maximum size
supported by the hardware (~14KB). This happens at the device open time
even if the configured MTU is lower (e.g. if it configured to standard
1500 bytes). Such behavior effectivly prevents interface start on boards
with a low ammount of RAM (e.g. WRT300N v2), since the kernel simly can
not allocates of ~0.8MB (14KB x 64).

So remove jumbo frame support for now.

Reported-by: Nerijus Baliunas 
Tested-by: Nerijus Baliunas 
Signed-off-by: Sergey Ryazanov 
---
 .../patches-4.4/304-ixp4xx_eth_jumboframe.patch| 80 --
 1 file changed, 80 deletions(-)
 delete mode 100644 
target/linux/ixp4xx/patches-4.4/304-ixp4xx_eth_jumboframe.patch

diff --git a/target/linux/ixp4xx/patches-4.4/304-ixp4xx_eth_jumboframe.patch 
b/target/linux/ixp4xx/patches-4.4/304-ixp4xx_eth_jumboframe.patch
deleted file mode 100644
index b16086bbc4..00
--- a/target/linux/ixp4xx/patches-4.4/304-ixp4xx_eth_jumboframe.patch
+++ /dev/null
@@ -1,80 +0,0 @@
 a/drivers/net/ethernet/xscale/ixp4xx_eth.c
-+++ b/drivers/net/ethernet/xscale/ixp4xx_eth.c
-@@ -57,7 +57,7 @@
- 
- #define POOL_ALLOC_SIZE   (sizeof(struct desc) * (RX_DESCS + 
TX_DESCS))
- #define REGS_SIZE 0x1000
--#define MAX_MRU   1536 /* 0x600 */
-+#define MAX_MRU   (14320 - ETH_HLEN - ETH_FCS_LEN)
- #define RX_BUFF_SIZE  ALIGN((NET_IP_ALIGN) + MAX_MRU, 4)
- 
- #define NAPI_WEIGHT   16
-@@ -1315,6 +1315,32 @@ static void destroy_queues(struct port *
-   }
- }
- 
-+static int eth_do_change_mtu(struct net_device *dev, int mtu)
-+{
-+  struct port *port;
-+  struct msg msg;
-+  /* adjust for ethernet headers */
-+  int framesize = mtu + ETH_HLEN + ETH_FCS_LEN;
-+
-+  port = netdev_priv(dev);
-+
-+  memset(, 0, sizeof(msg));
-+  msg.cmd = NPE_SETMAXFRAMELENGTHS;
-+  msg.eth_id = port->id;
-+
-+  /* max rx/tx 64 byte blocks */
-+  msg.byte2 = ((framesize + 63) / 64) << 8;
-+  msg.byte3 = ((framesize + 63) / 64) << 8;
-+
-+  msg.byte4 = msg.byte6 = framesize >> 8;
-+  msg.byte5 = msg.byte7 = framesize & 0xff;
-+
-+  if (npe_send_recv_message(port->npe, , "ETH_SET_MAX_FRAME_LENGTH"))
-+  return -EIO;
-+
-+  return 0;
-+}
-+
- static int eth_open(struct net_device *dev)
- {
-   struct port *port = netdev_priv(dev);
-@@ -1366,6 +1392,8 @@ static int eth_open(struct net_device *d
-   if (npe_send_recv_message(port->npe, , "ETH_SET_FIREWALL_MODE"))
-   return -EIO;
- 
-+  eth_do_change_mtu(dev, dev->mtu);
-+
-   if ((err = request_queues(port)) != 0)
-   return err;
- 
-@@ -1505,7 +1533,26 @@ static int eth_close(struct net_device *
-   return 0;
- }
- 
-+static int ixp_eth_change_mtu(struct net_device *dev, int mtu)
-+{
-+  int ret;
-+
-+  if (mtu > MAX_MRU)
-+  return -EINVAL;
-+
-+  if (dev->flags & IFF_UP) {
-+  ret = eth_do_change_mtu(dev, mtu);
-+  if (ret < 0)
-+  return ret;
-+  }
-+
-+  dev->mtu = mtu;
-+
-+  return 0;
-+}
-+
- static const struct net_device_ops ixp4xx_netdev_ops = {
-+  .ndo_change_mtu = ixp_eth_change_mtu,
-   .ndo_open = eth_open,
-   .ndo_stop = eth_close,
-   .ndo_start_xmit = eth_xmit,
-- 
2.13.6


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

[LEDE-DEV] [PATCH 0/2] ixp4xx: ethernet fixes (WRT300N v2)

2017-10-15 Thread Sergey Ryazanov

This series contains a couple of fixes for issues with the IXP4xx
ethernet driver, which were spotted in the [1].

This issues affect at least WRT300N v2 board support, but should be
useful for other boards too.

1. https://lists.openwrt.org/pipermail/openwrt-devel/2017-July/043131.html

Sergey Ryazanov (2):
  ixp4xx: fix non-standard phy support
  ixp4xx: drop the jumbo frame support

 .../207-npe_driver_multiphy_support.patch  | 28 +++-
 .../patches-4.4/304-ixp4xx_eth_jumboframe.patch| 80 --
 2 files changed, 25 insertions(+), 83 deletions(-)
 delete mode 100644 
target/linux/ixp4xx/patches-4.4/304-ixp4xx_eth_jumboframe.patch

-- 
2.13.6


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

[LEDE-DEV] [PATCH 1/2] ixp4xx: fix non-standard phy support

2017-10-15 Thread Sergey Ryazanov

The patch, which adds multiphy support, adds new path for non-standard
PHYs (e.g. MV88E6060 switch IC) to avoid using kernel phy framework. All
work well except the link status traking (Duplex and Speed), which is
reseted as soon as PHY connection procedure is done. This leads to lost
of the link status of non-standard PHY, which is configured exactly in
the ixp4xx_phy_connect() function.

Move the generic reset of a link state to the ixp4xx_phy_connect()
function to the code path, which is intended for handling of a normal
PHY.

Reported-by: Nerijus Baliunas 
Tested-by: Nerijus Baliunas 
Signed-off-by: Sergey Ryazanov 
---
 .../207-npe_driver_multiphy_support.patch  | 28 +++---
 1 file changed, 25 insertions(+), 3 deletions(-)

diff --git 
a/target/linux/ixp4xx/patches-4.4/207-npe_driver_multiphy_support.patch 
b/target/linux/ixp4xx/patches-4.4/207-npe_driver_multiphy_support.patch
index 207ccc533a..33c3327ee9 100644
--- a/target/linux/ixp4xx/patches-4.4/207-npe_driver_multiphy_support.patch
+++ b/target/linux/ixp4xx/patches-4.4/207-npe_driver_multiphy_support.patch
@@ -66,7 +66,18 @@ TODO: take care of additional PHYs through the PHY 
abstraction layer
snprintf(phy_id, MII_BUS_ID_SIZE + 3, PHY_ID_FMT,
mdio_bus->id, plat->phy);
port->phydev = phy_connect(dev, phy_id, _adjust_link,
-@@ -632,21 +663,32 @@ static void ixp4xx_phy_disconnect(struct
+@@ -625,6 +656,10 @@ static int ixp4xx_phy_connect(struct net
+ 
+   port->phydev->irq = PHY_POLL;
+ 
++  port->link = 0;
++  port->speed = 0;
++  port->duplex = -1;
++
+   return 0;
+ }
+ 
+@@ -632,21 +667,32 @@ static void ixp4xx_phy_disconnect(struct
  {
struct port *port = netdev_priv(dev);
  
@@ -102,7 +113,7 @@ TODO: take care of additional PHYs through the PHY 
abstraction layer
  }
  
  static inline void debug_pkt(struct net_device *dev, const char *func,
-@@ -1048,6 +1090,9 @@ static int eth_ioctl(struct net_device *
+@@ -1048,6 +1094,9 @@ static int eth_ioctl(struct net_device *
return hwtstamp_get(dev, req);
}
  
@@ -112,7 +123,7 @@ TODO: take care of additional PHYs through the PHY 
abstraction layer
return phy_mii_ioctl(port->phydev, req, cmd);
  }
  
-@@ -1068,18 +1113,30 @@ static void ixp4xx_get_drvinfo(struct ne
+@@ -1068,18 +1117,30 @@ static void ixp4xx_get_drvinfo(struct ne
  static int ixp4xx_get_settings(struct net_device *dev, struct ethtool_cmd 
*cmd)
  {
struct port *port = netdev_priv(dev);
@@ -143,3 +154,14 @@ TODO: take care of additional PHYs through the PHY 
abstraction layer
return phy_start_aneg(port->phydev);
  }
  
+@@ -1529,10 +1590,6 @@ static int eth_init_one(struct platform_
+   if ((err = register_netdev(dev)))
+   goto err_phy_dis;
+ 
+-  port->link = 0;
+-  port->speed = 0;
+-  port->duplex = -1;
+-
+   printk(KERN_INFO "%s: MII PHY %i on %s\n", dev->name, plat->phy,
+  npe_name(port->npe));
+ 
-- 
2.13.6


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

[LEDE-DEV] [RFC] at91: fix build of legacy target

2017-10-15 Thread Hauke Mehrtens

Changing the order of the devices fixes the build problem seen by the
build bot. I do not understand why this is making any difference at all,
this is probably only hiding a different bug.

Signed-off-by: Hauke Mehrtens 
---

Without this patch I am getting the following error message:

cat 
/home/hauke/openwrt/lede/build_dir/target-arm_arm926ej-s_musl_eabi/linux-at91_legacy/tmp/lede-at91-legacy-tny_a9260-squashfs-factory.bin.dtb
 >> 
/home/hauke/openwrt/lede/build_dir/target-arm_arm926ej-s_musl_eabi/linux-at91_legacy/tmp/lede-at91-legacy-tny_a9260-squashfs-factory.bin
dd 
if=/home/hauke/openwrt/lede/build_dir/target-arm_arm926ej-s_musl_eabi/linux-at91_legacy/tmp/lede-at91-legacy-tny_a9260-squashfs-factory.bin
 
of=/home/hauke/openwrt/lede/build_dir/target-arm_arm926ej-s_musl_eabi/linux-at91_legacy/tmp/lede-at91-legacy-tny_a9260-squashfs-factory.bin.new
 bs= conv=sync
dd: invalid number: ''
Makefile:74: recipe for target 
'/home/hauke/openwrt/lede/build_dir/target-arm_arm926ej-s_musl_eabi/linux-at91_legacy/tmp/lede-at91-legacy-tny_a9260-squashfs-factory.bin'
 failed
make[5]: *** 
[/home/hauke/openwrt/lede/build_dir/target-arm_arm926ej-s_musl_eabi/linux-at91_legacy/tmp/lede-at91-legacy-tny_a9260-squashfs-factory.bin]
 Error 1
make[5]: Leaving directory '/home/hauke/openwrt/lede/target/linux/at91/image'
Makefile:24: recipe for target 'install' failed


I am using this configuration:
$ ./scripts/diffconfig.sh 
CONFIG_TARGET_at91=y
CONFIG_TARGET_at91_legacy=y
CONFIG_TARGET_at91_legacy_DEVICE_tny_a9260=y

The build bots are also splotting this problem.


 target/linux/at91/image/legacy.mk | 13 ++---
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/target/linux/at91/image/legacy.mk 
b/target/linux/at91/image/legacy.mk
index c6d9ed8108..7a8b4abef1 100644
--- a/target/linux/at91/image/legacy.mk
+++ b/target/linux/at91/image/legacy.mk
@@ -110,13 +110,6 @@ define Device/ethernut5
 endef
 TARGET_DEVICES += ethernut5
 
-define Device/at91-q5xr5
-  $(Device/production-dtb)
-  DEVICE_TITLE := Exegin Q5XR5
-  KERNEL_SIZE := 2048k
-endef
-TARGET_DEVICES += at91-q5xr5
-
 define Device/wb45n
   $(Device/evaluation-fit)
   DEVICE_TITLE := Laird WB45N
@@ -131,3 +124,9 @@ define Device/wb45n
 endef
 TARGET_DEVICES += wb45n
 
+define Device/at91-q5xr5
+  $(Device/production-dtb)
+  DEVICE_TITLE := Exegin Q5XR5
+  KERNEL_SIZE := 2048k
+endef
+TARGET_DEVICES += at91-q5xr5
-- 
2.11.0


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

Re: [LEDE-DEV] [PATCH] kernel: enable CONFIG_ADVISE_SYSCALLS

2017-10-15 Thread rosenp

I don't see a change. I still get 6479872 for vmlinux.

On Sat, 2017-10-14 at 18:05 -0700, Florian Fainelli wrote:
> Le 10/14/17 à 17:07, Rosen Penev a écrit :
> > Without this, posix_[fm]advise does not work. This causes issues
> > with btrfs-progs, which uses fadvise to drop caches.
> 
> What's the kernel image size difference w/ and w/o this option? Would
> it
> make sense to expose it under config/Config-kernel.in for instance?
> 
> > 
> > Signed-off-by: Rosen Penev 
> > ---
> >  target/linux/generic/config-4.9 | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/target/linux/generic/config-4.9
> > b/target/linux/generic/config-4.9
> > index 8654357dbf..570efabc7a 100644
> > --- a/target/linux/generic/config-4.9
> > +++ b/target/linux/generic/config-4.9
> > @@ -90,7 +90,7 @@ CONFIG_32BIT=y
> >  # CONFIG_ADM6996_PHY is not set
> >  # CONFIG_ADM8211 is not set
> >  # CONFIG_ADT7316 is not set
> > -# CONFIG_ADVISE_SYSCALLS is not set
> > +CONFIG_ADVISE_SYSCALLS=y
> >  # CONFIG_ADXRS450 is not set
> >  CONFIG_AEABI=y
> >  # CONFIG_AFE4403 is not set
> > 
> 
> 

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

[LEDE-DEV] ar71xx use kernel 4.9 by default

2017-10-15 Thread Hauke Mehrtens

Hi,

I added support for kernel 4.9 to the ar71xx target some days ago and it
was tested by multiple people.

The only regression in kernel 4.9 compared to 4.4, I am aware of was
this performance regression reported by Sven Schönhoff:
http://lists.infradead.org/pipermail/lede-dev/2017-October/009251.html
I haven't found the time to investigate this problem, it would be nice
if some one could look into this.

If there are no other complains I would like to switch the default
kernel of the ar71xx target to 4.9 next weekend, are there any
objections to this plan?

Hauke

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

Re: [LEDE-DEV] [PATCH v2] ath10k-ct driver: use dma_alloc_coherent, 4.13 based driver

2017-10-15 Thread Hauke Mehrtens

On 10/12/2017 11:52 PM, Ben Greear wrote:
> On 10/12/2017 01:46 PM, Hauke Mehrtens wrote:
> 
>> I fixed this by backporting this commit from kernel 4.14:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0cc00f250e19c717fc9cdbdb7f55aaa569c7498
>>
> 
> Thanks for testing and for the fix.  I'll pull this into my 4.13 driver
> when I'm
> back from vacation...that way you can drop the external patch when I
> update LEDE with
> latest again...

Thank you for taking the patch into your main repository, so we can get
rid of it with the next upgrade of ath10k-ct.

Hauke

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

Re: [LEDE-DEV] [PATCH] ath10k-firmware: update QCA9888 and QCA4019 firmware

2017-10-15 Thread Hauke Mehrtens

On 10/14/2017 05:35 PM, Christian Lamparter wrote:
> On Saturday, October 14, 2017 11:24:24 AM CEST Hauke Mehrtens wrote:
>> This updates the firmware files for the QCA9888 and QCA4019
>> chips to a more recent version which is also used in the linux-firmware
>> repository.
>>
>> Signed-off-by: Hauke Mehrtens 
>> ---
>>
>> Could someone with a QCA4019 or QCA9888 device please test this.
>> I do not have these deceives to test this myself.
>>
>>  package/firmware/ath10k-firmware/Makefile | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/package/firmware/ath10k-firmware/Makefile 
>> b/package/firmware/ath10k-firmware/Makefile
>> index 84889d9d29..5e0f41ea52 100644
>> --- a/package/firmware/ath10k-firmware/Makefile
>> +++ b/package/firmware/ath10k-firmware/Makefile
>> @@ -223,7 +223,7 @@ define Package/ath10k-firmware-qca4019/install
>>  $(PKG_BUILD_DIR)/QCA4019/hw1.0/board-2.bin \
>>  $(1)/lib/firmware/ath10k/QCA4019/hw1.0/
>>  $(INSTALL_DATA) \
>> -
>> $(PKG_BUILD_DIR)/QCA4019/hw1.0/3.2.1/firmware-5.bin_10.4-3.2.1-00053 \
>> +
>> $(PKG_BUILD_DIR)/QCA4019/hw1.0/3.4/firmware-5.bin_10.4-3.4-00082 \
>>  $(1)/lib/firmware/ath10k/QCA4019/hw1.0/firmware-5.bin
>>  endef
> The new IPQ4019 firmware isn't as stable as the old one. I do see hangs
> from time to time (rx ring became corrupted). Whenever this is due to a
> bug in the firmware or the firmware is pushing harder, I don't know.
> 

Thank you for the information, so I will not upgrade the IPQ4019 firmware.

I also wanted to upgrade the QCA988X firmware first, but it was crashing
directly after being loaded and now linux-firmeware ships the old one again:
http://lists.infradead.org/pipermail/ath10k/2017-September/010138.html

Hauke

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

Re: [LEDE-DEV] WRT300N v2 AR5416 (was:MV88E6060 switch)

2017-10-15 Thread Sergey Ryazanov

On Mon, Oct 16, 2017 at 12:50 AM, Nerijus Baliunas
 wrote:
> WRT300N v2 has AR5416 card, so the driver should be ath9k. I enabled
> kmod-ath9k, but did not check "Support chips used in PC OEM cards" and
> "Enable TX99 support (WARNING: testing only, breaks normal operation!)".
> The module is loaded when booting, but:
>
> [   14.686040] ath9k :00:01.0: enabling device (0340 -> 0342)
> [   15.372420] kmodloader: page allocation failure: order:6, mode:0x240c0c0
> [   15.379319] CPU: 0 PID: 1331 Comm: kmodloader Not tainted 4.4.91 #0
> [   15.385595] Hardware name: Linksys WRT300N v2
> [   15.389993] Backtrace:
> ...
> [   15.755496] Mem-Info:
> [   15.757853] active_anon:135 inactive_anon:2 isolated_anon:0
> [   15.757853]  active_file:204 inactive_file:193 isolated_file:0
> [   15.757853]  unevictable:0 dirty:0 writeback:0 unstable:0
> [   15.757853]  slab_reclaimable:181 slab_unreclaimable:1094
> [   15.757853]  mapped:246 shmem:3 pagetables:20 bounce:0
> [   15.757853]  free:579 free_pcp:0 free_cma:0
> [   15.789499] DMA free:2316kB min:444kB low:552kB high:664kB 
> active_anon:540kB inactive_anon:8kB active_file:816kB inaco
> [   15.832021] lowmem_reserve[]: 0 0 0
> [   15.835528] DMA: 159*4kB (U) 76*8kB (U) 25*16kB (U) 13*32kB (U) 4*64kB (U) 
> 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB B
> [   15.847828] 400 total pagecache pages
> [   15.851504] 0 pages in swap cache
> [   15.854830] Swap cache stats: add 0, delete 0, find 0/0
> [   15.860105] Free swap  = 0kB
> [   15.862988] Total swap = 0kB
> [   15.865870] 4096 pages RAM
> [   15.868616] 0 pages HighMem/MovableOnly
> [   15.872456] 976 pages reserved
> [   16.518904] ath9k :00:01.0: Failed to initialize device
> [   16.525279] ath9k: probe of :00:01.0 failed with error -12
> [   16.535006] kmodloader: done loading kernel modules from /etc/modules.d/*
>
> is it because of low RAM?
> # cat /proc/meminfo
> MemTotal:  12480 kB
> MemFree: 576 kB
>

Yep, It looks like so.

You could try reduce firmware footprint by disabling some options
(e.g. disable IPv6 support, etc.).

-- 
Sergey

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

Re: [LEDE-DEV] [PATCH] uboot-sunxi: Backport fix for stale CONFIG_SUNXIG_GMAC references

2017-10-15 Thread Hauke Mehrtens

On 10/15/2017 11:05 AM, Zoltan HERPAI wrote:
> On Sat, 14 Oct 2017, Florian Fainelli wrote:
> 
>> This backports the upstream commit fixing stale references to
>> CONFIG_SUNXI_GMAC which have been later replaced by CONFIG_SUN7I_GMAC.
>> This fixes the designware MAC pinmuxing on e.g: Lamobo R1.
>>
>> Signed-off-by: Florian Fainelli 
> 
> Acked-by: Zoltan HERPAI 

Please refresh the patch and then

Acked-by: Hauke Mehrtens 

> 
>> ---
>> ...02-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch | 93
>> ++
>> 1 file changed, 93 insertions(+)
>> create mode 100644
>> package/boot/uboot-sunxi/patches/302-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch
>>
>>
>> diff --git
>> a/package/boot/uboot-sunxi/patches/302-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch
>> b/package/boot/uboot-sunxi/patches/302-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch
>>
>> new file mode 100644
>> index ..6e8a1ec8509b
>> --- /dev/null
>> +++
>> b/package/boot/uboot-sunxi/patches/302-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch
>>
>> @@ -0,0 +1,93 @@
>> +From 6ff005cf19363382fc867d7876a75fd8a386e894 Mon Sep 17 00:00:00 2001
>> +From: Dave Prue 
>> +Date: Thu, 31 Aug 2017 19:21:01 +0200
>> +Subject: [PATCH] sunxi: Fix CONFIG_SUNXI_GMAC references
>> +
>> +SUNXI_GMAC was still used to configure the code where as the
>> +same has been renamed and moved to Kconfig in below commit
>> +"sunxi: Move SUNXI_GMAC to Kconfig"
>> +(sha1: 4d43d065db3262f9a9918ba72457bf36dfb8e0bb)
>> +
>> +Signed-off-by: Dave Prue 
>> +Reviewed-by: Simon Glass 
>> +Reviewed-by: Jagan Teki 
>> +Reviewed-by: Mark Kettenis 
>> +Tested-by: Mark Kettenis 
>> +[Tweek commit message, config_whitelist.txt, build-whitelist.sh]
>> +Signed-off-by: Jagan Teki 
>> +---
>> + arch/arm/include/asm/arch-sunxi/sys_proto.h | 2 +-
>> + board/sunxi/Makefile    | 2 +-
>> + include/configs/sunxi-common.h  | 2 +-
>> + scripts/build-whitelist.sh  | 4 ++--
>> + scripts/config_whitelist.txt    | 1 -
>> + 5 files changed, 5 insertions(+), 6 deletions(-)
>> +
>> +Index: u-boot-2017.07/arch/arm/include/asm/arch-sunxi/sys_proto.h
>> +===
>> +--- u-boot-2017.07.orig/arch/arm/include/asm/arch-sunxi/sys_proto.h
>>  u-boot-2017.07/arch/arm/include/asm/arch-sunxi/sys_proto.h
>> +@@ -24,7 +24,7 @@ void sdelay(unsigned long);
>> + void return_to_fel(uint32_t lr, uint32_t sp);
>> +
>> + /* Board / SoC level designware gmac init */
>> +-#if !defined CONFIG_SPL_BUILD && defined CONFIG_SUNXI_GMAC
>> ++#if !defined CONFIG_SPL_BUILD && defined CONFIG_SUN7I_GMAC
>> + void eth_init_board(void);
>> + #else
>> + static inline void eth_init_board(void) {}
>> +Index: u-boot-2017.07/board/sunxi/Makefile
>> +===
>> +--- u-boot-2017.07.orig/board/sunxi/Makefile
>>  u-boot-2017.07/board/sunxi/Makefile
>> +@@ -9,7 +9,7 @@
>> + # SPDX-License-Identifier:    GPL-2.0+
>> + #
>> + obj-y    += board.o
>> +-obj-$(CONFIG_SUNXI_GMAC)    += gmac.o
>> ++obj-$(CONFIG_SUN7I_GMAC)    += gmac.o
>> + obj-$(CONFIG_SUNXI_AHCI)    += ahci.o
>> + obj-$(CONFIG_MACH_SUN4I)    += dram_sun4i_auto.o
>> + obj-$(CONFIG_MACH_SUN5I)    += dram_sun5i_auto.o
>> +Index: u-boot-2017.07/include/configs/sunxi-common.h
>> +===
>> +--- u-boot-2017.07.orig/include/configs/sunxi-common.h
>>  u-boot-2017.07/include/configs/sunxi-common.h
>> +@@ -302,7 +302,7 @@ extern int soft_i2c_gpio_scl;
>> + #define CONFIG_PHYLIB
>> + #endif
>> +
>> +-#ifdef CONFIG_SUNXI_GMAC
>> ++#ifdef CONFIG_SUN7I_GMAC
>> + #define CONFIG_PHY_GIGE    /* GMAC can use gigabit PHY    */
>> + #define CONFIG_PHY_ADDR    1
>> + #define CONFIG_MII    /* MII PHY management    */
>> +Index: u-boot-2017.07/scripts/build-whitelist.sh
>> +===
>> +--- u-boot-2017.07.orig/scripts/build-whitelist.sh
>>  u-boot-2017.07/scripts/build-whitelist.sh
>> +@@ -13,10 +13,10 @@ export LC_ALL=C LC_COLLATE=C
>> + # There are two independent greps. The first pulls out the component
>> parts
>> + # of CONFIG_SYS_EXTRA_OPTIONS. An example is:
>> + #
>> +-#    SUNXI_GMAC,AHCI,SATAPWR=SUNXI_GPB(8)
>> ++#    SUN7I_GMAC,AHCI,SATAPWR=SUNXI_GPB(8)
>> + #
>> + # We want this to produce:
>> +-#    CONFIG_SUNXI_GMAC
>> ++#    CONFIG_SUN7I_GMAC
>> + #    CONFIG_AHCI
>> + #    CONFIG_SATAPWR
>> + #
>> +Index: u-boot-2017.07/scripts/config_whitelist.txt
>> +===
>> +--- u-boot-2017.07.orig/scripts/config_whitelist.txt
>>  u-boot-2017.07/scripts/config_whitelist.txt
>> +@@ -2371,7 +2371,6 @@

[LEDE-DEV] WRT300N v2 AR5416 (was:MV88E6060 switch)

2017-10-15 Thread Nerijus Baliunas via Lede-dev

The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.

To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On Sat, 14 Oct 2017 17:48:12 +0300 Nerijus Baliunas 
 wrote:

> Thank you. Another question about wifi - there is no /etc/config/wireless
> file, and even if I create it and reboot the device, wifi is not working
> and there is no wlan0 interface. ath5k module is loaded.

WRT300N v2 has AR5416 card, so the driver should be ath9k. I enabled
kmod-ath9k, but did not check "Support chips used in PC OEM cards" and
"Enable TX99 support (WARNING: testing only, breaks normal operation!)".
The module is loaded when booting, but:

[   14.686040] ath9k :00:01.0: enabling device (0340 -> 0342)
[   15.372420] kmodloader: page allocation failure: order:6, mode:0x240c0c0
[   15.379319] CPU: 0 PID: 1331 Comm: kmodloader Not tainted 4.4.91 #0
[   15.385595] Hardware name: Linksys WRT300N v2
[   15.389993] Backtrace: 
[   15.392516] [] (dump_backtrace) from [] 
(show_stack+0x18/0x1c)
[   15.400134]  r7: r6:0006 r5:0240c0c0 r4:0001
[   15.405870] [] (show_stack) from [] 
(dump_stack+0x20/0x28)
[   15.413187] [] (dump_stack) from [] 
(warn_alloc_failed+0xf0/0x118)
[   15.421176] [] (warn_alloc_failed) from [] 
(__alloc_pages_nodemask+0x6c4/0x718)
[   15.430258]  r3:2001 r2:
[   15.433848]  r7: r6:0240c0c0 r5:0006 r4:0240c0c0
[   15.439603] [] (__alloc_pages_nodemask) from [] 
(alloc_kmem_pages+0x18/0x20)
[   15.448421]  r10:0002 r9:0004 r8: r7: r6:024080c0 
r5:c0a34c10
[   15.456290]  r4:c0a34b80
[   15.458925] [] (alloc_kmem_pages) from [] 
(kmalloc_order+0x18/0x4c)
[   15.466991] [] (kmalloc_order) from [] 
(__kmalloc+0x2c/0x120)
[   15.474897] [] (__kmalloc) from [] 
(ieee80211_txq_setup_flows+0x90/0x1f8 [mac80211])
[   15.484453]  r7: r6:002f r5:c0a34c10 r4:c0a34b80
[   15.490864] [] (ieee80211_txq_setup_flows [mac80211]) from 
[] (ieee80211_register_hw+0x898/0x948 )
[   15.502505]  r7: r6:002f r5: r4:c0a34b80
[   15.508685] [] (ieee80211_register_hw [mac80211]) from 
[] (ath9k_init_device+0x8e0/0xa04 [ath9k])
[   15.519371]  r10:c0e800fc r9:c0e80010 r8:c0e80010 r7: r6: 
r5:c0a34b80
[   15.527246]  r4:c0a354a0
[   15.529948] [] (ath9k_init_device [ath9k]) from [] 
(ath_pci_probe+0x240/0x2fc [ath9k])
[   15.539632]  r10: r9:bf1db968 r8:c0a34b80 r7: r6:c084bc68 
r5:c0a354a0
[   15.547501]  r4:c084bc00
[   15.550170] [] (ath_pci_probe [ath9k]) from [] 
(pci_device_probe+0x70/0xbc)
[   15.558911]  r10:c005bec8 r9:0001 r8:bf1de4c0 r7: r6:c084bc68 
r5:c084bc00
[   15.566785]  r4:bf1de4f4
[   15.569385] [] (pci_device_probe) from [] 
(driver_probe_device+0xf4/0x258)
[   15.578027]  r9:0001 r8:bf1de4f4 r7:c03ba818 r6:c03ba81c r5:c084bc9c 
r4:c084bc68
[   15.585842] [] (driver_probe_device) from [] 
(__driver_attach+0x70/0x94)
[   15.594315]  r9: r8:c0372008 r7:c0388b28 r6:bf1de4f4 r5:c084bc9c 
r4:c084bc68
[   15.602179] [] (__driver_attach) from [] 
(bus_for_each_dev+0x74/0x98)
[   15.610389]  r7:c0388b28 r6:c018681c r5:bf1de4f4 r4:
[   15.616117] [] (bus_for_each_dev) from [] 
(driver_attach+0x20/0x28)
[   15.624153]  r6:c055a900 r5: r4:bf1de4f4
[   15.628850] [] (driver_attach) from [] 
(bus_add_driver+0xd4/0x1e8)
[   15.636803] [] (bus_add_driver) from [] 
(driver_register+0xa4/0xe8)
[   15.644843]  r7:c0376008 r6:c0376008 r5:bf1e1000 r4:bf1de4f4
[   15.650595] [] (driver_register) from [] 
(__pci_register_driver+0x38/0x40)
[   15.659240]  r5:bf1e1000 r4:c0428ee0
[   15.662919] [] (__pci_register_driver) from [] 
(ath_pci_init+0x1c/0x2c [ath9k])
[   15.672150] [] (ath_pci_init [ath9k]) from [] 
(init_module+0x14/0x38 [ath9k])
[   15.681153] [] (init_module [ath9k]) from [] 
(do_one_initcall+0x1bc/0x200)
[   15.689863] [] (do_one_initcall) from [] 
(do_init_module+0x60/0x1a0)
[   15.697985]  r9:c0d83f34 r8:001a r7: r6:c0428420 r5:c06bc800 
r4:bf1de540
[   15.705803] [] (do_init_module) from [] 
(load_module+0x1444/0x188c)
[   15.713848]  r6:c06bca10 r5:c06bc800 r4:bf1de540
[   15.718540] [] (load_module) from [] 
(SyS_init_module+0x114/0x134)
[   15.726460]  r10:0051 r9:c0d82000 r8:0001276a r7:c1b0417c r6: 
r5:b6f2518c
[   15.734358]  r4:c17c
[   15.736932] [] (SyS_init_module) from [] 
(ret_fast_syscall+0x0/0x38)
[   15.745060]  r10: r9:c0d82000 r8:c0009564 r7:0080 r6:0003 
r5:
[   15.752956]  r4:1f02
[   15.755496] Mem-Info:
[   15.757853] active_anon:135 inactive_anon:2 isolated_anon:0
[   15.757853]  active_file:204 inactive_file:193 isolated_file:0
[   15.757853]  unevictable:0 dirty:0 writeback:0 unstable:0
[   15.757853]  slab_reclaimable:181 slab_unreclaimable:1094
[   15.757853]  mapped:246 shmem:3

[LEDE-DEV] test omap target with kernel 4.9

2017-10-15 Thread Hauke Mehrtens

Hi,

I added kernel 4.9 support for the omap target, could someone please
test this on some device if it is still working and report back so I can
fix the problems or merge this to master.

You can find my code here:
https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/omap

Hauke

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

[LEDE-DEV] [PATCH] ipq806x: add ap.dk01.1 board support

2017-10-15 Thread Roman Yeryomin

- add partitions
- enable wifi and ethernet
- set max cpu speed to 710MHz
- set memory size to 256MB
- add image generation
- extract pre-cal data from ART partition

Wirespeed NAT can be achieved with spreading rx interrupts over different cores.
Wifi needs love -- too slow. Could be that latest ath10k helps, didn't test yet.

Signed-off-by: Roman Yeryomin 
---
 .../etc/hotplug.d/firmware/11-ath10k-caldata   |  6 ++
 target/linux/ipq806x/base-files/lib/ipq806x.sh |  3 +
 target/linux/ipq806x/image/Makefile| 18 -
 ...s-ipq4019-ap.dk01.1-add-256MB-memory-node.patch | 14 
 ...2-dts-ipq4019-ap.dk01.1-fix-max-cpu-speed.patch | 15 
 ...4-03-dts-ipq4019-ap.dk01.1-add-partitions.patch | 72 ++
 ...pq4019-ap.dk01.1-enable-wifi-and-ethernet.patch | 87 ++
 7 files changed, 214 insertions(+), 1 deletion(-)
 create mode 100644 
target/linux/ipq806x/patches-4.9/864-01-dts-ipq4019-ap.dk01.1-add-256MB-memory-node.patch
 create mode 100644 
target/linux/ipq806x/patches-4.9/864-02-dts-ipq4019-ap.dk01.1-fix-max-cpu-speed.patch
 create mode 100644 
target/linux/ipq806x/patches-4.9/864-03-dts-ipq4019-ap.dk01.1-add-partitions.patch
 create mode 100644 
target/linux/ipq806x/patches-4.9/864-04-dts-ipq4019-ap.dk01.1-enable-wifi-and-ethernet.patch

diff --git 
a/target/linux/ipq806x/base-files/etc/hotplug.d/firmware/11-ath10k-caldata 
b/target/linux/ipq806x/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 39757eb..271667f 100644
--- a/target/linux/ipq806x/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ipq806x/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -50,6 +50,9 @@ case "$FIRMWARE" in
fritz4040)
/usr/bin/fritz_cal_extract -i 1 -s 0x400 -e 0x207 -l 12064 -o 
/lib/firmware/$FIRMWARE $(find_mtd_chardev "urlader_config")
;;
+   ap-dk01.1-c1)
+   ath10kcal_extract "ART" 4096 12064
+   ;;
esac
;;
 "ath10k/pre-cal-ahb-a80.wifi.bin")
@@ -57,6 +60,9 @@ case "$FIRMWARE" in
fritz4040)
/usr/bin/fritz_cal_extract -i 1 -s 0x400 -e 0x208 -l 12064 -o 
/lib/firmware/$FIRMWARE $(find_mtd_chardev "urlader_config")
;;
+   ap-dk01.1-c1)
+   ath10kcal_extract "ART" 20480 12064
+   ;;
esac
;;
 
diff --git a/target/linux/ipq806x/base-files/lib/ipq806x.sh 
b/target/linux/ipq806x/base-files/lib/ipq806x.sh
index e8ff7ea..940c7ef 100644
--- a/target/linux/ipq806x/base-files/lib/ipq806x.sh
+++ b/target/linux/ipq806x/base-files/lib/ipq806x.sh
@@ -14,6 +14,9 @@ ipq806x_board_detect() {
machine=$(cat /proc/device-tree/model)
 
case "$machine" in
+   *"AP-DK01.1-C1")
+   name="ap-dk01.1-c1"
+   ;;
*"AP148")
name="ap148"
;;
diff --git a/target/linux/ipq806x/image/Makefile 
b/target/linux/ipq806x/image/Makefile
index 3a76c7f..60b3a71 100644
--- a/target/linux/ipq806x/image/Makefile
+++ b/target/linux/ipq806x/image/Makefile
@@ -264,7 +264,23 @@ define Device/AP-DK04.1-C1
DEVICE_TITLE := QCA AP-DK04.1-C1
 endef
 
+define Device/AP-DK01.1-C1
+   PROFILES += $$(DEVICE_NAME)
+   DEVICE_TITLE := QCA AP-DK01.1-C1
+   BOARD_NAME := ap-dk01.1-c1
+   DEVICE_DTS := qcom-ipq4019-ap.dk01.1-c1
+   KERNEL_LOADADDR := 0x80208000
+   KERNEL_INSTALL := 1
+   KERNEL_SIZE := 4096k
+   IMAGE_SIZE := 26624k
+   FILESYSTEMS := squashfs
+   $(call Device/FitImage)
+   IMAGES := sysupgrade.bin
+   IMAGE/sysupgrade.bin := append-kernel | pad-to {KERNEL_SIZE} | 
append-rootfs | pad-rootfs | append-metadata
+   DEVICE_PACKAGES := ath10k-firmware-qca4019
+endef
+
 TARGET_DEVICES += AP148 AP148-legacy C2600 D7800 DB149 EA8500 FRITZ4040 R7500 \
- R7500v2 R7800 NBG6817 VR2600v AP-DK04.1-C1
+ R7500v2 R7800 NBG6817 VR2600v AP-DK04.1-C1 AP-DK01.1-C1
 
 $(eval $(call BuildImage))
diff --git 
a/target/linux/ipq806x/patches-4.9/864-01-dts-ipq4019-ap.dk01.1-add-256MB-memory-node.patch
 
b/target/linux/ipq806x/patches-4.9/864-01-dts-ipq4019-ap.dk01.1-add-256MB-memory-node.patch
new file mode 100644
index 000..8a80979
--- /dev/null
+++ 
b/target/linux/ipq806x/patches-4.9/864-01-dts-ipq4019-ap.dk01.1-add-256MB-memory-node.patch
@@ -0,0 +1,14 @@
+--- a/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi
 b/arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1.dtsi
+@@ -20,6 +20,11 @@
+   model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK01.1";
+   compatible = "qcom,ipq4019";
+ 
++  memory {
++  device_type = "memory";
++  reg = <0x8000 0x1000>;
++  };
++
+   clocks {
+ xo: xo {
+ compatible = "fixed-clock";
diff --git 
a/target/linux/ipq806x/patches-4.9/864-02-dts-ipq4019-ap.dk01.1-fix-max-cpu-speed.patch

[LEDE-DEV] test at91 target with kernel 4.9

2017-10-15 Thread Hauke Mehrtens

Hi,

I added kernel 4.9 support for the at91 target, could someone please
test this on some device if it is still working and report back so I can
fix the problems or merge this to master.

You can find my code here:
https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/at91

Hauke

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

[LEDE-DEV] SDK Error: Makefile:48: *** DESCRIPTION:= is obsolete

2017-10-15 Thread yanosz

Hello,

I'm trying to create a package following:
https://lede-project.org/docs/guide-developer/helloworld/start

When I do
make -j1 V=99 package/hellowold/compile

I get:

make[3]: Entering directory
'/tmp/lede-sdk-17.01.3-x86-64_gcc-5.4.0_musl-1.1.16.Linux-x86_64/build_dir/target-x86_64_musl-1.1.16/helloworld-1.0'
Makefile:48: *** DESCRIPTION:= is obsolete, use
Package/PKG_NAME/description.  Stop.
[...]

The Makefile is at:
https://gist.github.com/yanosz/09198538d019d393f5e571d1a573a2c7
Notice, that DESCRIPTION:= is unset, thus the warning appears to be false.

It seems, that the DESCRIPTION is set during the built, causing the error.

When removing the check, the makefile seems to in into an endless recursion:

shell-init: error retrieving current directory: getcwd: cannot access
parent directories: No such file or directory
make: getcwd: No such file or directory
make[153]: Entering directory
'/tmp/lede-sdk-17.01.3-x86-64_gcc-5.4.0_musl-1.1.16.Linux-x86_64/build_dir/target-x86_64_musl-1.1.16/helloworld-1.0'

I quit after 153 tries, ending the loop.

What may be wrong here?

Thanks,
yanosz



-- 
For those of you without hope, we have rooms with color TV,
cable and air conditioning

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

Re: [LEDE-DEV] [PATCH] uboot-sunxi: Backport fix for stale CONFIG_SUNXIG_GMAC references

2017-10-15 Thread Zoltan HERPAI


On Sat, 14 Oct 2017, Florian Fainelli wrote:


This backports the upstream commit fixing stale references to
CONFIG_SUNXI_GMAC which have been later replaced by CONFIG_SUN7I_GMAC.
This fixes the designware MAC pinmuxing on e.g: Lamobo R1.

Signed-off-by: Florian Fainelli 


Acked-by: Zoltan HERPAI 


---
...02-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch | 93 ++
1 file changed, 93 insertions(+)
create mode 100644 
package/boot/uboot-sunxi/patches/302-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch

diff --git 
a/package/boot/uboot-sunxi/patches/302-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch
 
b/package/boot/uboot-sunxi/patches/302-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch
new file mode 100644
index ..6e8a1ec8509b
--- /dev/null
+++ 
b/package/boot/uboot-sunxi/patches/302-sunxi-Fix-CONFIG_SUNXI_GMAC-references.patch
@@ -0,0 +1,93 @@
+From 6ff005cf19363382fc867d7876a75fd8a386e894 Mon Sep 17 00:00:00 2001
+From: Dave Prue 
+Date: Thu, 31 Aug 2017 19:21:01 +0200
+Subject: [PATCH] sunxi: Fix CONFIG_SUNXI_GMAC references
+
+SUNXI_GMAC was still used to configure the code where as the
+same has been renamed and moved to Kconfig in below commit
+"sunxi: Move SUNXI_GMAC to Kconfig"
+(sha1: 4d43d065db3262f9a9918ba72457bf36dfb8e0bb)
+
+Signed-off-by: Dave Prue 
+Reviewed-by: Simon Glass 
+Reviewed-by: Jagan Teki 
+Reviewed-by: Mark Kettenis 
+Tested-by: Mark Kettenis 
+[Tweek commit message, config_whitelist.txt, build-whitelist.sh]
+Signed-off-by: Jagan Teki 
+---
+ arch/arm/include/asm/arch-sunxi/sys_proto.h | 2 +-
+ board/sunxi/Makefile| 2 +-
+ include/configs/sunxi-common.h  | 2 +-
+ scripts/build-whitelist.sh  | 4 ++--
+ scripts/config_whitelist.txt| 1 -
+ 5 files changed, 5 insertions(+), 6 deletions(-)
+
+Index: u-boot-2017.07/arch/arm/include/asm/arch-sunxi/sys_proto.h
+===
+--- u-boot-2017.07.orig/arch/arm/include/asm/arch-sunxi/sys_proto.h
 u-boot-2017.07/arch/arm/include/asm/arch-sunxi/sys_proto.h
+@@ -24,7 +24,7 @@ void sdelay(unsigned long);
+ void return_to_fel(uint32_t lr, uint32_t sp);
+
+ /* Board / SoC level designware gmac init */
+-#if !defined CONFIG_SPL_BUILD && defined CONFIG_SUNXI_GMAC
++#if !defined CONFIG_SPL_BUILD && defined CONFIG_SUN7I_GMAC
+ void eth_init_board(void);
+ #else
+ static inline void eth_init_board(void) {}
+Index: u-boot-2017.07/board/sunxi/Makefile
+===
+--- u-boot-2017.07.orig/board/sunxi/Makefile
 u-boot-2017.07/board/sunxi/Makefile
+@@ -9,7 +9,7 @@
+ # SPDX-License-Identifier:GPL-2.0+
+ #
+ obj-y += board.o
+-obj-$(CONFIG_SUNXI_GMAC)  += gmac.o
++obj-$(CONFIG_SUN7I_GMAC)  += gmac.o
+ obj-$(CONFIG_SUNXI_AHCI)  += ahci.o
+ obj-$(CONFIG_MACH_SUN4I)  += dram_sun4i_auto.o
+ obj-$(CONFIG_MACH_SUN5I)  += dram_sun5i_auto.o
+Index: u-boot-2017.07/include/configs/sunxi-common.h
+===
+--- u-boot-2017.07.orig/include/configs/sunxi-common.h
 u-boot-2017.07/include/configs/sunxi-common.h
+@@ -302,7 +302,7 @@ extern int soft_i2c_gpio_scl;
+ #define CONFIG_PHYLIB
+ #endif
+
+-#ifdef CONFIG_SUNXI_GMAC
++#ifdef CONFIG_SUN7I_GMAC
+ #define CONFIG_PHY_GIGE   /* GMAC can use gigabit PHY 
*/
+ #define CONFIG_PHY_ADDR   1
+ #define CONFIG_MII/* MII PHY management   */
+Index: u-boot-2017.07/scripts/build-whitelist.sh
+===
+--- u-boot-2017.07.orig/scripts/build-whitelist.sh
 u-boot-2017.07/scripts/build-whitelist.sh
+@@ -13,10 +13,10 @@ export LC_ALL=C LC_COLLATE=C
+ # There are two independent greps. The first pulls out the component parts
+ # of CONFIG_SYS_EXTRA_OPTIONS. An example is:
+ #
+-# SUNXI_GMAC,AHCI,SATAPWR=SUNXI_GPB(8)
++# SUN7I_GMAC,AHCI,SATAPWR=SUNXI_GPB(8)
+ #
+ # We want this to produce:
+-# CONFIG_SUNXI_GMAC
++# CONFIG_SUN7I_GMAC
+ # CONFIG_AHCI
+ # CONFIG_SATAPWR
+ #
+Index: u-boot-2017.07/scripts/config_whitelist.txt
+===
+--- u-boot-2017.07.orig/scripts/config_whitelist.txt
 u-boot-2017.07/scripts/config_whitelist.txt
+@@ -2371,7 +2371,6 @@ CONFIG_STV0991_HZ_CLOCK
+ CONFIG_ST_SMI
+ CONFIG_SUNXI_AHCI
+ CONFIG_SUNXI_EMAC
+-CONFIG_SUNXI_GMAC
+ CONFIG_SUNXI_GPIO
+ CONFIG_SUNXI_MAX_FB_SIZE
+ CONFIG_SUNXI_USB_PHYS
--
2.11.0


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



___
Lede-dev mailing list

Re: [LEDE-DEV] [PATCH 0/4] ar71xx: add support for kernel 4.9

Re: [LEDE-DEV] test omap target with kernel 4.9

Re: [LEDE-DEV] test omap target with kernel 4.9

[LEDE-DEV] [PATCH 2/2] ixp4xx: drop the jumbo frame support

[LEDE-DEV] [PATCH 0/2] ixp4xx: ethernet fixes (WRT300N v2)

[LEDE-DEV] [PATCH 1/2] ixp4xx: fix non-standard phy support

[LEDE-DEV] [RFC] at91: fix build of legacy target

Re: [LEDE-DEV] [PATCH] kernel: enable CONFIG_ADVISE_SYSCALLS

[LEDE-DEV] ar71xx use kernel 4.9 by default

Re: [LEDE-DEV] [PATCH v2] ath10k-ct driver: use dma_alloc_coherent, 4.13 based driver

Re: [LEDE-DEV] [PATCH] ath10k-firmware: update QCA9888 and QCA4019 firmware

Re: [LEDE-DEV] WRT300N v2 AR5416 (was:MV88E6060 switch)

Re: [LEDE-DEV] [PATCH] uboot-sunxi: Backport fix for stale CONFIG_SUNXIG_GMAC references

[LEDE-DEV] WRT300N v2 AR5416 (was:MV88E6060 switch)

[LEDE-DEV] test omap target with kernel 4.9

[LEDE-DEV] [PATCH] ipq806x: add ap.dk01.1 board support

[LEDE-DEV] test at91 target with kernel 4.9

[LEDE-DEV] SDK Error: Makefile:48: *** DESCRIPTION:= is obsolete

Re: [LEDE-DEV] [PATCH] uboot-sunxi: Backport fix for stale CONFIG_SUNXIG_GMAC references

19 matches

Site Navigation

Mail list logo

Footer information