aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* layerscape: fix ls1046ardb 32-bit call traceYangbo Lu2017-11-102-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enabled CONFIG_ARCH_DMA_ADDR_T_64BIT in kernel to resolve below call trace when ls1046ardb 32-bit started up kernel. [ 0.142141] Bman ver:0a02,02,01 [ 0.145326] ------------[ cut here ]------------ [ 0.149969] WARNING: CPU: 0 PID: 1 at arch/arm/mm/ioremap.c:303 __arm_ioremap_pfn_caller+0x1ac/0x1d8 [ 0.159152] Modules linked in: [ 0.162216] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.51-g9c76e024 #2 [ 0.169036] Hardware name: Generic DT based system [ 0.173853] [<c02236a4>] (unwind_backtrace) from [<c021ed94>] (show_stack+0x10/0x14) [ 0.181638] [<c021ed94>] (show_stack) from [<c04d2d38>] (dump_stack+0x98/0xac) [ 0.188899] [<c04d2d38>] (dump_stack) from [<c0245bcc>] (__warn+0xe4/0x100) [ 0.195896] [<c0245bcc>] (__warn) from [<c0245c98>] (warn_slowpath_null+0x20/0x28) [ 0.203504] [<c0245c98>] (warn_slowpath_null) from [<c0229e24>] (__arm_ioremap_pfn_caller+0x1ac/0x1d8) [ 0.212861] [<c0229e24>] (__arm_ioremap_pfn_caller) from [<c0229f0c>] (ioremap_cache+0x20/0x28) [ 0.221608] [<c0229f0c>] (ioremap_cache) from [<c105e390>] (parse_mem_property.part.3+0x18/0x50) [ 0.230441] [<c105e390>] (parse_mem_property.part.3) from [<c105e6dc>] (qman_init_early+0x314/0x334) [ 0.239623] [<c105e6dc>] (qman_init_early) from [<c0201a24>] (do_one_initcall+0xb4/0x168) [ 0.247844] [<c0201a24>] (do_one_initcall) from [<c1000e84>] (kernel_init_freeable+0x1d8/0x280) [ 0.256590] [<c1000e84>] (kernel_init_freeable) from [<c0adbcfc>] (kernel_init+0x8/0x114) [ 0.264812] [<c0adbcfc>] (kernel_init) from [<c021bb28>] (ret_from_fork+0x14/0x2c) [ 0.272423] ---[ end trace 39aaeef329e2a0a2 ]--- [ 0.277058] qman-fqd addr 0xfb000000 size 0x800000 Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update config-4.9Yangbo Lu2017-11-102-4/+12
| | | | | | | | Some new options were introduced by kernel patches. And some options should be removed/added. The config-4.9 should be updated accordingly. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update kernel patchesYangbo Lu2017-11-1013-1411/+14969
| | | | | | | Updated kernel patches to align layerscape kernel with latest LSDK linux (LSDK-17.09-update-103017-V4.9 tag). Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: support all-in-one firmware for ls1088ardb/ls2088ardbYangbo Lu2017-11-101-8/+32
| | | | | | | Suppport all-in-one firmware for ls1088ardb/ls2088ardb by integrating u-boot/rcw/mc/dpl/restool. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: remove default profileYangbo Lu2017-11-102-36/+0
| | | | | | | | | | Default profile had to enable many packages for all devices support. This made these packages still enabled when built for single device. This patch is to remove default profile. For multiple devices build, it's proper to build with multiple devices profile. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: clean up kernel patchesYangbo Lu2017-11-108-538/+538
| | | | | | | | | | | | | | | A previous patch disaggregated kernel patch 601 intending to reverse the ndo_get_stats64 change, but it also dropped many other changes without a reason. This caused build issue for layerscape. This patch is to fix that with below steps. 1. Reversed patch "1c4415a layerscape: reverse changes to ndo_get_stats64", but kept kernel patch 701 which was a proper fix. 2. Reversed the ndo_get_stats64 change in kernel patch 601. 3. Renamed patch 601 (net patch) to 202 (core-linux patch). Maybe it's more proper. Fixes: 1c4415a679f9 ("layerscape: reverse changes to ndo_get_stats64") Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* brcm47xx: fix switch port mapping on Asus RT-N16Tim Thorpe2017-11-101-1/+1
| | | | | | | On the Asus RT-N16, the ports are not mapped the in the same way as the RT-N12. It is, however, the same as the Linksys E3000v1. Signed-off-by: Tim Thorpe <timfthorpe@gmail.com>
* ar71xx: fix regression in 74x164 initialization with 4.9Felix Fietkau2017-11-101-10/+12
| | | | | | | | | The memcpy of the init data relies on chip->registers to be initialized, which only happens later in the code. Move this initialization further down to make it work. This was breaking PCIe/USB on some MikroTik RouterBoard devices. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: add missing macaddr retrieval for Netgear DGN3500Daniel Gimpelevich2017-11-081-0/+2
| | | | | | | The MAC addresses were not being set for LAN and WAN. This will now use the same MAC mechanism as the rest of the target. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* ramips: add support for TP-Link TL-WR840N v5Robert Marko2017-11-086-1/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link TL-WR840N v5 is simple N300 router with 5-port FE switch and non-detachable antennas, based on MediaTek MT7628NN (aka MT7628N) WiSoC. Specification: - MT7628N/N (580 MHz) - 64 MB of RAM (DDR2) - 4 MB of FLASH - 2T2R 2.4 GHz - 5x 10/100 Mbps Ethernet - 2x external, non-detachable antennas - UART (J1) header on PCB (115200 8n1) - 1x LED (GPIO-controlled), 1x button * LED in TL-WR840N v5 is a dual-color, dual-leads type which isn't (fully) supported by gpio-leds driver. This type of LED requires both GPIOs state change at the same time to select color or turn it off. For now, we support/use only the green part of the LED. Orange LED is registered so you can later use it for your own purposes. Flash instruction: Unlike TL-WR840N v4 flashing through WEB UI works in v5. 1. Download lede-ramips-mt76x8-tl-wr840n-v5-squashfs-sysupgrade.bin image. 2. Go to 192.168.0.1 3. Flash the sysupgrade image through Firmware upgrade section of WEB UI. 4. Wait until green LED stops flashing and use the router. Notes: TFTP recovery is broken since TP-Link reused bootloader code for v4 and that does not take into account only 4 MB of flash and bricks the device. So do not use TFTP Recovery or you will have to rewrite SPI flash. They fixed it in later GPL code,but it is unknown which version of bootloader you have. After manually compiling and flashing bootloader from GPL sources TFTP recovery works properly. Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: make mtdsplit-tplink.c honor rootfs offsetThibaut VARÈNE2017-11-081-6/+6
| | | | | | | | | | | | | | | | | | | | The splitter ignored the rootfs offset from the header, probably because until c1e6e61 it was invalid. This patch fixes the splitter to use the now correct header data. Regarding target/linux/ar71xx/files/drivers/mtd/tplinkpart.c, this particular splitter "falls back" to the correct rootfs offset reading and as such it doesn't need to be updated, although it will report a kernel partition length that can be larger than the actual length as it assumes that partition fills the entire segment up to the rootfs partition. Tested-by: Mathias Kresin <dev@kresin.me> Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Tested-by: Daniel Engberg <daniel.engberg.lists@pyret.net> Tested-by: Henryk Heisig <hyniu@o2.pl> Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* sunxi: add Orange Pi 2 supportZoltan HERPAI2017-11-061-0/+9
| | | | | | | | | | | | | - H3 @ 1.3 GHz - 1GiB DDR3 - 10/100Mbps Ethernet - Realtek RTL8189ETV wifi - 4 USB 2.0 Difference to the "Orange Pi Plus" is the lack of Gbit ethernet and lack of onboard flash. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* ag71xx: Switch from driver to kernel macro for NAPI_WEIGHT.Rosen Penev2017-11-063-7/+6
| | | | | | NAPI_POLL_WEIGHT was introduced in the kernel for exactly this purpose 5 years ago. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ixp4xx: drop the jumbo frame supportSergey Ryazanov2017-11-061-80/+0
| | | | | | | | | | | | | | | 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 <nerijus@users.sourceforge.net> Tested-by: Nerijus Baliunas <nerijus@users.sourceforge.net> Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* ixp4xx: fix non-standard phy supportSergey Ryazanov2017-11-061-3/+25
| | | | | | | | | | | | | | | | | 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 <nerijus@users.sourceforge.net> Tested-by: Nerijus Baliunas <nerijus@users.sourceforge.net> Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* sunxi: Added profile for HAOYU Electronics Marsboard A10Kayo Phoenix2017-11-061-0/+10
| | | | | | | | | The MarsBoard was a short-lived credit-card sized, extendable board with an Allwinner A10 SoC. http://linux-sunxi.org/MarsBoard_A10 Signed-off-by: Kayo Phoenix <kayo@illumium.org> [Forward-ported to new target layout:] Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* ar71xx: only use SPI NOR 4K sectors on smaller flash chips for mikrotik devicesFelix Fietkau2017-11-061-1/+0
| | | | | | | | On NOR based Mikrotik devices, 4K sectors significantly slow down firmware flashing and jffs2 usage. On NAND based devices they may be necessary to run rbcfg (the boot loader config is often on SPI NOR). Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: add support for limiting 4K erase sector support based on flash chip ↵Felix Fietkau2017-11-069-0/+64
| | | | | | | | | | | | | | | | size Some targets need 4K sectors for small flash chips (e.g. some routerboards, where the entire chip is just one "erase block"), whereas on other devices 4K sectors lead to horrible flash erase/write performance. Set the default limit in the generic kernel configuration to 4 MiB to ensure that all new platforms don't use 4K sectors for bigger flash chips. On all existing targets use 16 MiB for now to avoid regressions. They will be changed individually in follow-up commits. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ip806x: nbg6817: sysupgrade support both targets for kernel/ rootfs partitionsStefan Lippers-Hollmann2017-10-291-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With this commit and the previous "nbg6817: don't hardcode the rootfs location by using append-rootblock instead" applied, it is possible to boot- and sysupgrade from both dual-boot sets (the primary mmcblk0p4+mmcblk0p5 or the alternative mmcblk0p7+mmcblk0p8). However the sysupgrade support does not toggle between both dual-boot sets between firmware upgrades so far. The partition map of the eMMC used in the nbg6817 is: Found valid GPT with protective MBR; using GPT. Disk /dev/mmcblk0: 7471104 sectors, 3.6 GiB Logical sector size: 512 bytes Disk identifier (GUID): XXX Partition table holds up to 12 entries First usable sector is 34, last usable sector is 7471070 Partitions will be aligned on 2-sector boundaries Total free space is 1 sectors (512 bytes) Number Start (sector) End (sector) Size Code Name 1 34 8225 4.0 MiB FFFF rootfs_data 2 8226 16417 4.0 MiB FFFF romd 3 16418 18465 1024.0 KiB FFFF header 4 18466 26657 4.0 MiB FFFF kernel 5 26658 157729 64.0 MiB FFFF rootfs 6 157730 159777 1024.0 KiB FFFF header_1 7 159778 167969 4.0 MiB FFFF kernel_1 8 167970 299041 64.0 MiB FFFF rootfs_1 9 299042 823329 256.0 MiB FFFF bu1 10 823330 7471069 3.2 GiB FFFF bu2 rootfs_data is the ext4 formatted overlay of the OEM firmware, LEDE ignores it due to its (too) small size. romd/ bu1 are initialized with zeroes (0x00) and unused. bu2 is formatted with ext4 and used for streamboost and other optional functionality by the OEM firmware, it is reformatted during factory resets of the OEM firmware. header/ header_1 contains version information for the corresponding vendor firmwares installed to kernel/rootfs or kernel_1/ rootfs_1, the format hasn't been completely reverse engineered so far and remains left untouched by LEDE: V1.00(ABCS.2)C0: 00000000 00 00 a7 74 01 32 f0 00 56 31 2e 30 30 28 41 42 |...t.2..V1.00(AB| 00000010 43 53 2e 32 29 43 30 00 ff ff ff ff ff ff ff ff |CS.2)C0.........| 00000020 ff ff ff ff ff ff ff ff 00 00 d5 dc 4e 42 47 36 |............NBG6| 00000030 38 31 37 00 ff ff ff ff ff ff ff ff ff ff ff ff |817.............| 00000040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00000060 ff ff ff ff ff ff ff ff ff ff ff ff 00 00 22 a3 |..............".| 00000070 00 1c 70 00 ff ff ff ff ff ff ff ff ff ff ff ff |..p.............| 00000080 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00000800 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00100000 V1.00(ABCS.5)C0: 00000000 00 00 bf 94 01 46 d8 00 56 31 2e 30 30 28 41 42 |.....F..V1.00(AB| 00000010 43 53 2e 35 29 43 30 00 ff ff ff ff ff ff ff ff |CS.5)C0.........| 00000020 ff ff ff ff ff ff ff ff 00 00 d6 5a 4e 42 47 36 |...........ZNBG6| 00000030 38 31 37 00 ff ff ff ff ff ff ff ff ff ff ff ff |817.............| 00000040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00000060 ff ff ff ff ff ff ff ff ff ff ff ff 00 00 c0 2c |...............,| 00000070 00 1c 58 00 ff ff ff ff ff ff ff ff ff ff ff ff |..X.............| 00000080 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00010000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00100000 Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ip806x: nbg6817: don't hardcode the rootfs location by using ↵Stefan Lippers-Hollmann2017-10-291-1/+2
| | | | | | | | | | | | | | | | | | | append-rootblock instead This changes the cmdline from: Kernel command line: root=/dev/mmcblk0p5 rootfstype=squashfs,ext4 rootwait noinitrd Bootloader command line (ignored): board=NBG6817 root=/dev/mmcblk0p5 rootwait zld_ver=2.04 console=ttyHSL1,115200n8 mtdparts=m25p80:0xC0000(SBL)ro,0x40000(TZ)ro,0x40000(RPM)ro,0x80000(u-boot)ro,0x10000(env)ro,0x10000(ART)ro,0x10000(dualflag),0x210000(reserved) to Kernel command line: rootfstype=squashfs,ext4 rootwait noinitrd root=/dev/mmcblk0p5 Bootloader command line (ignored): board=NBG6817 root=/dev/mmcblk0p5 rootwait zld_ver=2.04 console=ttyHSL1,115200n8 mtdparts=m25p80:0xC0000(SBL)ro,0x40000(TZ)ro,0x40000(RPM)ro,0x80000(u-boot)ro,0x10000(env)ro,0x10000(ART)ro,0x10000(dualflag),0x210000(reserved) As a consequence booting from the alternative dual-boot partition set (root=/dev/mmcblk0p8) becomes possible. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: ipq4019: add ap-dk01.1-c1 board supportRoman Yeryomin2017-10-305-1/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | AP-DK01.1-C1 is QCA dev board with: - ipq4018 quad core ARM @716.8MHz, 2x2 dual (11n+11ac) radio - 256MB RAM - 32MB SPI flash - QCA8075 multiport ethernet phy (WAN port, 4x LAN ports) First installation via u-boot: sf probe sf erase 0x180000 0x1a00000 tftpboot 0x84000000 lede-ipq806x-AP-DK01.1-C1-squashfs-sysupgrade.bin sf write 0x84000000 0x180000 $filesize Further upgrades via sysupgrade. Changes: - add partitions - set memory size to 256MB - add reserved memory mapping - add correct compatible string - add image generation - extract pre-cal data from ART partition Compile and run tested. Wirespeed NAT can be achieved with spreading rx interrupts over different cores. Wifi speed is ~550Mbps @5GHz in open air. Note: AP-DK01.1-C1 is fully compatible with AP-DK01.2-C1, which has ipq4028 instead of ipq4018 on board. Changes since v2: - based on dts(i) rework/cleanup submitted: http://lists.infradead.org/pipermail/lede-dev/2017-October/009596.html - precise reserved memory mapping - more precise description - compatible string Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ipq806x: ipq4019: dts: fix maximum cpu speedRoman Yeryomin2017-10-302-9/+13
| | | | | | | | Supported frequencies of all ipq40xx chips are 48, 200, 500 and 716.8 MHz. Previous 666MHz setting was most likely related to instability of early chips/boards made before mass production. Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ipq806x: ipq4019: dts: remove spi chip node from ap-dk01 dtsiRoman Yeryomin2017-10-304-20/+17
| | | | | | All ap-dk01 boards have different spi chips, thus no point in keeping it in dtsi. Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ipq806x: ipq4019: dts: move ap-dk01 networking entries to dtsiRoman Yeryomin2017-10-304-70/+32
| | | | | | That is mdio/ethernet and wifi are present on all ap-dk01 boards. Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ipq806x: ipq4019: dts: remove counter entry from ap-dk01 boardsRoman Yeryomin2017-10-303-15/+0
| | | | | | There is no code implementing "qcom,qca-gcnt", so no point in keeping it. Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ipq806x: ipq4019: dts: move ap-dk01 tcsr nodes to dtsiRoman Yeryomin2017-10-304-85/+42
| | | | | | tcsr configuration is the same for all ap-dk01 boards Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ipq806x: ipq4019: dts: remove crypto nodes from board dtsRoman Yeryomin2017-10-303-24/+0
| | | | | | | | | crypto and cryptobam are already present in dtsi used by these boards: - fritz4040 - nbg6617 - rt-ac58u Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ipq806x: ipq4019: dts: move xo and timer nodes to SoC dtsiRoman Yeryomin2017-10-302-0/+105
| | | | | | xo and timer are common thing and it makes more sense to keep them in SoC dtsi Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ipq806x: ipq4019: dts: fix pinctrl node nameRoman Yeryomin2017-10-303-1/+56
| | | | Signed-off-by: Roman Yeryomin <roman@advem.lv>
* mt7620: image.mk: make elecom-header reproducibleAlexander Couzens2017-11-061-1/+3
| | | | | | | | | elecom-header adds a timestamp dependency. Replace the timestamps with SOURCE_DATE_EPOCH [0] variable. [0] https://reproducible-builds.org/specs/source-date-epoch/ Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* ar71xx: fix section mismatch in TP-Link Archer C7 v4 supportFelix Fietkau2017-11-051-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: fix flash fast read on devices using multiple flash chipsFelix Fietkau2017-11-051-5/+11
| | | | | | | Add a callback to allow the SPI driver to indicate which devices fast flash read works on. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* 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>
* ar71xx: wzr-hp-ag300h: drop unused wmac led_pin settingsMathias Kresin2017-11-031-3/+0
| | | | | | | | | The GPIOs are used for defined LEDs and therefore are ignored/unset in the ath9k driver since 192f0a3db859. The wireless led led trigger is added in userspace since e20965811db6, which makes the ap9x_pci_setup_wmac_led_pin() superfluous. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: mach-rbspi: fix 74x164 supportThibaut VARENE2017-11-031-0/+1
| | | | | | | | | | | | | The platform data was missing the num_registers element which is now mandatory in linux 4.9 Without this patch, the gpio probing would fail with: gpio gpiochip1: (74x164): tried to insert a GPIO chip with zero lines Fixes: #1106 Tested-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
* 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: add support for switching between 3-byte and 4-byte addressing on ↵Felix Fietkau2017-11-022-9/+224
| | | | | | | | | | | | | | | w25q256 flash On some devices the flash chip needs to be in 3-byte addressing mode during reboot, otherwise the boot loader will fail to start. This mode however does not allow regular reads/writes onto the upper 16M half. W25Q256 has separate read commands for reading from >16M, however it does not have any separate write commands. This patch changes the code to leave the chip in 3-byte mode most of the time and only switch during erase/write cycles that go to >16M addresses. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar7: add kernel 4.9 supportJonas Gorski2017-10-2915-0/+1067
| | | | | | Compile and run tested on WAG354Gv1. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* ar7: drop unused 4.1 supportJonas Gorski2017-10-2914-995/+0
| | | | | | Kernel 4.1 isn't support anymore anyway. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* ar7: unbreak serial consoleJonas Gorski2017-10-293-33/+53
| | | | | | | | | Serial output was broken since 3.16 for shared uarts between kernel and login. Fix this by adding a fix sent upstream. While at it, drop a useless patch that adds duplicate code. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* ar7: remove gpio character deviceJonas Gorski2017-10-295-216/+0
| | | | | | | There are no obvious users, and any out of tree users should convert to one of the generic APIs. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* layerscape: reverse changes to ndo_get_stats64Mathew McBride2017-10-299-2365/+650
| | | | | | | | | | | | The NXP LSDK kernel backported changes for interface ndo_get_stats64 functions from mainline, this causes a compile error with backports/mac80211, which expects the original 4.9 defintion. As reversing the ndo_get_stats64 change signifcantly reduces the size of patch 601, the patches that were aggregated into it have been disaggregated. Signed-off-by: Mathew McBride <matt@traverse.com.au>
* layerscape: Remove netfilter and LZ4 config symbolsMathew McBride2017-10-292-164/+0
| | | | | | | | These conflict with the kmod packages (such as nf-netlink) Signed-off-by: Mathew McBride <matt@traverse.com.au> [Add same changes for arm8_32b subtarget and refresh config] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* arc770: mark as source-onlyHans Dedecker2017-10-281-1/+1
| | | | | | | | | Mark target arc770 as source-only as it has package compile issues (e.g. iproute2) due to the usage of uClibc. As a prerequisite to be included in future releases the arc770 target needs to switch either to glibc or musl. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* 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>
* kernel: enable CONFIG_ADVISE_SYSCALLSRosen Penev2017-10-271-1/+1
| | | | | | | Without this, posix_[fm]advise does not work. This causes issues with btrfs-progs, which uses fadvise to drop caches. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ar71xx: fix board.bin used by QCA9886 in Archer C58/C59/C60Henryk Heisig2017-10-271-0/+2
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* ar71xx: Archer C58/C59/C60 fix qca9886 wireless interfaceHenryk Heisig2017-10-263-7/+9
| | | | | | | This commit fix 5GHz wireless interface used in Archer C58/C59/C60v1 and set correctly MAC address on this interface. Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* treewide: do not use IMG_PREFIX in Image/PrepareJonas Gorski2017-10-263-12/+12
| | | | | | | | | | | | | | IMG_PREFIX can be modified in ImageBuilder by passing EXTRA_IMAGE_NAME on command line, but Image/Prepare is not run in ImageBuilder. This causes missing files when IMG_PREFIX is used for target file names in Image/Prepare, then as source file names in Image/BuildKernel or Image/Build. Fix this by using a fixed output file name in Image/Prepare, and copy to the expected file name in Image/BuildKernel instead, which is run by ImageBuilder. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 11:05:15 +0000