Re: [PATCH] ath79: Push MV88E6060 DSA switch into package

)add those three config symbols would be much easier than shaving off another 800 KB (or ~950-1000 KB with kernel v6.6 now) from that already below-minimal image. Regards Stefan Lippers-Hollmann --- End Message --- ___ openwrt-deve

Re: Buildbots missing for ipq60xx?

until this is resolved and the source-only flag gets removed - pending a new (and official, not via third parties) wireless firmware release from QCA. Regards Stefan Lippers-Hollmann pgpoUDeNUHhFd.pgp Description: Digitale Signatur von OpenPGP --- End Message --- __

Re: qca-wireless: ipq50xx: ipq5018: add bdf for ikuai sw8

ly I'm not an OpenWrt developer and can't for the project in any way. so take this as my personal suggestion for an ideal way forward. Regards Stefan Lippers-Hollmann --- End Message --- ___ openwrt-devel mailing list openwrt-devel@l

Re: [PATCH 1/1] kernel/x86: merge "generic" into "legacy"

ly used for "legacy"-class machines, but it was > genuinely available. Running an i386 VM on x86_64 hosts is not uncommon, these are for the emulated hardware in a VM, not (necessarily) the host. > > +CONFIG_XEN=y […] > > Xen got started on this class of machine. At th

Re: [PATCH 11/11] kernel/x86: enable x32 support for amd64

Hi On 2023-11-14, Elliott Mitchell wrote: > On Wed, Nov 15, 2023 at 05:35:11AM +0100, Stefan Lippers-Hollmann wrote: > > On 2023-11-14, Elliott Mitchell wrote: [...] > > What would be the reason for enabling x32? > > There is very little upstream buy-in for x32, when this que

Re: [PATCH 11/11] kernel/x86: enable x32 support for amd64

Hi On 2023-11-15, Stefan Lippers-Hollmann wrote: > On 2023-11-14, Elliott Mitchell wrote: > > Date: Thu, 30 Mar 2023 16:30:49 -0700 > > > > Full amd64 support isn't really appropriate for most situations > > OpenWRT is deployed. Whereas x86-x32 seems ext

Re: [PATCH 11/11] kernel/x86: enable x32 support for amd64

ut... If I read it correctly, you enable CONFIG_X86_X32 in target/linux/x86/config-*, while explicitly disabling it in the only subtarget config (target/linux/x86/64/config-*) where it would matter, is that really the intended way round and in line with the commit description? Regards Stefa

Re: [PATCH 08/11] kernel/x86: move SCx200 support from generic to geode

dropping it down to legacy (geode?) would be preferable to the status quo (so one x86_64 subtarget and one combined i486/i586/i686 subtarget). */ Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.

Re: Adding a new x86 image or related packages to the default x86 image

to this churn and pretty much rot away in the tree, while at the same time making progress harder for the other x86{,_64} devices. Regards Stefan Lippers-Hollmann pgpbyqv1ZCjkx.pgp Description: Digitale Signatur von OpenPGP ___ op

Re: Objective of OpenWRT/x86?

