aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: add missing metadata for tp-link imagesFelix Fietkau2016-11-211-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* scripts/getver.sh: treat all commits as local if can't find upstreamRafał Miłecki2016-11-211-1/+1
| | | | | | | | | | | | | | | If something goes wrong and script can't find upstream revision it will return something like: r2220 which looks like a valid upstream revision 2220. We cant' distinguish it from e.g. 2200 upstream commits and 20 local ones. The new format still provides revision number but also points clearly that is may be not the upstream one: r0+2220 Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Acked-by: John Crispin < john@phrozen.org>
* grub2: add PKG_FIXUP:=autoreconfAlexandru Ardelean2016-11-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | The host-side build of grub2 requires this sometimes. This will re-generate the ./configure script from configure.ac. I don't know the conditions of how this reproduces, it just sometimes appears, and sometimes doesn't. Build error ``` <lede-dir>/build_dir/target-x86_64_musl-1.1.15_yogi/host/grub-2.02~beta2/build-aux/missing: line 81: aclocal-1.14: command not found WARNING: 'aclocal-1.14' is missing on your system. You should only need it if you modified 'acinclude.m4' or 'configure.ac' or m4 files included by 'configure.ac'. The 'aclocal' program is part of the GNU Automake package: <http://www.gnu.org/software/automake> It also requires GNU Autoconf, GNU m4 and Perl in order to run: <http://www.gnu.org/software/autoconf> <http://www.gnu.org/software/m4/> <http://www.perl.org/> Makefile:3962: recipe for target 'aclocal.m4' failed ``` Adding PKG_FIXUP adds sanity (i.e. autoreconf is used for host & target builds) over just using HOST_FIXUP. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* ramips: Fix sdhci kernel panics on MT7621Andrew Yong2016-11-211-2/+2
| | | | | | | | | | | | | | Enable work-arounds present in the code commented-out but needed to write to sdcard on mt7621 which currently causes kernel to oops when engaging in serious writing to sdcard. With this change applied, there are still occasional warnings thrown by the mmc driver, however, at least it no longer crashes the system and even large writes (full-card dump/erase/write/compare) don't show any corruption. Signed-off-by: Daniel Golle <daniel@makrotopia.org> Rebase to LEDE and added "CONFIG_SOC_MT7621" check to ensure non-MT7621 devices do not face performance regressions. Signed-off-by: Andrew Yong <me@ndoo.sg>
* odhcpd: update to latest git HEADJohn Crispin2016-11-211-2/+2
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* odhcpd: update to latest git HEADJohn Crispin2016-11-211-4/+4
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mvebu: Add BQL patch for mvneta driver.Toke Høiland-Jørgensen2016-11-211-0/+83
| | | | | | | | This adds the patch submitted to upstream that adds BQL to the mvneta driver: https://patchwork.kernel.org/patch/9328413/. Helps latency under load when the physical link is saturated. Signed-off-by: Toke Høiland-Jørgensen <toke@toke.dk>
* firmware-utils: Add support for the Cisco Meraki MX60/MX60WChris Blake2016-11-211-11/+58
| | | | | | | | | | | | | | This patch adds header support for the Cisco Meraki MX60/MX60W, which are a part of the apm821xx target. Some structure changes were needed due to the fact this device uses U-Boot (unlike other devices in mkmerakifw.c) which uses a different header structure to define the load offsets for the image. A thanks to Christian for helping implement this properly. Cc: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* lantiq: use dwc2 by default on danubeBen Mulvihill2016-11-211-13/+13
| | | | | | Use dwc2 by default on all danube boards. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
* lantiq: dwc2 parameters for danubeBen Mulvihill2016-11-211-2/+31
| | | | | | | | | | Parameters for dwc2 on lantiq. A separate dwc2_core_params structure is defined for danube because danube fifo sizes are large enough to be autodetected. This is not the case on arx and vrx. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
* lantiq: device tree bindings for dwc2 on danubeBen Mulvihill2016-11-211-1/+2
| | | | | | | | | Device tree binding for dwc2 usb driver on danube. Leave old ifxhcd-danube driver as an alternative. Also adds dr_mode = "host" to eliminate warning on boot. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
* lantiq: initialise dwc2 on danubeBen Mulvihill2016-11-211-0/+10
| | | | | | Initialise dwc2 usb driver on danube boards as well as ar9 and vr9. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
* apm821xx: Add support for the Cisco Meraki MX60/MX60WChris Blake2016-11-2111-16/+283
| | | | | | | | | | | | | | | | | | | This patch adds support for the Cisco Meraki MX60/MX60W Security Appliance. Flashing information can be found at https://github.com/riptidewave93/LEDE-MX60 Specs are as follows: AppliedMicro APM82181 SoC at 800MHz 1GiB NAND - Samsung K9K8G08U0D 512MB DDR RAM - 4x Nanya NT5TU128M8GE-AC Atheros AR8327-BL1A Gigabit Ethernet Switch 1x USB 2.0 Port More info can be found at https://wiki.openwrt.org/toh/meraki/mx60 Cc: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* ramips: add support for WeVO W2914NS v2perillamint2016-11-218-0/+168
| | | | Signed-off-by: Yong-hyu Ban <perillamint@gentoo.moe>
* openvpn: update to 2.3.13Magnus Kroken2016-11-211-2/+2
| | | | | | Changelog: https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn23#OpenVPN2.3.13 Signed-off-by: Magnus Kroken <mkroken@gmail.com>
* ar71xx: Fix switch config on Mikrotik RB450/GJoão Chaínho2016-11-211-2/+6
| | | | | | | This patch fixes the ethernet switch initial config for Mikrotik RB450 and RB450G. The previous version wrongly changed the RouterStation Pro config. This one creates a specific config for the RB450G and leaves the RouterStation Pro unchanged. Signed-off-by: João Chaínho <joaochainho@gmail.com>
* uboot-envtools: add 'dockstar' for kirkwoodPaul Wassi2016-11-211-0/+1
| | | | | | Add board 'dockstar' to known fw_env-configurations. Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* uboot-envtools: add support for YunCore CPE830Piotr Dymacz2016-11-211-0/+1
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for YunCore CPE830Piotr Dymacz2016-11-2110-26/+131
| | | | | | | | | CPE830 is a clone of AP90Q, with different type of antenna (panel) and additional 4 LEDs for WiFi signal level indication. Use the same flash approach as for YunCore AP90Q. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* uboot-envtools: add support for YunCore CPE870Piotr Dymacz2016-11-211-0/+1
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for YunCore CPE870Piotr Dymacz2016-11-2110-0/+188
| | | | | | | | | | | | | | | | | | | | | | | | | | YunCore CPE870 is an outdoor CPE/AP based on Atheros AR9341. Short specification: - 535/400/200 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, passive PoE support - 64/128 MB of RAM (DDR2) - 8 MB of FLASH - 2T2R 2.4 GHz with external PA (SKY65174-21), up to 30 dBm - internal 14 dBi panel antenna - 8x LED, 1x button - UART (JP1) header on PCB Flash instruction (do it under U-Boot, using UART): 1. tftp 0x80060000 lede-ar71xx-generic-cpe870-squashfs-sysupgrade.bin 2. erase 0x9f020000 +$filesize 3. cp.b $fileaddr 0x9f020000 $filesize 4. setenv bootcmd "bootm 0x9f020000" 5. saveenv && reset Vendor firmware access (login/password): Admin/5up Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* uboot-envtools: add support for YunCore AP90QPiotr Dymacz2016-11-211-0/+1
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for YunCore AP90QPiotr Dymacz2016-11-2110-7/+163
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | YunCore AP90Q is an outdoor CPE/AP based on Qualcomm/Atheros QCA9531 v2. Short specification: - 650/600/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, passive PoE support - 64/128 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz with external PA, up to 29 dBm - 2x internal 5 dBi omni antennas - 4x LED, 1x button - UART (JP1) header on PCB Flash instruction under U-Boot, using UART: 1. tftp 0x80060000 lede-ar71xx-generic-ap90q-squashfs-sysupgrade 2. erase 0x9f050000 +$filesize 3. cp.b $fileaddr 0x9f050000 $filesize 4. setenv bootcmd "bootm 0x9f050000" 5. saveenv && reset Flash instruction under vendor fimrware, using telnet/SSH: 1. Connect PC with 192.168.1.x address to WAN port 2. Power up device, enter failsafe mode with button (no LED indicator!) 3. Change root password and reboot (mount_root, passwd ..., reboot -f) 4. Upload lede-ar71xx-generic-ap90q-squashfs-sysupgrade.bin to /tmp using SCP 5. Connect PC with 192.168.188.x address to LAN port, SSH to 192.168.188.253 6. Invoke: - cd /tmp - fw_setenv bootcmd "bootm 0x9f050000" - mtd erase firmware - mtd -r write lede-ar71xx-generic-ap90q-squashfs-sysupgrade.bin firmware Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for COMFAST CF-E380AC v1 and v2Piotr Dymacz2016-11-2112-9/+211
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | COMFAST CF-E380AC v1/v2 is a ceiling mount AP with PoE support, based on Qualcomm/Atheros QCA9558+QCA9880+AR8035. There are two versions of this model, with different RAM and U-Boot mtd partition sizes: - v1: 128 MB of RAM, 128 KB U-Boot image size - v2: 256 MB of RAM, 256 KB U-Boot image size Version number is available only inside vendor GUI, hardware and markings are the same. Short specification: - 720/600/200 MHz (CPU/DDR/AHB) - 1x 10/100/1000 Mbps Ethernet, with PoE support - 128 or 256 MB of RAM (DDR2) - 16 MB of FLASH - 3T3R 2.4 GHz, with external PA (SE2576L), up to 28 dBm - 3T3R 5 GHz, with external PA (SE5003L1), up to 30 dBm - 6x internal antennas - 1x RGB LED, 1x button - UART (T11), LEDs/GPIO (J7) and USB (T12) headers on PCB - external watchdog (Pericon Technology PT7A7514) Flash instruction: Original firmware is based on OpenWrt. Use sysupgrade image directly in vendor GUI. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for COMFAST CF-E320N v2 and CF-E520N/CF-E530NPiotr Dymacz2016-11-2110-42/+329
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As we already have support for CF-E316N v2 and many devices from this vendor look similar, the support was included in existing mach-*.c file, with few cleanups and fixes. All 3 devices are based on Qualcomm/Atheros QCA9531 v2. COMFAST CF-E320N v2 is a ceiling mount AP with PoE support. Short specification: - 650/393/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 22 dBm - 2x internal antennas - 1x RGB LED, 1x button - UART (J1), GPIO (J9) and USB (J2) headers on PCB - external watchdog (Pericon Technology PT7A7514) COMFAST CF-E520N/CF-E530N are in-wall APs with USB and PoE support. They seem to have different only the front panel. Short specification: - 650/393/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, WAN with PoE support - 1x USB 2.0 (in CF-E520N covered by panel, available on PCB) - 32 MB of RAM (DDR2) - 8 MB of FLASH - 2T2R 2.4 GHz, up to 22 dBm - 2x internal antennas - 1x LED, 1x button - UART (J1) headers on PCB Flash instruction: Original firmware is based on OpenWrt. Use sysupgrade image directly in vendor GUI. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ipq806x: c2600: change wan and lan led trigger to swconfig portHenryk Heisig2016-11-211-2/+2
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* ipq806x: enable swconfig LED supportHenryk Heisig2016-11-211-0/+1
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* kernel: remove pipetypes unused var warningKevin Darbyshire-Bryant2016-11-211-1/+11
| | | | | | | Update patch to remove pipetypes var declaration which was throwing unused variable warning due to the original patch removing the only use. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
* ipq806x: switch to upstream usb driver and backport fixesPavel Kubelun2016-11-2118-23/+1094
| | | | | | Also removing fifo-resize property drom DT as it has been removed from the driver. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
* ar71xx: fix drivers/mtd/nand/ar934x_nfc.cPaul Wassi2016-11-181-8/+2
| | | | | | | Fix the incorrect usage of ar934x_nfc_write_page and ar934x_nfc_write_page_raw. Add *page* in the argument list and remove the local variable. Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* lantiq: remove device specific sysupgrade image checksFelix Fietkau2016-11-201-22/+1
| | | | | | Replaced by image metadata Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq806x: remove device specific sysupgrade image checksFelix Fietkau2016-11-201-24/+1
| | | | | | Replaced by image metadata Signed-off-by: Felix Fietkau <nbd@nbd.name>
* firmware-utils: tplink-safeloader: keep per-device info on trailing charRafał Miłecki2016-11-201-5/+11
| | | | | | | | | | | | | | | | | Recent refactoring introduced a regression. It ignored second argument of make_support_list function which was originally true for C2600. The new generic build_image function always passes false. This patch allows specifying trailing char in a device specific info. It also switches Archer C9 to the \0 char to make it compliant with vendor images. I verified generated images to be binary identical to the ones that were created before whole refactoring. Reported-by: Jo-Philipp Wich <jo@mein.io> Fixes: fd924d2068f ("firmware-utils: tplink-safeloader: use one function for generating images") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: add bcm47xxpart patch fixing parsing with some TRX formatsRafał Miłecki2016-11-201-0/+37
| | | | | | | | This fixes parsing partition placed after TRX with block-aligned length. It's important e.g. for Archer C9 which has TRX with kernel only and rootfs as separated partition. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ipq806x: fix build errorsPavel Kubelun2016-11-193-0/+262
| | | | | | Add missing patches that broke LEDE builder while updating WDT driver Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
* kernel: rtl8367(b): fix build errorMathias Kresin2016-11-192-2/+2
| | | | | | | | | | Fix build on targets not using CONFIG_MODULE_STRIPPED. Neither RTL8367_DRIVER_DESC nor RTL8367B_DRIVER_DESC are defined anywhere. It worked for targets using CONFIG_MODULE_STRIPPED since our module stripper no-ops the various module info macros. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: run append-metadata before check-size to fix build errorsFelix Fietkau2016-11-191-4/+4
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* x86: fix GRUB_ROOT for Xen subtargetWilfried Klaebe2016-11-192-1/+7
| | | | | | | | | Change grub's root device to xen/xvda,msdos1 for the x86_xen_domu target so that it will boot without further changes. Signed-off-by: Wilfried Klaebe <w+lede-project@chaos.in-kiel.de> [Jo-Philipp Wich: fixed and rebased patch from FS#264, added subject] Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: append metadata to imagesFelix Fietkau2016-11-197-22/+33
| | | | | | | metadata checks are not enforced yet, because some images are still being built by legacy code Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: append metadata to imagesFelix Fietkau2016-11-192-5/+7
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq806x: append metadata to imagesFelix Fietkau2016-11-192-6/+6
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: add support code for appending metadata to imagesFelix Fietkau2016-11-192-1/+22
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* base-files: validate metadata of sysupgrade imagesFelix Fietkau2016-11-193-2/+43
| | | | | | | | | | | Use fwtool to extract it, only require metadata to be present if the platform sysupgrade script sets REQUIRE_IMAGE_METADATA=1 Image metadata is in JSON format and contains a list of supported devices, along with version information that could be displayed by a UI later before the actual upgrade happens. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* fwtool: add utility for appending and extracting firmware metadata/signaturesFelix Fietkau2016-11-195-0/+693
| | | | | | | | | | | | | | | | | | | | | | | | | This will be used to append extra information to images which allows the system to verify if an image is compatible with the system. The extra data is appended to the end of the image, where it will be ignored when upgrading from systems that do not process this data yet: If the image is a squashfs or jffs2 image, the extra data will land after the end-of-filesystem marker, where it will be overwritten once the system boots for the first timee. If the image is a sysupgrade tar file, tar will simply ignore the extra data when unpacking. The layout of the metadata/signature chunks is constructed in a way that the last part contains just a magic and size information, so that the tool can quickly check if any valid data is present without having to do a pattern search throughout the full image. Chunks also contain CRC32 information to detect file corruption, even when the image is not signed. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* bcm53xx: build image for TP-LINK Archer C9 v1Rafał Miłecki2016-11-192-1/+27
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: support SafeLoader format in sysupgradeRafał Miłecki2016-11-192-2/+36
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* firmware-utils: tplink-safeloader: add Archer C9 supportRafał Miłecki2016-11-191-0/+33
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* osafeloader: new util for extracting partitions from SafeLoaderRafał Miłecki2016-11-195-0/+649
| | | | | | | | SafeLoader is image format used by some TP-LINK devices. This tool allows extracting selected partitions out of it. It can be used for sysupgrade. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add kernel support for TP-LINK Archer C9 V1Rafał Miłecki2016-11-193-42/+194
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* firmware-utils: tplink-safeloader: use one function for generating imagesRafał Miłecki2016-11-191-79/+29
| | | | | | Thanks to the struct device_info we can now use one unified function. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 18:56:31 +0000