aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ar71xx: /lib/ar71xx.sh: add model detection for TP-Link TL-WR810NMatthias Schiffer2018-02-031-0/+3
| | | | | | Properly report the revision in /tmp/sysinfo/model. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* kernel: bump 4.4 to 4.4.112 for 17.01Kevin Darbyshire-Bryant2018-01-2212-165/+19
| | | | | | | | | | | | | | | | | | | | | | Refresh patches. Remove upstreamed patches: target/linux/generic/patches-4.4/030-2-smsc75xx-use-skb_cow_head-to-deal-with-cloned-skbs.patch target/linux/generic/patches-4.4/030-3-cx82310_eth-use-skb_cow_head-to-deal-with-cloned-skb.patch target/linux/generic/patches-4.4/030-4-sr9700-use-skb_cow_head-to-deal-with-cloned-skbs.patch target/linux/generic/patches-4.4/030-5-lan78xx-use-skb_cow_head-to-deal-with-cloned-skbs.patch CVEs completely or partially addressed: CVE-2017-5715 CVE-2017-5753 CVE-2017-17741 CVE-2017-1000410 Compile-tested: ar71xx Archer C7 v2 Run-tested: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: bump 4.4 to 4.4.111 for 17.01Kevin Darbyshire-Bryant2018-01-172-3/+3
| | | | | | | | Refresh patches Tested-on: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ar71xx: Netgear WNR2000v4: do not include USB packages [17.01]Stijn Segers2018-01-131-1/+0
| | | | | | | | | The Netgear WNR2000v4 does not have a USB port. Hence, including USB packages into the default images is useless. It looks like the WNR2000v4 definition in master is OK. v2 fixes the silly typo in the patch title (WNR2000v4 instead of WNR200v4) Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* ramips: fix lenovo newifi-y1 switch and LED configChuanhong Guo2018-01-092-3/+5
| | | | | | | | | | | | | | There are 3 ethernet ports on Y1. LAN1 on port1, LAN2 on port0 and WAN on port4. Use a standalone switch configuration to match this and use the switch trigger so that LAN LED could indicate the connetction status for both lan ports correctly. This patch also drop the internet led configuration, because there is a WAN led for port4 and eth0.2 isn't always used as WAN. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: firewrt: indicate boot status via LEDMathias Kresin2018-01-091-0/+1
| | | | | | | Add the Firefly FireWRT gree power LED to diag.sh to indicate the boot status via the power LED. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ag71xx: Fix rx ring buffer stall on small packets flood on qca956x and qca953x.Vittorio Gambaletta2018-01-093-1/+22
| | | | | | Backported from Code Aurora QSDK Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
* ar71xx: QCA956X: add missing registerHenryk Heisig2018-01-096-4/+66
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* mvebu: fix mvneta build with Linux 4.4.110Jo-Philipp Wich2018-01-089-54/+65
| | | | | | | | | | | | | | | | | | | | | | | | Kernel 4.4.109 added pp->link, pp->duplex and pp->speed setters to mvneta_port_disable() which the mvneta patchset failed to patch out after rebasing, leading to the following build error: CC drivers/net/ethernet/marvell/mvneta.o drivers/net/ethernet/marvell/mvneta.c: In function 'mvneta_port_disable': drivers/net/ethernet/marvell/mvneta.c:1199:4: error: 'struct mvneta_port' has no member named 'link' pp->link = 0; ^ drivers/net/ethernet/marvell/mvneta.c:1200:4: error: 'struct mvneta_port' has no member named 'duplex' pp->duplex = -1; ^ drivers/net/ethernet/marvell/mvneta.c:1201:4: error: 'struct mvneta_port' has no member named 'speed' pp->speed = 0; ^ Fix the issue by rebasing 134-net-mvneta-convert-to-phylink.patch to remove these struct member accesses as well. Fixes: 7f5a040359 ("kernel: update kernel 4.4 to version 4.4.110") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: update kernel 4.4 to version 4.4.110Hauke Mehrtens2018-01-0736-146/+147
| | | | | | This fixes: CVE-2017-5754 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm47xx: relocate the stack in loaderHauke Mehrtens2018-01-062-2/+4
| | | | | | | | | | | By default we are reusing the stack provided by CFE, like it is intended by CFE. On my WRT54GS it is located at 0x8043BF30, so a big kernel image could overwrite it. Relocate it to a different memory region which is still under the 8MB RAM, but in the higher area. We only need this memory region for the stack of the loader, Linux will set up this for its own. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm47xx: relocate loader to higher addressHauke Mehrtens2018-01-061-1/+1
| | | | | | | | | | | | | | | | | | | | | The boot process on a WRT54GL works the following way: 1. CFE gets loaded by the boot rom from flash 2. CFE loads the loader from the flash and gzip uncompresses it 3. CFE starts the loader 4. The loader stores the FW arguments and relocates itself to BZ_TEXT_START (now 0x80600000) 5. The loader reads the Linux image from flash 6. The loader lzma decompresses the Linux image to LOADADDR (0x80001000) 7. The loader executes the uncompress Linux image at LOADADDR The BZ_TEXT_START was set to 0x80400000 before. When the kernel gets uncompressed and is bigger than BZ_TEXT_START - LOADADDR it overwrote the loader which was currently uncompressing it and made the board crash. Increase the BZ_TEXT_START my 2 MB to have more space for the kernel. Even on 16MB RAM devices the memory goes till 0x80FFFFFF so this should not be a problem. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm47xx: image: build firmware for Asus WL-500g DeluxeRafał Miłecki2018-01-021-0/+8
| | | | | | | | It's a device based on BCM5365P (0x5365 package 0x00). This SoC has USB 1.1 controller but device has two USB 2.0 parts. They are handled by PCI-based controllers: 1106:3038 UHCI and 1106:3104 EHCI. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: bump 4.4 to 4.4.108 for 17.01Kevin Darbyshire-Bryant2017-12-302-3/+3
| | | | | | Refresh patches. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ramips: fix widora neo diag ledMathias Kresin2017-12-291-2/+4
| | | | | | | The diag LED is named widora:orange:wifi and can't be derived from the boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: bump 4.4 to 4.4.107Etienne Haarsma2017-12-2324-82/+82
| | | | | | | | | | | | | Bump 4.4 to 4.4.107 and refreshed all patches. Made the following patch for Mediatek and Oxnas compatible with kernel 4.4.107: 0072-mtd-backport-v4.7-0day-patches-from-Boris.patch Compile-tested: ar71xx Run-tested: ar71xx Signed-off-by: Etienne Haarsma <bladeoner112@gmail.com> Reviewed-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Tested-by: Rosen Penev <rosenp@gmail.com>
* brcm47xx: remove target specific network preinit configJo-Philipp Wich2017-12-132-32/+0
| | | | | | | | | | The generic preinit code is now able to setup network and switch vlan settings from the /etc/board.json file, therefor drop the target specific code. Fixes FS#790. Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit 833c500cb2985e9b76a1aae3b6a577977eee5457)
* ar71xx: fix switch port numbering on RB750r2 and RB750UPr2João Chaínho2017-12-131-0/+6
| | | | | | | | This patch fixes the switch port numbering on Mikrotik RB750r2 (hEX lite) and RB750UPr2 (hEX PoE lite). Tested on a RB750UPr2. Maybe this patch is applicable to other devices (e.g. RB951Ui-2nD, RB952Ui-5ac2nD) but I have no way to test them. Signed-off-by: João Chaínho <joaochainho@gmail.com> (cherry picked from commit 61027e343025b5f47e7e79db71576e6bd5e97c1d)
* rb532: enable high-res timers, refresh kernel configFelix Fietkau2017-12-131-2/+1
| | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry picked from commit 2dc23a7576614181e35a0bf6444fc55144dd711b)
* xburst: enable high-res timers, refresh kernel configFelix Fietkau2017-12-131-7/+3
| | | | | | | Helps with system performance Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry picked from commit f859a7b696d79fae8dd98859a3451a6f9d77570f)
* kernel: add CONFIG_SCHED_HRTICK=y to the generic configFelix Fietkau2017-12-131-0/+1
| | | | | | | | It is used by pretty much every target Signed-off-by: Felix Fietkau <nbd@nbd.name> (backported from commit b47fd7656336162360ebf66147326763ddae3f8d) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ip17xx: correct aneg_done return valueSergey Ryazanov2017-12-131-1/+1
| | | | | | | | | | PHY core treats any positive return value as the auto-negotiation done indication. Since we do not actually check any device register in this callback then update it to return positive value with a neutral meaning instead of the register flag to avoid confusing for future readers. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 2cc61e6e8e951b1480a024fdb66bc539aa163bbc)
* mvswitch: fix autonegotiation issueSergey Ryazanov2017-12-131-0/+7
| | | | | | | | | | | | | | | | The Marvel 88E6060 switch has an MDIO interface, but does not emulate regular PHY behavior for the host. The network core can not detect using the generic code, whether the connection via the attached PHY can be used or not. The PHY's state machine is stuck in a state of auto-negotiation and does not go any further so the Ethernet interface of the router stay forever in the not-runing state. Fix this issue by implementing the aneg_done callback to be able to inform the network core that the Ethernet interface link to which the switch is connected can be marked as RUNNING. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 913b2290caad437bb523d6f1ee5a70707f7f7ef4)
* lantiq: spi: double time out toleranceHauke Mehrtens2017-12-131-0/+37
| | | | | | | | | | | | | | | | | | | | The generic SPI code calculates how long the issued transfer would take and adds 100ms in addition to the timeout as tolerance. On my 500 MHz Lantiq Mips SoC I am getting timeouts from the SPI like this when the system boots up: m25p80 spi32766.4: SPI transfer timed out blk_update_request: I/O error, dev mtdblock3, sector 2 SQUASHFS error: squashfs_read_data failed to read block 0x6e After increasing the tolerance for the timeout to 200ms I haven't seen these SPI transfer time outs any more. The Lantiq SPI driver in use here has an extra work queue in between, which gets triggered when the controller send the last word and the hardware FIFOs used for reading and writing are only 8 words long. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 6153248052b2e067df9596c2d619345261b1d3f7)
* ramips: support jumbo frame on mt7621 up to 2kMichael Lee2017-12-134-17/+32
| | | | | Signed-off-by: Michael Lee <igvtee@gmail.com> (cherry picked from commit eee09bfe01e8cc2db1501f82dde7b9b6bb424faf)
* x86: keep /boot mounted for kexecDaniel Golle2017-12-131-4/+7
| | | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 63571cb56c7ff2692b5c9aa78133c3f4996e2ac5)
* kernel: move initramfs's init script out of base-filesRafał Miłecki2017-12-131-0/+0
| | | | | | | | | Keeping it in base-files was resulting in adding it to the base-files package. This file is meant to be included manually for initramfs images only. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit f6433eede79db4f6276b68e815bb17a9364292c7)
* build: allow specifying flow-control to grub on serial consolePhilip Prindeville2017-12-131-2/+2
| | | | | | | | On the more sophisticated (i.e. deeper FIFO) serial controllers, flow-control might be needed to avoid dropping output. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com> (cherry picked from commit 7fe5963be023fd59a11652ecfb065d3405a91c48)
* ar8327: Add workarounds for AR8337 switch.Vittorio Gambaletta2017-12-132-1/+62
| | | | | | | | | | | | | | | | | RGMII RX delay setting needs to be always specified for AR8337 to avoid port 5 RX hang on high traffic / flood conditions. Also, the HOL registers that set per-port and per-packet-priority buffer sizes are updated with the reduced values suggested by the QCA switch team. Finally, AR8327 reserved register fixups are disabled for the AR8337. This patch is adapted from the Code Aurora QSDK, but with magic values mapped to proper defines. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> (cherry picked from commit 967b6be118e3217e8d6a28df9c615d3255e7b1ae)
* lantiq: remove lantiq_board_model, it is unusedFelix Fietkau2017-12-131-9/+0
| | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry picked from commit fd93f81fd85e964a697a5f550f7f162e3ec1ca05)
* lantiq: remove lantiq_board_name, use the generic function insteadFelix Fietkau2017-12-136-18/+5
| | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry picked from commit 7e798dab56546d6f8e2fe0f913ff41e8f010af51)
* lantiq: move lantiq_board_detect() to 03_preinit_board.shFelix Fietkau2017-12-132-10/+10
| | | | | | | It is only used there Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry picked from commit aa95d6cd20f7e08420562b9747c197c2eac1d2e2)
* x86: image: drop duplicated copy of bzImage into vmlinuzRafał Miłecki2017-12-131-1/+0
| | | | | | | It's already done once few lines earlier in the Image/Build/iso. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 425f958830428f989d7381ddda3a8f503e587c5c)
* x86: image: drop unneeded grub callRafał Miłecki2017-12-131-1/+0
| | | | | | | | It appears there isn't any Image/Build/grub/* define so this step looks redundant. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit f5d403488ed62bb7f0e0017b02890b4d72240a55)
* x86: image: drop unused ROOTDELAY variableRafał Miłecki2017-12-131-2/+0
| | | | | | | | It's unused since commit 742700719303 ("x86: remove the olpc subtarget, it has been unmaintained for a long time"). Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 9a267e6a4b08d1fa2a98523e5eb9f2325c9506e2)
* bcm53xx: suppress osafeloader info error messages during flashingFelix Fietkau2017-12-131-1/+1
| | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry picked from commit 727e244faec8ec8e0004a2b772d1a9424f0c9d5d)
* kernel: remove out of tree direct-io disable hackFelix Fietkau2017-12-137-168/+0
| | | | | | | | | Direct-IO support has to be enabled for the release build anyway, so this hack is not worth keeping Signed-off-by: Felix Fietkau <nbd@nbd.name> (backported from commit 0b7ed65cec8084bb98ae0e2758b7aca6c447cd4b) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: bump 4.4 to 4.4.103 for 17.01Etienne Haarsma2017-12-1211-76/+12
| | | | | | | | | | | | | Refreshed all patches. Removed upstream ramips patches: 0101-MIPS-ralink-Fix-MT7628-pinmux.patch 0102--MIPS-ralink-Fix-typo-in-mt7628-pinmux-function.patch Compile-tested: ar71xx Run-tested: ar71xx Signed-off-by: Etienne Haarsma <bladeoner112@gmail.com>
* ramips: backport MT7628 pinmux fixesMathias Kresin2017-11-274-2/+66
| | | | | | | | | | | | According to the datasheet the REFCLK pin is shared with GPIO#37 and the PERST pin is shared with GPIO#36. While at it fix a typo inside the pinmux setup code. The function is called refclk and not reclk. Update device tree source files accordingly. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add missing reset button for Nexx WT1520INAGAKI Hiroshi2017-11-271-9/+15
| | | | | | | | | | | | | This commit adds missing the GPIO key used as reset button. Nexx WT1520 has a GPIO key for factory reset, but it's not defined in WT1520.dtsi and cannot use it. Drop the UART (full) from the device tree source file, it was never used for this board. Adjust the kernel bootargs accordingly. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> [add note about dropped UART (full) to the commit message] Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: bump 4.4 to 4.4.102Etienne Haarsma2017-11-2626-52/+40
| | | | | | | | | | | | Refreshed all patches. Removed upstream ramips patch: 0063-set-CM_GCR_BASE_CMDEFTGT_MEM-according-to-datasheet.patch Compile-tested: ar71xx Run-tested: ar71xx Signed-off-by: Etienne Haarsma <bladeoner112@gmail.com> Tested-by: Stijn Segers <francesco.borromini@inventati.org>
* ramips: fix Planex CS-QR10 device packagesMathias Kresin2017-11-221-1/+3
| | | | | | | | | Add kmod-sound-core, it is a dependency of kmod-sound-mt7620 and will not be autoselected. Remove kmod-i2c-core, it will be autoselected by kmod-i2c-ralink. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix DCH-M225 supportMathias Kresin2017-11-222-2/+7
| | | | | | | | | | | | | | Setting the pins of the uartf group to gpio+i2s at the time the i2c driver loads is to late for the WPS gpio button. The gpio-keys driver fails to load since the pin used by the WPS button is not yet set to GPIO. The WPS button with the rfkill keycode is essential for this wifi only board. Add the missing sound and i2c kernel modules corresponding to the device nodes. Signed-off-by: Mathias Kresin <dev@kresin.me>
* brcm47xx: fix switch port mapping on D-Link DIR-330Antony Black2017-11-161-0/+1
| | | | | | | | D-Link DIR-330 is clone of ASUS WL500GP2, by default conf the WAN port is eth1, it's not working cus eth1 not soldered and wan port function performs 5th port of the switch. Signed-off-by: Antony Black <gtrtfm@gmail.com>
* brcm47xx: fix switch port mapping on Asus RT-N12 and RT-N16 modelsJo-Philipp Wich2017-11-101-0/+2
| | | | | | | | | | | | | | | | On Asus RT-N12 and RT-N16 models, the WAN and LAN4 ports are swapped in the initial switch configuration since the presets present in nvram appear to be wrong. Add special casing for these models to detect_by_model() in order to ensure a proper switch configuration. Fixes FS#502. (cherry picked from commit 96ed69101da254b0cb61a0dfc42bd48d27bfacb9 and squashed with commit f2fdd68664cdf09075e6f18b20946e41a22284b2) Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: fix LED config for DIR-869 A1Florian Beier2017-11-031-7/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the LED configuration for the D-Link DIR-869 A1. In order to support the device I probed around using an initramfs image for the UniFi AC. Pulling GPIO 15 to low enabled the LEDs while high disabled them. GPIO 16 set to low meant that the color was white while pulling it to high made the color change to orange. The past code was written based upon these findings. However, running a flashed image I now discovered that GPIO 15 controls the orange LEDs while GPIO 16 controls the white ones and that both are active when low. This means that the GPIOs were inverted and one active_low was set wrong which this patch fixes. Behavior of the LED front after this patch is applied: cat /sys/devices/platform/leds-gpio/leds/d-link:white:status/brightness 0 -> white LEDs are OFF 255 -> white LEDs are ON cat /sys/devices/platform/leds-gpio/leds/d-link:orange:status/brightness 0 -> orange LEDs are OFF 255 -> orange LEDs are ON If the brightness of both is set to 255 the LED front will be white. If the brightness of both is set to 0 the LED front will be off. Signed-off-by: Florian Beier <beier.florian@gmail.com>
* ipq806x: nbg6817: sync MAC addresses to the upstream valuesStefan Lippers-Hollmann2017-11-032-2/+5
| | | | | | | | | | | | | | | | | | | | | | The ZyXEL NBG6817 calculates all MAC addresses based on the ethaddr value stored in the U-Boot environment (0:APPSBLENV). No MAC addresses are stored in the ART partition and the generated MAC addresses for the wlan interfaces alternate randomly between 12:34:56:78:90:12 and 00:03:7f:12:34:56. interface new/ OEM MAC old MAC wlan-2.4g (phy1): ethaddr undefined wlan-5g (phy0): ethaddr + 1 undefined lan : ethaddr + 2 ethaddr wan : ethaddr + 3 ethaddr + 1 This patch defines stable MAC addresses for the wlan interfaces for the first time instead of generating them at random. The previously defined values for lan/ wan are changed to follow the settings of the OEM firmware. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: nbg6817: add kmod-fs-ext4 to device packagesStefan Lippers-Hollmann2017-11-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The ZyXEL NBG6817 uses an eMMC flash for the rootfs, which is split into the readonly squashfs and ext4 for the overlay. This adds the required package to the device packages to allow mounting the overlay by default. /dev/root on /rom type squashfs (ro,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,noatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime) /dev/loop0 on /overlay type ext4 (rw,noatime,data=ordered) overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work) tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000) debugfs on /sys/kernel/debug type debugfs (rw,noatime) mountd(pid1040) on /tmp/run/blockd type autofs (rw,relatime,fd=7,pgrp=1,timeout=30,minproto=5,maxproto=5,indirect) Before this commit, the ext4 based overlayfs could not be mounted, which left only the tmpfs based/ volatile emergency overlay in place. Fixes: https://forum.lede-project.org/t/zyxel-nbg6817-flashing-from-oem/768 Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ramips: fix Youku-YK1 supportEdmunt Pienkowsky2017-10-274-5/+6
| | | | | | | | | | | | | | | | | | | | | | Remove the ephy-pins from the ethernet device tree node. The ephy-pins are useed to controll the ePHY LEDs and this board doesn't have these. Instead one of the ePHY pins is used in GPIO mode to control the WAN LED. Use the switch LED trigger to control the WAN LED. Move the power LED handling to diag.sh to show the boot status via this LED. Add the missing kernel packages for USB and microSD card reader to the default package selection. Fix the maximum image size value. The board has a 32MByte flash chip. Fixes: FS#1055 Signed-off-by: Edmunt Pienkowsky <roed@onet.eu> [make the commit message more verbose, remove GPIO pinmux for pins not used as GPIOs] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add missing default lan interfaceMathias Kresin2017-10-251-0/+2
| | | | | | | | | With removing the boards from the the default case to fix the xDSL WAN MAC-Address, the setting for the default LAN interface wasn't added. Fixes: 92a12c434ca3 ("lantiq: fix avm fritz box mac addresses") Signed-off-by: Mathias Kresin <dev@kresin.me>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 09:57:31 +0000