to provide high-density demands, you'd end up with at least five (kvm, Xen, hyper-v, virtualbox, vmware, parallels, maybe more) new images next to x86_64/generic, which I don't think anyone really wants or needs (those who do, will want even more fine-tuned i

Re: [PATCH 0/9] (mostly) x86 kernel configuration adjustments

Hi On 2023-04-26, Elliott Mitchell wrote: > On Thu, Apr 27, 2023 at 01:11:13AM +0200, Stefan Lippers-Hollmann wrote: > > On 2023-04-26, Elliott Mitchell wrote: > > [...] > > > > > > Looks like little of ISA remained on "64", yet some DMA support rema

Re: [PATCH 0/9] (mostly) x86 kernel configuration adjustments

sting hardware. (It's pointless to enable x32, unless you can demonstrate that OpenWrt's buildsystem can successfully build for it, with a 32 bit userland and 64 bit kernels). Regards Stefan Lippers-Hollmann pgpI7VuI7p1FI.pgp Description: Digitale Signatur von OpenPGP __

Re: [PATCH 9/9] kernel/x86: remove DRM support

away from deprecated (FB_*) graphics drivers to DRM based ones, with kernel based mode setting this is getting more (any) attention for console support as well. Even without getting anywhere near X/ Wayland, there is more than just a 80x25 tty on real hardware (and even VMs). Regards Stefa

Re: [PATCH 6/9] kernel/x86: enable x32 support for amd64

s as well (as in major toolchain changes necessary to get it working as expected). Regards Stefan Lippers-Hollmann pgpOhkC04JJfF.pgp Description: Digitale Signatur von OpenPGP ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: 22.03.3 for mvebu (Turris Omnia)

until the next kernel v5.15 based major stable release arrives (23.xy.0) or until 22.03.x gets fixed eventually (which doesn't appear to be very likely at the moment). Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openw

Re: [PATCH 7/8] ath10k-ct: Support qcom,ath10k-calibration-data-base64

not check wolfssl/ mbedtls for potential alternatives. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [PATCH 1/3] hostapd: update to 2022-05-08

Hi On 2022-06-12, Stefan Lippers-Hollmann wrote: > On 2022-06-07, David Bauer wrote: > > Update hostapd to Git HEAD from 2022-05-08. This allows us to take > > advantage of background radar-detection ad well as BSS color collision. > > I'm noticing a build failure for wp

Re: [PATCH 1/3] hostapd: update to 2022-05-08

PRECATED=y # CONFIG_OPENSSL_WITH_DEPRECATED is not set Reverting the last four patches to hostapd fixes the issue again: b72c7db2293cf728851696e6370806cc3e0fa305 hostapd: fix missing HS20 support for hostapd-full 6ee4383350bc5b1920f81095f2ecd05b14e3bff6 hostapd: ubus: add bss-color to get_stat

Re: [PATCH v2 1/3] Move mvswitch 88E6060 driver to the ath25

t;a=blob;f=target/linux/ar71xx/base-files/etc/board.d/02_network;h=44fce970c0fd8b4811242fac0b53764a09244a2f;hb=refs/heads/openwrt-19.07#l324 so it should be possible for ath25 as well, although the effort might not be worth it, considering the age and specifications of the target devices. Regards

Re: Best VSDL modem-router to target?

(ATA, VoIP-DECT base, etc.). The forum has quite a lot of information about these devices and may be better suited to guide you on your search. Regards Stefan Lippers-Hollmann pgpydzY80VKJN.pgp Description: Digitale Signatur von OpenPGP ___ openwr

Re: mac address issue of tp-link wdr3600 and archer c7-v2

wireless interface that generally won't cause too much trouble. The documented behaviour for the tl-wdr3600 would be: LAN label WAN label + 1 5G label 2G label - 1 according to https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=a4260ea

Re: Release goals for 22.XX

t.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ar71xx/config-4.14;h=9a524fae4316caa10431bd6b3b4dadbe8660f14c;hb=d5ae5658730a82312a20e68220f92f611b11d094#l433 and https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr941nd.c;h=1ddeec730eab47

Re: Release goals for 22.XX

as already been used by the tl-wr941nd v2/ v3 (very early ath79/ tiny) for many years, this might help for reference. https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ath79/dts/ar9132_tplink_tl-wr941-v2.dts;h=58586eb03615b3ef95963182

Re: Build issues gcc10

00:17 sha256sums -rw-r--r-- 1 18 13. Sep 00:11 version.buildinfo $ ls -1 bin/targets/ipq806x/generic/packages/kmod-* | cut -d_ -f2 | sort -u 5.10.63-1 5.10.63+1.11-ipq806x-1 5.10.63-2 5.10.63+2020-12-07-1e9689c8-1 5.10.63+2021-06-03-b44cd7b2-5 5.10.63+2021-06-24-9b3a8197-1 5.10.63+2021-07-1

Re: Question about qca8k dsa driver and path to follow

then moving the patches from ipq806x to generic later, when there is something tangible for ath79 or bcm53xx (as part of their PRs/ patch series to migrate from swconfig to qca8k). Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing li

Re: Clarification about dsa and ipq806x

ail/openwrt-devel/2020-September/031417.html Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [PATCH 1/2] realtek: Add generic zyxel_gs1900 image definition

1900-24HP:AAHM GS1900-24HPv2: ABTP GS1900-48: AAHN GS1900-48HP:AAHO GS1900-48HPv2: ABTQ Most of these should be supportable by OpenWrt. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: 20.xx: state of the DSA

L8382M) has been pretty positive so far. I haven't really stressed it too much, but the simple cases I needed are working nicely. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.

Re: 20.xx: state of the DSA

sible to migrate additional targets over to DSA right now, even for the devices where drivers exist, as this would invalidate all testing on these devices. IMHO this would be more of a todo item for immediately after 20.xy.0 gets released. Regards Stefan Lippers-Hollmann ___

Re: 20.xx: postponse LuCI HTTPS per default

a significant portion of OpenWrt's most common use cases, without introducing serious problems and side-effects for a significant number of OpenWrt users - and/or would require heavy investments into OpenWrt's infrastructure (technical and legal). Regards Stefan Lippers-Hol

Re: The status of intel ax200 support (iwlwifi)

re won't allow AP mode in the 5 GHz band at all (maybe using 25 mW on the short range band (ETSI EN 300 440-1), if you're lucky). That is an intentional choice from Intel to restrict (all of-) their WLAN cards and not fixable. Regards Stefan Lippers-Hollmann

