aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* layerscape: use MKUBIFS_OPTS for per-device ubi parametersYangbo Lu2018-12-182-6/+3
| | | | | | | UBIFS_OPTS couldn't be used for per-device ubi parameters. Let's use MKUBIFS_OPTS instead. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: drop kernel 4.9 supportBiwen Li2018-12-1838-275972/+0
| | | | | | | This patch is to drop kernel 4.9 support. Signed-off-by: Biwen Li <biwen.li@nxp.com> Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add LS1021AIOT board supportBiwen Li2018-12-183-2/+307
| | | | | | | | | | | | | | | | | | | | | | | The LS1021A-IoT gateway reference design based on the QorIQ LS1021A processor is a purpose-built, small footprint hardware platform with a wide array of high-speed connectivity and low-speed serial interfaces to support secure delivery of IoT services for home, business or other commercial location. - Combines standards-based, open source software with a feature-rich IoT gateway design to establish a common, open framework for secured IoT service delivery and management. - Provides a wide assortment of high-speed and serial-based connectivity in a compact, highly secure design. - High efficiency through the use of the Arm-based QorIQ LS1021A embedded processor. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Biwen Li <biwen.li@nxp.com>
* layerscape: upgrade kernel to 4.14Biwen Li2018-12-1845-1/+242886
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch is to upgrade kernel to 4.14 for layerscape. patches-4.14 for layerscape included two categories. - NXP Layerscape SDK kernel-4.14 patches All patches on tag LSDK-18.09-V4.14 were ported to OpenWrt kernel. Since there were hundreds patches, we had to make an all-in-one patch for each IP/feature. See below links for LSDK kernel. https://lsdk.github.io/components.html https://source.codeaurora.org/external/qoriq/qoriq-components/linux - Non-LSDK kernel patches Other patches which were not in LSDK were just put in patches-4.14. Kept below patches from patches-4.9. 303-dts-layerscape-add-traverse-ls1043.patch 821-add-esdhc-vsel-to-ls1043.patch 822-rgmii-fixed-link.patch Renamed and rebase them as below in patches-4.14, 303-add-DTS-for-Traverse-LS1043-Boards.patch 712-sdk-dpaa-rgmii-fixed-link.patch 824-mmc-sdhci-of-esdhc-add-voltage-switch-support-for-ls.patch Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Biwen Li <biwen.li@nxp.com>
* kernel: Add missing symbols to 4.19Petr Štetiar2018-12-181-0/+4
| | | | | | | | While building 4.19 for ath79 with CONFIG_ALL_KMODS=y with verbose mode enabled I was asked by kernel config about few symbols/modules so I'm adding those missing symbols to the generic config. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* cns3xxx: fix writing to wrong PCI registersKoen Vandeputte2018-12-183-0/+237
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Originally, cns3xxx used it's own functions for mapping, reading and writing registers. Upstream commit 802b7c06adc7 ("ARM: cns3xxx: Convert PCI to use generic config accessors") removed the internal PCI config write function in favor of the generic one: cns3xxx_pci_write_config() --> pci_generic_config_write() cns3xxx_pci_write_config() expected aligned addresses, being produced by cns3xxx_pci_map_bus() while the generic one pci_generic_config_write() actually expects the real address as both the function and hardware are capable of byte-aligned writes. This currently leads to pci_generic_config_write() writing to the wrong registers on some ocasions. First issue seen due to this: - driver ath9k gets loaded - The driver wants to write value 0xA8 to register PCI_LATENCY_TIMER, located at 0x0D - cns3xxx_pci_map_bus() aligns the address to 0x0C - pci_generic_config_write() effectively writes 0xA8 into register 0x0C (CACHE_LINE_SIZE) This seems to cause some slight instability when certain PCI devices are used. Another issue example caused by this this is the PCI bus numbering, where the primary bus is higher than the secondary, which is impossible. Before: 00:00.0 PCI bridge: Cavium, Inc. Device 3400 (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 255 Bus: primary=02, secondary=01, subordinate=ff, sec-latency=0 After fix: 00:00.0 PCI bridge: Cavium, Inc. Device 3400 (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 255 Bus: primary=00, secondary=01, subordinate=02, sec-latency=0 And very likely some more .. Fix all by omitting the alignment being done in the mapping function. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.89Koen Vandeputte2018-12-1821-164/+132
| | | | | | | | | | | | Refreshed all patches. Remove upstreamed patches: - 096-v4.20-netfilter-ipv6-Preserve-link-scope-traffic-original-.patch Compile-tested on: ar71xx, cns3xxx, imx6 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.146Koen Vandeputte2018-12-184-5/+6
| | | | | | | | | | Refreshed all patches. Compile-tested on: brcm2708 Runtime-tested on: brcm2708 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: bump 3.18 to 3.18.130Koen Vandeputte2018-12-182-15/+15
| | | | | | | | | Refreshed all patches. Compile-tested on: adm5120 Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: replace cameo-factory with existing build commandsMathias Kresin2018-12-171-2/+4
| | | | | | | | Use pad-offset and append-string to create the cameo factory images for the D-LINK DIR-825 C1/DIR-835 A1 factory images. Tested-by: Sebastian Kemper <sebastian_ml@gmx.net> Signed-off-by: Mathias Kresin <dev@kresin.me>
* build: move append-string to image-commands.mkMathias Kresin2018-12-171-4/+0
| | | | | | Move it to image-commands.mk so that it can used by other targets. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: preserve oif of IPv6 link scope packetsHans Dedecker2018-12-1710-11/+107
| | | | | | | | | | | Backort upstream patch which preserves oif of IPv6 link scoped packets. The outgoing interface of IPv6 link scope packets can be changed by the function ip6_route_me_harder. This is unwanted behavior for link local packets and multicast packets as the outgoing interface is fixed and must not be altered as it can break neighbor discovery and multicast listener discovery. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ipq40xx: GL-B1300: convert to new partitions layoutChristian Lamparter2018-12-171-52/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | Alberto Bursi reported: >The patch "ipq40xx: specify "firmware" partition format for GL.iNet GL-B1300" >prevents boot on my B1300. I compiled from latest sources. The GL-B1300 was using the discouraged direct subnodes method to declare the partitions on the flash. |The partition table should be a subnode of the flash node and should be named |'partitions'. This node should have the following property: |- compatible : (required) must be "fixed-partitions" |Partitions are then defined in subnodes of the partitions node. | |For backwards compatibility partitions as direct subnodes of the flash device are |supported. This use is discouraged. |NOTE: also for backwards compatibility, direct subnodes that have a compatible |string are not considered partitions, as they may be used for other bindings. <https://www.kernel.org/doc/Documentation/devicetree/bindings/mtd/partition.txt> Hence, this patch converts the device to the "partitions" layout. Fixes: 1cbe457cf94 ("ipq40xx: specify "firmware" partition format for GL.iNet GL-B1300") Reported-by: Alberto Bursi <bobafetthotmail@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: dts: Remove newly added default-state=off propertyChristian Lamparter2018-12-171-10/+0
| | | | | | I'm afraid that this will be "one of many" patches to come. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ar71xx/ath79: switch devices to the -ct driver and firmwareChristian Lamparter2018-12-173-5/+5
| | | | | | | Since commit 61b5b4971e7 ("mac80211: make ath10k-ct the default ath10k") select ath10k-ct and the -ct firmwares by default. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bcm53xx: include WiFi firmware for devices with 4366C0Rafał Miłecki2018-12-171-1/+1
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: backport ifconfig ioctl support for class e addressesKevin Darbyshire-Bryant2018-12-173-0/+237
| | | | | | | | | | | | | | | | | Backport net: Allow class-e address assignment via ifconfig ioctl While most distributions long ago switched to the iproute2 suite of utilities, which allow class-e (240.0.0.0/4) address assignment, distributions relying on busybox, toybox and other forms of ifconfig cannot assign class-e addresses without this kernel patch. While CIDR has been obsolete for 2 decades, and a survey of all the open source code in the world shows the IN_whatever macros are also obsolete... rather than obsolete CIDR from this ioctl entirely, this patch merely enables class-e assignment, sanely. https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65cab850f0eeaa9180bd2e10a231964f33743edf Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* treewide: dts: Remove default-state=off property from all gpio LED nodesPetr Štetiar2018-12-1772-233/+0
| | | | | | | | | | | | | | | | | | >From the Documentation/devicetree/bindings/leds/common.txt: - default-state : The initial state of the LED. Valid values are "on", "off", and "keep". If the LED is already on or off and the default-state property is set the to same value, then no glitch should be produced where the LED momentarily turns off (or on). The "keep" setting will keep the LED at whatever its current state is, without producing a glitch. The default is off if this property is not present. So setting the default-state of the LEDs to `off` is redundant as `off` is default LED state anyway. We should remove it as almost every new PR/patch submission contains this property by default which seems to be just copy&paste from some DTS file already present in the tree. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: add support for TP-Link Archer A7Karl-Felix Glatzer2018-12-176-0/+273
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for TP-Link Archer A7 Specification: - SOC: QCA9563 - Flash: 16 MiB (SPI) - RAM: 128 MiB (DDR2) - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: - 2.4GHz (bgn) SoC internal - 5GHz (ac) QCA988x - USB: 1x USB 2.0 port - Button: 1x power, 1x reset, 1x wps - LED: 10x LEDs - UART: holes in PCB - Vcc, GND, RX, TX from ethernet port side - 115200n8 Flash instructions: Upload openwrt-ath79-generic-tplink_archer-a7-v5-squashfs-factory.bin via the Webinterface. Flash instruction using tftp recovery: 1. Connect the computer to one of the LAN ports of the Archer A7 2. Set the computer IP to 192.168.0.66 3. Start a tftp server with the OpenWrt factory image in the tftp root directory renamed to ArcherC7v5_tp_recovery.bin 2. Connect power cable to Archer A7, press and hold the reset button and turn the router on 3. Keep the reset button pressed for ~5 seconds 4. Wait ~150 seconds to complete flashing Changes since first revision: - Flash instructions using stock image webinterface - Changed "Version 5" in model string to "v5" - Split DTS file in qca9563_tplink_archer-x7-v5.dtsi and qca9563_tplink_archer-a7-v5.dts - Firmware image is now build with dynamic partitioning - Default to ath10k-ct Changes since second revision: - Changed uboot@0 to uboot@20000 in DTS file - Fixed ordering issue in board led script - Specify firmware partition format in DTS file - Rebased Makefile device definition on common Device/tplink-safeloader-uimage definition - Merged switch section in network script (same configuration as tplink,tl-wdr3600 and tplink,tl-wdr4300) Signed-off-by: Karl-Felix Glatzer <karl.glatzer@gmx.de>
* ath79, brcm63xx: Fix debounce-interval properties in gpio-keys-polled nodesPetr Štetiar2018-12-1770-71/+181
| | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes wrong usage of debounce-interval subnode property of gpio-keys-polled nodes, which was used inproperly in parent node, but it belongs to the subnodes, excerpt from the docs: Optional subnode-properties: - debounce-interval: Debouncing interval time in milliseconds. If not specified defaults to 5. And the docs are up to date as the source code matches that description as well: if (fwnode_property_read_u32(child, "debounce-interval", &button->debounce_interval)) button->debounce_interval = 5; While at it, I've also re-formatted gpio-keys-polled nodes, usually just adding new lines after every key subnode. Cc: Tomasz Maciej Nowak <tomek_n@o2.pl> Cc: Matt Merhar <mattmerhar@protonmail.com> Cc: Jonas Gorski <jonas.gorski@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: ag71xx: Fix code formatting in ag71xx_probePetr Štetiar2018-12-171-2/+2
| | | | Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: ag71xx: Unify debug output with ar71xx and make debugging easierPetr Štetiar2018-12-171-16/+32
| | | | | | | | | Currently it's quite hard to diff debugging output between ar71xx and ath79, so this patch tries to improve it by adding the same ag71xx_dump_regs function and placing debugging output from the registers to relatively same places. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ar71xx: ag71xx: Replace duplicate debugging code with simple function callPetr Štetiar2018-12-171-16/+1
| | | | | | | ag71xx_dump_regs is used in code several times, and is providing same output. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq806x: drop kernel/ rootfs partition images for the ZyXEL NBG6817Stefan Lippers-Hollmann2018-12-171-3/+1
| | | | | | | | | | | | | Since commit 8e9a59a6b924469c0061d4bd945ae0c6dbfdecfe (build: add mkrasimage) a proper factory image can be provided for the ZyXEL NBG6817, which can be flashed from the OEM firmware or used for tftp based push-button recovery, therefore the previously used partition images for mmcblk0p5-rootfs.bin and mmcblk0p4-kernel.bin are no longer required (and using them properly has always been slightly difficult and risky) and can now be dropped from the image generation code. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ath79: add d-link dir-825-c1 and dir-835-a1Sebastian Kemper2018-12-177-8/+332
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit ports both dir-825-c1 and dir-835-a1 from ar71xx to ath79. They're pretty much identical, except dir-835-a1 has less LEDs. The routers come with 128 MByte of RAM and 16 MBytes of flash and sport 2.4GHz and 5.0GHz wireless. Both routers have entries already in OpenWrt's TOH. Please check there for more information on these antiquities. https://openwrt.org/toh/hwdata/d-link/d-link_dir-825_c1 https://openwrt.org/toh/hwdata/d-link/d-link_dir-835_a1 Installation: 1. Connect to the web interface of the vendor firmware (usually listening on 192.168.0.1). 2. Go to "Tools", then "Firmware". 3. In the "Firmware Upgrade" box click "Browse". 4. Select the OpenWrt factory image for your router. 5. Click "Upload", confirm the popups if you agree to flash the file you selected. 6. Wait for firmware upgrade to complete. It takes about 5 minutes. Run-tested on dir-825-c1. dir-835-a1 should work as well, but I don't have this router so I can't confirm. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [trivial changes]
* ipq40xx: device-tree overhaulChristian Lamparter2018-12-1714-145/+156
| | | | | | | | | | | | - replace licence texts with SPDX-License-Identifier where applicable. - make node-names more generic to fit with Device-Tree Release v0.2 Section 2.2.2 Generic Names Recommendation. - utilize wifi0/1, blsp1_uart1 labels Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: specify "firmware" partition format for EnGenius EAP1300Christian Lamparter2018-12-171-0/+1
| | | | | | | Specify firmware partition format by compatible string. Cc: Steven Lin <steven.lin@senao.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: specify "firmware" partition format for GL.iNet GL-B1300Christian Lamparter2018-12-171-0/+1
| | | | | | Specify firmware partition format by compatible string. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: specify "firmware" partition format for Compex WPJ428Christian Lamparter2018-12-171-0/+1
| | | | | | Specify firmware partition format by compatible string. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: specify "firmware" partition format for ZyXEL WRE6606Christian Lamparter2018-12-171-0/+1
| | | | | | Specify firmware partition format by compatible string. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: specify "firmware" partition format for Netgear EX61[50]0v2Christian Lamparter2018-12-171-0/+1
| | | | | | | Specify firmware partition format by compatible string. Cc: David Bauer <mail@david-bauer.net> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: specify "firmware" partition format for AVM Fritz!Box 4040Christian Lamparter2018-12-171-0/+1
| | | | | | Specify firmware partition format by compatible string. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: add DT binding support to the fit parserChristian Lamparter2018-12-171-0/+6
| | | | | | It allows specifying default and Netgear parsers directly in the DT. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* gemini: Activate USB support againHauke Mehrtens2018-12-161-0/+1
| | | | | | | | | | | This activates the CONFIG_USB_SUPPORT option in the in the gemini kernel again which will provide the core USB support and makes it possible to compile the rest of the USB parts into modules. Without this change USB will not be available in the gemini target and some modules fail to compile because the feature list indicates USB support. Fixes: 10ec966f7ba7 ("gemini: Break out USB to packages") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: add support for Netgear R6350NOGUCHI Hiroshi2018-12-165-2/+179
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Netgear R6350 is a wireless router, aka Netgear AC1750. Specification: - SoC: Mediatek MT7621AT (2 CPU cores, 4 threads) - RAM: 128MiB (Nanya NT5CC64M16GP-DI) - ROM: 128MiB NAND Flash (Macronix MX30LF1G18AC-TI) - Wireless: for 11b/g/n (upto 300Mbps): MT7603 for 11a/ac (upto 1450Mbps) : MT7615, is not avaliable now - Ethernet LAN speed: up to 1000Mbps - Ethernet LAN ports: 4 - Ethernet WAN speed: up to 1000Mbps - Ethernet WAN ports: 1 - USB ports: 1 (USB 2.0) - LEDs: 4 (all can be controlled by SoC's GPIO) - buttons: 2 - serial ports: unknown Installation through telnet: - Copy kernel.bin and rootfs.bin to a USB flash disk, plug to usb port on the router. - Enable telnet with link: http://192.168.1.1/setup.cgi?todo=debug (login if required, default: admin password) - You will see "Debug Enabled!" - Telnet 192.168.1.1 and login with "root" - ls /mnt/shares/ to find out path of your USB disk. 'myUdisk' for example. - cd /mnt/shares/myUdisk - mtd_write write rootfs.bin Rootfs - mtd_write write kernel.bin Kernel - reboot recovery when bricked: nmrpflash can be used to recover to the netgear firmware if a broken image was flashed. The SC_PART_MAP partition suggests that an on flash partition table exists. After implementing a partition parser/builder for the sercom partition format, the definitions don't match the flash layout used by the stock firmware. It either means the partition format has not yet been completely understood or it isn't used by the stock firmware. For now, use fixed partitions instead. Signed-off-by: NOGUCHI Hiroshi <drvlabo@gmail.com> [apply latest ramips changes and document the on flash partition map issues] Signed-off-by: Mathias Kresin <dev@kresin.me>
* jffs2: Fix use of uninitialized delayed_work, lockdep breakageDaniel Santos2018-12-164-2/+126
| | | | | | | | | | I've sent this one upstream. This patch is critical if you want to run with "prove lock correctness" (lockdep) and you happen to have certain mtd devices. The misuse of the uninitialized object is undefined behaviour, but being zeroed it does not appear to have actually broken anything other than the lockdep engine. Signed-off-by: Daniel Santos <daniel.santos@pobox.com>
* netfilter: Add fib support for nftablesBrett Mastbergen2018-12-162-0/+2
| | | | Signed-off-by: Brett Mastbergen <bmastbergen@untangle.com>
* kernel: mv88e6060: disable hardware level MAC learningAnderson Luiz Alves2018-12-163-0/+132
| | | | | | | | | | | | | | | | Disable Marvell's hardware level MAC learning because it breaks station roaming. When enabled it drops all frames that arrive from a MAC address that is on a different port at learning table. Problem description: Multiple APs with inter-AP roaming connected to different ports, when station moves from one AP on one port to another AP on another port, traffic flow breaks down because the learning table is not updated. Signed-off-by: Anderson Luiz Alves <alacn1@gmail.com> [Replaced with upstream version, move to generic] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: add mv88e61xx switch port-mirroring supportDeng Qingfang2018-12-162-6/+169
| | | | | | Compile & run tested on mvebu Signed-off-by: Deng Qingfang <dengqf6@mail2.sysu.edu.cn>
* lantiq: add integer latency stat for lantiq-dslAndre Heider2018-12-161-0/+8
| | | | | | | The current stats always have a 'ms' suffix, and they're used by luci. Introduce dsl.latency_[down|up] values, exported in µs without suffix. Signed-off-by: Andre Heider <a.heider@gmail.com>
* ath79: add support for TP-Link TL-WR842N/ND v1 routerMarcin Jurkowski2018-12-154-0/+175
| | | | | | | | | | | | | | | | | | This ports support for TP-Link TL-WR842N/ND v1 from ar71xx. CPU: Atheros AR7241 400 MHz RAM: 32 MiB FLASH: 8 MiB PORTS: 4 Port 100/10 Switch, 1 Port 100/10 Wan WiFi: Atheros AR9287 LED: SYS, WiFi, LAN, WAN, 3G, QSS BTN: WiFi, Reset/WPS AR71xx target used "tl-mr3420" as board id so force flag is needed if upgrading from old target. Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [trivial cleanup]
* ipq806x: add ath10k calibration data MAC addresses patchingChristian Lamparter2018-12-152-35/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ben Greear reported in his patch: |Subject: netgear r7800: Fix mac address of radios. | |Reloading the driver causes the phyX to change, and that |caused the MAC address to change. This is because all ODM/OEMs except QCA bothered to write the correct MAC address for the ath10k wifi into the calibration data. This patch copies over the MAC patching helper functions from ipq40xx's target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata file and converts all the devices to patch the correct MACs into the extracted calibration data before it gets sent to the driver, which sets up the device with the correct MAC address. It also removes the entries in the 10_fix_wifi_mac file as they have served their purpose for good. Please note the C2600: There is conflicting information on what the offset for the second wifi is supposed to be. This patch uses what was specified in 10_fix_wifi_mac. According to Ben Greear this method is save to use with the stock firmware too. As he explained that the stock firmware messes up rx-bssid mask calculation when the MAC is changed after the first vif is created. Reported-by: Ben Greear <greearb@candelatech.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ramips: mt7620: add usb packagesMathias Kresin2018-12-151-4/+16
| | | | | | | | | Add the usb drivers for all boards with enabled ochi/ehci node in the dts file. Fixes: FS#1987 Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: mt7620: remove unnecessary usb packagesMathias Kresin2018-12-151-3/+3
| | | | | | These are either installed as dependency or not required at all. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: mt7620: add usb ohci driverMathias Kresin2018-12-151-6/+6
| | | | | | | Add the USB 1.1 driver for all boards not having a fixed USB 2.0 device attached to the USB bus. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: several fixes for HC5x61Deng Qingfang2018-12-156-25/+43
| | | | | | | | | | | | | | | | | | | | | - Mark other partitions as read-only for HC5x61 - Only enable USB and PCIe for HC5761/HC5861 HC5661 doesn't have a USB port, and there is nothing attached to its PCIe. - Fix HC5761 switch ports HC5761 has only 3 ethernet ports (1x WAN + 2x LAN). Remove unused ports. - Fix HC5861 5GHz radio HC5861 has MT7612EN 5GHz WiFi chip, not MT7610EN. - Fix HC5761/HC5861 WiFi LEDs After 5GHz is enabled, it becomes wlan0. And 2.4GHz would be wlan1. - Fix HC5x61 image size It should be 15872k (0xf80000) Signed-off-by: Deng Qingfang <dengqf6@mail2.sysu.edu.cn>
* ipq40xx: integrate ath10kcal_patch_mac into ath10kcal_patch_mac_crcChristian Lamparter2018-12-151-17/+11
| | | | | | | | | | | | | | | In the thread: "ipq806x: add ath10k calibration data MAC addresses patching" Chuanhong Guo <gch981213@gmail.com> noted that: "All ath10k calibration data have a checksum at 0x2. ath10kcal_patch_mac works for QCA9880/QCA9882 only because the ath10k firmware for these two chips doesn't check the checksum value. (QCA proprietary driver checks this and refuses to use caldata with incorrect checksum.)" This patch updates 11-ath10k-caldata of the ipq40xx target accordingly. Reported-by: Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: netfilter: chain filters merged into nf_tables.koHauke Mehrtens2018-12-151-6/+6
| | | | | | | | | | | | | | | | | | In mainline kernel commit 02c7b25e5f5 ("netfilter: nf_tables: build-in filter chain type") all chain filters were merged into one file and into one kernel module to save some memory. The code protected by these configuration options CONFIG_NF_TABLES_BRIDGE, CONFIG_NF_TABLES_IPV4, CONFIG_NF_TABLES_ARP, CONFIG_NF_TABLES_IPV6, CONFIG_NF_TABLES_NETDEV and CONFIG_NF_TABLES_INET was merged into the nft_chain_filter.c file which is now always compiled into the nf_tables.ko file. This only happened in kernel 4.19 and OpenWrt has to select these as modules in older kennel versions. Mark them as build-in in the kernel 4.19 specific kernel configuration file which will then not be overwritten by the package specific settings which try to make them modular again. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: netfilter: Adapt merge ipv4/ipv6 masquerade codeHauke Mehrtens2018-12-151-2/+2
| | | | | | | | | | | | | | | | In kernel commit 0168e8b361 ("netfilter: nat: merge ipv4/ipv6 masquerade code into main nat module") the CONFIG_NF_NAT_MASQUERADE_IPV4 and CONFIG_NF_NAT_MASQUERADE_IPV6 kernel configuration option were changed to bool and the code will not be compiled as a own module any more, but it will be integrated into nf_nat_ipv4.ko or nf_nat_ipv6.ko to save some memory. Activate these options as bool in the generic kernel 4.19 configuration only, to always build them into the nf_nat_ipv*.ko modules. The kmod file will still try to select them as module, but the generic configuration will not be overwritten. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Make CONFIG_NVMEM tristateHauke Mehrtens2018-12-151-0/+33
| | | | | | | | | | | | CONFIG_OF_NET depends on CONFIG_NVMEM in kernel 4.19. To fix some build problems in mainline Linux kernel CONFIG_NVMEM was changed from tristate to bool in commit 2a37ce25d9 ("nvmem: disallow modular CONFIG_NVMEM"). This patch in OpenWrt revert the upstream commit and changes CONFIG_NVMEM back to tristate we just have to make sure to build this in for all targets which select CONFIG_OF_NET. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-25 06:38:55 +0000