Re: A proposal of https certificate assignment system for luci

configure VLAN tagging on WAN or adding PPPoE credentials. For these, the user will have to accept a self-signed certificate at least once for doing the initial configuration - at which point they can just stick to the already accepted self-signed certificate as well. Regards Stefan Lippers-Ho

Re: [PATCH] kernel: add ar5523 driver

-G/ Super-AG with up to 108 MBit/s) and doesn't support 802.11n, so +@DRIVER_11N_SUPPORT should be dropped. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re:

is probably not going to work, as quite a lot of ath79 devices depend on a different kernel/ rootfs split for the flash partitioning. Regards Stefan Lippers-Hollmann -- [0] target/linux/ipq806x/patches-5.4/0067-generic-Mangle-bootloader-s-kernel-arguments.patch target/linux/mvebu/p

Re: Release goals for 20.XX

repos pushed from downloads.openwrt.org and the canonical location of the git repos is git.openwrt.org (github is just a mirror and the package feeds are a different question alltogether). This migration to gitlab can happen at any point and doesn't need to be tied to a release. Regards Stefa

Re: Simplified LuCI interface project: dashboard, quick setup, configuration

simplified/ easy setup assistant (as long as full luci is easily available - and considering that the easy overview doesn't get confused by this). Regards Stefan Lippers-Hollmann [0] push := default and strongly suggested by the OEM firmware, but

Re: [PATCH] kernel: bump 5.4 to 5.4.53

he cake hack as upstream have backported the changes themselves, > but in a slightly different way. > > generic/hack-5.4/641-sch_cake-fix-IP-protocol-handling-in-the-presence-of.patch > > Signed-off-by: Kevin Darbyshire-Bryant [...] Runtime tested on: Tested-by: Stefan Lipper

Re: [OpenWrt-Devel] [PATCH] ath79: switch to kernel 5.4

HP-AG300H/ AR7161 - TP-Link TL-WDR3600/ AR9344 - TP-Link TL-WDR4300/ AR9344 Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [PATCH] kernel: Fix ath79 DSP exception at bootup

Mehrtens [...] I can confirm that this works on the TP-Link TL-WDR3600 and TL-WDR4300, tested on top of r13676-g9858a8c582 with kernel 5.4.50 and this patch. Thanks a lot for looking into this. Tested-by: Stefan Lippers-Hollmann [ath79/tl-wdr3600; ath79/tl-wdr4300] Regards Stefa

Re: [OpenWrt-Devel] [PATCH] ath79: switch to kernel 5.4

's master/ r13611-3f27a6e640, tested on both tl-wdr3600 and tl-wdr4300 with kernel v5.4.48. The device bootloops very early and in close succession, requiring tftp recovery[0]. Regards Stefan Lippers-Hollmann -- [0] early hardware revisions before h/w rev. 1.5 didn't ship with

Re: [OpenWrt-Devel] [PATCH 1/2] hostapd: update to latest Git hostap_2_9-1113-gc54a5e96b505

hwcrypto 1 Reverting just these two hostapd patches, but keeping the mac80211 bump, the warnings vanish immediately. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 1/3] ipq806x: remove support for kernel 4.14

4.19 kernel version") > > Signed-off-by: Adrian Schmutzler [...] Acked-by: Stefan Lippers-Hollmann [ipq8065/nbg6817] Thanks a lot for looking into this, given the rather good feedback for kernel 5.4 testing on ipq806x (at least r7500v2, r7800 and nbg6817 are covered with good results

Re: [OpenWrt-Devel] RFT: Add support for kernel 5.4

Hi On 2020-03-09, Adrian Schmutzler wrote: > > -Original Message- > > From: Stefan Lippers-Hollmann [mailto:s@gmx.de] [...] > > On 2020-02-28, John Crispin wrote: > > > On 28.02.20 21:30, Stefan Lippers-Hollmann wrote: > > > > On 202

Re: [OpenWrt-Devel] [PATCH] exfat-nofuse: fix kernel 5.4 compilation issue

eption. > I also want an exfat package for 5.4. As it stands even though it is > in the staging directory, I don't think a package is available. https://github.com/openwrt/openwrt/pull/2807 [...] Regards Stefan Lippers-Hollmann __

Re: [OpenWrt-Devel] RFT: Add support for kernel 5.4

Hi On 2020-02-28, John Crispin wrote: > On 28.02.20 21:30, Stefan Lippers-Hollmann wrote: > > On 2020-02-28, m...@adrianschmutzler.de wrote: > >>> On 2020-02-28, Koen Vandeputte wrote: [...] > > ath79 with kernel 4.14 has already been (mostly) broken by "ath7

Re: [OpenWrt-Devel] RFT: Add support for kernel 5.4

On 2020-02-28, Stefan Lippers-Hollmann wrote: [...] > does break the (shared between all kernel versions) DTS definitions for > NAND based ath79 devices (breaking compilation with kernel 4.14). Obviously this not meant to read NAND, but the more modern SOCs using this new SPI driver (only a

Re: [OpenWrt-Devel] RFT: Add support for kernel 5.4

geextender +#TARGET_DEVICES += winchannel_wb2000 +#TARGET_DEVICES += zbtlink_zbt-wd323 Admittedly, the affected TL-WR941ND v2 (4/32) is barely worth the effort anymore. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH 4/4] scripts/gen_image_generic.sh: use /bin/sh

Hi On 2019-12-29, Rosen Penev wrote: > This has nothing bash specific. [...] > +++ b/scripts/gen_image_generic.sh > @@ -1,4 +1,4 @@ > -#!/usr/bin/env bash > +#!/bin/bash I assume this was supposed to become #!/bin/sh instead? Regards Stefan Lippers-Hollmann -- Thanks f

[OpenWrt-Devel] [PATCH v2] mac80211: Adapt to changes to skb_get_hash_perturb()

e Mehrtens Signed-off-by: Stefan Lippers-Hollmann --- ...t-to-changes-to-skb_get_hash_perturb.patch | 68 +++ 1 file changed, 68 insertions(+) create mode 100644 package/kernel/mac80211/patches/build/102-backports-Adapt-to-changes-to-skb_get_hash_perturb.patch The second hunk was mi

Re: [OpenWrt-Devel] v5.4 as next kernel

mes no longer crash stmmac, so I do consider the current state of the v4.19 patches for ipq806x to be an improvement over v4.14). Regards Stefan Lippers-Hollmann [0] https://github.com/openwrt/openwrt/pull/2472 ___ openwrt-devel mailing

Re: [OpenWrt-Devel] [PATCH 1/6] hostapd: update to version 2.8

ostap/list/?series=62725&state=* > > Signed-off-by: Hauke Mehrtens Tested-by: Stefan Lippers-Hollmann [...] > --- a/package/network/services/hostapd/Makefile > +++ b/package/network/services/hostapd/Makefile > @@ -11,9 +11,9 @@ PKG_RELEASE:=6 > > PKG_SOURCE_URL:

Re: [OpenWrt-Devel] Bumping ar71xx to 4.14

od state of ath79, it might be useful to lift the source-only flag for it soon. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] LEDE > OpenWrt > TP-Link TL-WDR4900 1.0

kports) versions - which shouldn't happen, but in practice does occassionally. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenWrt 19.01 plans

ur target is still on an older kernel (e.g. ar71xx is still on kernel 4.9), it isn't available. Regards Stefan Lippers-Hollmann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2] build: add mkrasimage

Hi On 2018-08-21, David Bauer wrote: > On 8/21/18 8:31 AM, Stefan Lippers-Hollmann wrote: > > While this passes the version check, the appended git hash does break > > later on in the flashing process - so at the moment only the numerical > > revision (of DISTRIB_REVIS

Re: [OpenWrt-Devel] [PATCH v2] build: add mkrasimage

|| * 0010 > make that RAS_VERSION := "V1.99(OWRT.$(patsubst r%,%,$(REVISION)))C0" > to avoid spawning a shell + sed process. I'll have a look at improving this tonight, thanks. Regards Stefan Lippers-Hollmann _

Re: [OpenWrt-Devel] [PATCH v2] build: add mkrasimage

On 2018-08-21, Stefan Lippers-Hollmann wrote: > Hi > > On 2018-08-21, Stefan Lippers-Hollmann wrote: > > On 2018-08-20, David Bauer wrote: > [...] > > For now, I've supplied a valid/ future firmware version for testing > > > > RAS_VERSION := "V1.00

Re: [OpenWrt-Devel] [PATCH v2] build: add mkrasimage

Hi On 2018-08-21, Stefan Lippers-Hollmann wrote: > On 2018-08-20, David Bauer wrote: [...] > For now, I've supplied a valid/ future firmware version for testing > > RAS_VERSION := "V1.00(ABCS.9)C0" While perhaps not ideal yet, this is accepted by the OEM webinterface

Re: [OpenWrt-Devel] [PATCH v2] build: add mkrasimage

images for all devices > it is added to. > > Signed-off-by: David Bauer with the caveat explained below: Tested-by: Stefan Lippers-Hollmann > v2 changes: > - Rework image-generation code > - Add factory image for NBG6616 > - Add factory image for NBG6817 Thanks a lot

Re: [OpenWrt-Devel] [PATCH] build: add mkrasimage

y image for the NBG6817 by using make-ras is on my radar, but as that router is in use as my main router with a rather complex vlan and 4addr setup, it might take a while until I find an opportunity to look into it. Regards Stefan Lippers-Hollmann

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v2] ipq806x: add kernel 4.14 support

ion, I'm not formally filing this branch as a pull request. Regards Stefan Lippers-Hollmann pgp6FW4NvIpCz.pgp Description: Digitale Signatur von OpenPGP ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.infradead.org/mailman/listinfo/openwrt-devel

Re: [LEDE-DEV] [PATCH v2] ipq806x: add kernel 4.14 support

smooth sysupgrade, no patches or other changes needed tested by: Stefan Lippers-Hollmann Message-ID: <20180504214003.61bbd2be@mir> I've been running my nbg6817 successfully on kernel 4.14 for a bit over two weeks now, no issues at all. It is still possible to drop the kernel size to

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v2 2/4] base-files: add sysupgrade -u to skip unchanged files

ut only effective for files touched > but not modified. [...] This patch series works very nicely for me on ar71xx, brcm47xx, ipq806x and lantiq, -u unclutters the overlay contents quite significantly and makes spotting (manual) changes a lot easier.

Re: [OpenWrt-Devel] [openwrt-realtek] Is it possible to add support for rtl8676?

ire you personally (as I can't really imagine (m)any others to share your motivation) to spend massive efforts on upstream kernel- and toolchain support, before even thinking about OpenWrt specifics. Regards Stefan Lippers-Hollmann [1] lexra as an architecture used by

[OpenWrt-Devel] [PATCH trunk/r47894] hostapd: fix post v2.4 security issues

-off-by: Stefan Lippers-Hollmann --- I have kept the upstream patches as untouched as possible (except for the necessary backporting), so this introduces trailing whitespace in several places. ...Fix-HTTP-chunked-transfer-encoding-parser.patch | 49 +++ ...r-Fix-payload-length

Re: [OpenWrt-Devel] Recommended settings ip6 DNS server / dnsmasq

venient for me; I make quite heavy use of local (forward- and reverse) local DNS entries for physical and virtual systems. > and it does not work. The assigned address is still > 2a01:e35:87d8:::953 Most likely because you didn't restart odhcpd - or eventually because you spli

Re: [OpenWrt-Devel] OpenWRT IPv6 firewall

n an ISP-like position, you certainly need to provide unfiltered access to your clients, but CPE devices (which OpenWrt certainly is) better error on the side of caution and provide the ingrained expectation of having a secure local net. Regards Stefan Lippers-Hollmann

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

N (APL) is particularly bad --> empty list (the official TP-Link vendor firmware allows this after selecting germany[1]). - to make sure that transmitted IEEE 802.11d country IEs don't create even more havoc. Regards Stefan Lippers-Hollmann [1] http://www.tp-lin

Re: [OpenWrt-Devel] support for TP-Link TL-WDR3500. Was: Re: [RFC] ar71xx: add support for the TP-Link TL-WDR4310 v1.0

Hi On Saturday 22 December 2012, Stefan Lippers-Hollmann wrote: > On Thursday 20 December 2012, Nicolás Echániz wrote: > > TP-Link WDR3600 is supported since r33219. It has the same hardware as > > the WDR4300 with one less chain/antenna. > > > > However the model W

Re: [OpenWrt-Devel] support for TP-Link TL-WDR3500. Was: Re: [RFC] ar71xx: add support for the TP-Link TL-WDR4310 v1.0

ould at least have a serial console prepared (and once you considering this, do check the original bootlog and make high resolution pictures of the PCB before trying your luck) - as you would need it to recover from a bricked device. Regards Stefan Lippers-Hollmann

[OpenWrt-Devel] [RFC] ar71xx: add support for the TP-Link TL-WDR4310 v1.0

| Signed-off-by: Stefan Lippers-Hollmann Cc: Gabor Juhos --- UNTESTED, please don't apply until anyone with TL-WDR4310 hardware can confirm this to be functional. Update: According to http://wiki.openwrt.org/toh/tp-link/tl-wdr4310, these changes seem to be sufficient. linux/ar71xx/base-