aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* apm821xx: convert MR24 to use DT PHY defintionChristian Lamparter2018-01-125-0/+369
| | | | | | Convert the MR24 to use the DT phy probing and at803x PHY driver. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add linux 4.14 apm821xx patchesChristian Lamparter2018-01-1214-3/+1458
| | | | | | | | | | | This patch updates the apm821xx target to use the 4.14 kernel. 4.14 finally ships with a driver for the WNDR4700's tc654 fan controller. The custom driver is deprecated in favor of the upstream driver and the thermal cooling definitions in the DTS are updated. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kmod-sched-cake: bump to latest cake bakeKevin Darbyshire-Bryant2018-01-111-3/+3
| | | | | | | | | | | | | | | | | More important bug fix: 402f05c Use full-rate mtu_time in all tins. Fixes an issue where some cake tins experienced excessive latency since 49776da (dynamically adjust target) Minor bug fixes: 31277c2 Avoid unsigned comparison against zero. Fix compiler warning, no known impact. 8cf5278 ack_filter: fix TCP flag check. A very contrived case may have lead to dropping a SYN packet that should not be dropped. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* at91: create device specific sdcard imagesHauke Mehrtens2018-01-111-4/+4
| | | | | | | | | | Without this patch one sdcard image with the following name is created for all devices: openwrt-at91-sama5--sdcard.img.gz This makes the build system create device specific versions like: openwrt-at91-sama5-at91-sama5d2_xplained-sdcard.img.gz Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.13Kevin Darbyshire-Bryant2018-01-114-10/+10
| | | | | | Refresh patches Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: bump 4.4 to 4.4.111Kevin Darbyshire-Bryant2018-01-113-5/+5
| | | | | | | | Refresh patches Tested-on: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: bump 4.9 to 4.9.76Kevin Darbyshire-Bryant2018-01-113-15/+15
| | | | | | | | | Refresh patches Tested-on: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* build: fix restoring /etc/opkg with PER_DEVICE_ROOTFSJo-Philipp Wich2018-01-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When generating per-device rootfs directories, the ./etc/opkg/ directory is moved away prior to calling opkg install, opkg remove and rootfs_prepare. After the opkg invocations and the rootfs_prepare macro call, the saved opkg config directory is supposed to be moved back to its previous ./etc/opkg location. The mv command however can fail to properly restore the directory under certain circumstances, e.g. when the prior opkg or files/ overlay copy operations caused a new ./etc/opkg/ directory to be created. In this case, the backed up directory (named target-dir-$hash.opkg) will be moved into the preexisting ./etc/opkg/ directory instead, causing the opkg configuration to be located in a wrong path on the final rootfs, e.g. in /etc/opkg/target-dir-$hash.opkg/distfeeds.conf instead of /etc/opkg/distfeeds.conf. Solve this problem by replacing the naive "mv" command with a recursive "cp -T" invocation which causes the backed up directory tree to get merged with the destination directory in case it already exists. Also perform the rootfs_prepare macro call after restoring the opkg configuration, to allow users to override it again by using the files/ overlay mechanism. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* sdk: change base feed fallback to git.openwrt.orgJo-Philipp Wich2018-01-111-1/+2
| | | | | | | Change the hardcoded lede-project.org base feed fallback to $(PROJECT_GIT)/openwrt/openwrt.git instead. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* bcm53xx: replace linux,part-probe with a proper partitions subnodeRafał Miłecki2018-01-115-22/+106
| | | | | | | | | This solution is more upstream compatible as it only requires specifying of_match_table in the parser code and doesn't depend on linux,part-probe which is solution made generic by a LEDE downstream patch that can't be upstreamed. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: backport mtd implementation for "compatible" in "partitions" subnodeRafał Miłecki2018-01-1118-56/+386
| | | | | | | | | | | This backports upstream support for "compatible" DT property set for the "partitions" subnode of flash node. It allows specifying how partitions should be created/parsed. Right now only "fixed-partitions" is supported. It should eventually replace our downstream "linux,part-probe" solution. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: allow disabling multicast routing supportMatthias Schiffer2018-01-115-5/+20
| | | | | | | | Multicast routing support is not needed in most setups, and increases the size of the kernel considerably (>10K after LZMA). Add a config switch to allow disabling it. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* generic: unlock Winbond flash on bootMatthias Schiffer2018-01-112-0/+74
| | | | | | | | | | | | The underlying issue breaking Spansion flash has been fixed with "mtd: spi-nor: wait until lock/unlock operations are ready" and "mtd: spi-nor: wait for SR_WIP to clear on initial unlock", so we can support unlocking for Winbond flash again. This is necessary to have writable flash on certain UBNT devices with some bootloader versions. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ebtables: update to latest git 2017-10-24Matthias Schiffer2018-01-111-3/+3
| | | | | | | 6a82659 Use flock() for --concurrent option 73c2371 ebtables: extensions: Constify option struct Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* sunxi: enable missing config symbolJo-Philipp Wich2018-01-111-0/+1
| | | | | | | | Enable CONFIG_MFD_AXP20X_I2C after the switch to Kernel 4.9, this symbol is reportedly required to get USB working on the Banana Pi. Ref: https://forum.lede-project.org/t/sunxi-kernel-4-9-usb-not-working/10513 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* omcproxy: silence fw3 warningsHans Dedecker2018-01-102-3/+3
| | | | | | Silence fw3 warnings in omcproxy init script in case fw3 is not enabled Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* treewide: replace LEDE_GIT with PROJECT_GITJo-Philipp Wich2018-01-1025-25/+25
| | | | | | | Remove LEDE_GIT references in favor to the new name-agnostic PROJECT_GIT variable. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* downloads.mk: introduce name-agnostic PROJECT_GIT variableJo-Philipp Wich2018-01-101-2/+4
| | | | | | | | | | Introduce a name-agnostic PROJECT_GIT variable poiting to https://git.openwrt.org/ and declare LEDE_GIT and OPENWRT_GIT as aliases to it. After some transition time we can drop this alias variables. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* netifd: update dhcp.script to handle dynamic routingMogula Pranay2018-01-102-2/+8
| | | | | | | | | | | | Certain DHCP servers push a gateway outside of the assigned interface subnet, to support those situations, install a host route towards the gateway. If Gateway and IP are served in same network, openwrt quagga cannot learn routes (rip routes are not getting added, showing inactive) whereas working fine when Gateway and IP are in different network. Signed-off-by: Mogula Pranay <mogula.pranay@nxp.com> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ltq-xdsl-app: drop script for renaming the netdevMathias Kresin2018-01-104-22/+6
| | | | | | | Our netdevs are named dsl by default now, the rename via scripts isn't required anymore. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: create ATM/PTM interfaces with dsl as netdev nameMathias Kresin2018-01-104-5/+17
| | | | | | | | | | | | | | | | | | | | | Renaming an atm etherbride using 'ip link' (via hotplug) is racy since the original netdev might disappear before br2684ctl has finished appling it's setting: local2.notice br2684ctl[1667]: Interface "nas0" created sucessfully local2.notice br2684ctl[1667]: Communicating over ATM 0.8.35, encapsulation: LLC kern.info kernel: dsl0: renamed from nas0 kern.err kernel: br2684:br2684_regvcc: tried to attach to non-existent device local2.err br2684ctl[1667]: Could not configure interface:No such device or address By passing the final used netdev name to br2684ctl_wrap another race condition workaround will be enabled again. Change the lantiq ptm driver to create a netdev with the name dsl as well. Albeit the rename via 'ip link' works fine so far, using a different approach for ptm then atm could be confusing. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ltq-xdsl-app: drop manual br2684ctl reloadMathias Kresin2018-01-102-4/+0
| | | | | | | | | | br2684ctl starts automatically, set up reload triggers, which fire as soon as a atm driver is loaded. No need to do the reload via the script. The reload is only required as soon as we can reliable switch between atm and ptm driver and need to be implemented in a race free way. Signed-off-by: Mathias Kresin <dev@kresin.me>
* linux-atm: add br2684ctl option to specify the netdev nameMartin Schiller2018-01-104-4/+84
| | | | | | | | | | | Add the uci option nameprefix to specifc a target netdev name. Patch the br2684ctl code to accept and set a netdev name via commandline parameters. It allows to use the same netdev name for ATM and PTM lines on lantiq xdsl hardware. Signed-off-by: Martin Schiller <ms@dev.tdt.de> Signed-off-by: Mathis Kresin <dev@kresin.me>
* armvirt: re-enable VFP supportJo-Philipp Wich2018-01-101-1/+0
| | | | | | | | | | Enable CONFIG_VFP again which was disabled during the 4.9 -> 4.14 bump. Boot tested both 32 and 64 bit subtargets using initramfs images with the qemu-system-arm and qemu-system-aarch64 emulators. Fixes: aa100b66f2 ("armvirt: bump to v4.14") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* armvirt: 64: add missing kernel config symbolsJo-Philipp Wich2018-01-101-0/+13
| | | | | Fixes: aa100b66f2 ("armvirt: bump to v4.14") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: bump 4.4 to 4.4.110Kevin Darbyshire-Bryant2018-01-1026-125/+136
| | | | | | | | | | Refresh patches Fixes: CVE-2017-5754 aka Meltdown Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> [fix typo in commit msg, conflict after 4.14 bump] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: bump 4.9 to 4.9.75Kevin Darbyshire-Bryant2018-01-1019-43/+43
| | | | | | | | | | | | | Refresh patches Fixes: CVE-2017-5754 aka Meltdown Tested-on: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [fix conflict after 4.14 bump] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* uboot-at91: make packages hiddenHauke Mehrtens2018-01-091-0/+1
| | | | | | | | These packages are needed to generate the image, better mark them hidden so we will activate them based on which boards gets build and they will be activated always when the board which needs then gets build. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* at91bootstrap: make packages hiddenHauke Mehrtens2018-01-091-0/+1
| | | | | | | | These packages are needed to generate the image, better mark them hidden so we will activate them based on which boards gets build and they will be activated always when the board which needs then gets build. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* at91bootstrap: remove redundant definition of BUILD_SUBTARGETHauke Mehrtens2018-01-091-8/+0
| | | | | | | It is sufficient to define this in AT91Bootstrap/Default as this is not used for all. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* at91bootstrap: at91bootstrap default selectionSandeep Sheriker Mallikarjun2018-01-091-16/+16
| | | | | | | | | | | The fixes following problems 1. changing prefix at91bootstrap to AT91bootstrap will fix the default selection of at91bootstrap for the selected sama5 subtarget. 2. fixed missing default selection of sama5d4 nand flash for the selected sama5d4 subtarget. 3. corrected at91bootstrap Title name. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* uboot-at91: fix build after fpu activationSandeep Sheriker Mallikarjun2018-01-091-1/+1
| | | | | | | | | neon and VFPv4 support is added to this target and uboot-at91 build fails due to TARGET_CFLAGS -mfloat-abi set to hard. as a fix, setting uboot-at91 CFLAGS -mfloat-abi=soft. Fixes: 01cc6bd495f ("at91: sama5: activate fpu") Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* kernel: kmod-w1 depends on kmod-hwmon-core since Linux 4.14Jo-Philipp Wich2018-01-091-0/+1
| | | | | | | | | Fixes the following dependency error encountered by the buildbots: Package kmod-w1 is missing dependencies for the following libraries: hwmon.ko Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kirkwood: sort occurrences of boardame alphabeticallyMathias Kresin2018-01-095-93/+92
| | | | | | | This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-envtools: add pogoplug v4Alberto Bursi2018-01-091-1/+2
| | | | | | add pogoplug v4 envs support in uboot-envtools Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* kirkwood: add pogoplug v4Alberto Bursi2018-01-094-1/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | also known as POGO-V4-A3-02 or POGO-V4-A3-01 SoC: Marvell 88F6192 800Mhz SDRAM memory: 128MB Gigabit ethernet: 1 Marvell 88E1310 Flash memory: 128MB 2 status LEDs (one green one red) 1 "Eject" button on the back (used as "Reset" button) 1 USB 2.0 port (on upper side) 1 sata slot (power + data) for 2.5'' drives (upper side) 2 USB 3.0 ports from a controller on PCIe x1 of the SoC 1 full-size SDcard slot (fits a whole SD card into it) This device supports the (linux-only) kwboot tool to send a new uboot over serial console, so it is easy to unbrick in case the uboot is erased and the device won't boot. ----- Install instructions: ----- Since it's not possible to get ssh access to these devices, the only way to take control is to solder pins to get TTL serial access. Case can be opened by removing screws beneath two rubber feet at back of device, then lifting while prying the sides of the upper part out to unhook a latch on each side about 2/3rds of the way toward the front. Serial connection pins are those labeled "J11", left of SD as you face SD opening. Pins are (from left to right, i.e. the first in the list is the nearest to the SD slot) GND, Rx, Tx. Do not connect +V pin if you use a USB (self-powered) TTL-to-USB dongle. Any USB TTL-to-USB converter will work. Baud rate is 115200, parity "none", databits "8", flow control "none". Stock uboot is unable to read ubi partitions (nor usb) so we will replace it first with our uboot. Start a TFTP server at IP address 169.254.254.254, and place the uboot.kwb file in the folder of the server. Start the serial session and then power up the device. As soon as you see text on the serial start pressing random letter keys to stop the boot process. If you see something like the following line you can proceed: CE>> Otherwise if text is still scrolling by you missed the opportunity, pull the plug and try again. write printenv ethaddr The uboot will write something like this: ethaddr=00:50:43:00:02:02 This is the device's MAC address, also present in the sticker under the device. Write this down as we will need to add it in the new uboot configuration. Use the following commands to load the new uboot: tftp 0x20000 u-boot.kwb If the uboot confirms that the transfer was successful, then you can write it to flash with the following commands: nand erase 0 0x200000 nand write 0x20000 0 0x1c0000 if after the last command the uboot wrote "xxxx bytes written: OK" then it was written correctly and we can proceed. If it did not go well, try again or ask assistence in forums. Shutting down or rebooting at this time will brick the device, to unbrick it you will need to use the kwboot tool from a Linux PC or Virtual Machine. Now write: reset and press enter, the device will reboot and you should see again text scrolling by. Press a random key to stop it, and now you should see pogoplugv4> We now add the MAC address back, write: setenv ethaddr '00:50:43:00:02:02' Confirm that the uboot has understood by writing printenv ethaddr If all looks ok, save the setting with saveenv At this point the uboot is configured, and we only need to load the firmware in the flash memory. Follow the steps below in "Firmware recovery procedure". ---- Firmware recovery procedure ---- The new uboot allows easy recovery from a bad firmware upgrade where you can't access the device anymore over ssh or luci. Take a USB flash drive formatted as FAT32, and copy the initramfs image file in it (it will have "initramfs" in the file name), then rename it as "initramfs.bin". Insert the USB drive in the USB 2.0 port of the pogoplug (the port at the top). Power up the device, and wait for it to finish booting. The uboot should find and load the "initramfs.bin" from usb and if you are connected with serial you should see the linux kernel boot log (text scrolling by). Once it is done, press Enter and you will be greeted by the OpenWRT banner. If you were not connected with serial just wait a bit and, you will be able to access it with ssh or luci web interface (once you find its IP). The recovery "initramfs" images are run from RAM, so you will have to do a normal sysupgrade (firmware upgrade) to write a firmware image to flash memory. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* uboot-kirkwood: add uboot for pogoplug v4Alberto Bursi2018-01-092-1/+1581
| | | | | | | | | | | | | | | | | | | | | add an uboot able to boot a kernel in an ubi partition This uboot also has a "recovery" feature, before booting from flash it will try to boot a initramfs image called "initramfs.bin" from a FAT32-formatted USB drive connected to the USB 2.0 port. (u-boot lacks drivers for usb 3.0 controllers) Just rename the initramfs image and place it on the usb drive, the uboot will load it. In case there is no USB drive or no such file is found, the uboot will boot from internal flash. The whole check takes less than a second, boot times are not impacted. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* kirkwood: sync image filename with boardnameMathias Kresin2018-01-092-37/+53
| | | | | | | | | | Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: use the generic board detectMathias Kresin2018-01-0910-119/+49
| | | | | | | Drop the target specific detection function in favour of the generic one provided by base-files. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: use image metadataMathias Kresin2018-01-092-21/+4
| | | | | | | Append and enforce image metadata. Remove the device specific image checks, they are replaced by image metadata. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-kirkwood: fix default u-boot selectionMathias Kresin2018-01-091-0/+2
| | | | | | | | | Build the Seagate GoFlexHome u-boot for the Seagate GoFlexNet as well. The name clearly indicates that the u-boot can be used for both boards Build the Zyxel NSA310 u-boot if the NSA310B image is selected. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: fix nsa310b compatible stringsMathias Kresin2018-01-091-1/+1
| | | | | | Use a destinct compatible string fro the nsa310b. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: fix compatible string in ib62x0 dtsMathias Kresin2018-01-092-0/+9
| | | | | | | | There is no point in being that specifc in a generic dts covering a range of boards. Keep only the the generic compat string to use it for a devicetree based boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: drop support for orphaned boardsMathias Kresin2018-01-098-330/+5
| | | | | | | No image build code for the Guruplug, Sheevaplug and NSA310S exists. Drop support for the boards for now. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: cleanup image build codeMathias Kresin2018-01-091-26/+8
| | | | | | | | | | | | | | Drop NAND_BLOCKSIZE, UBI_OPTS and UBIFS_OPTS. They are either used by not supported filesystems or by the legacy image build code. Add common used options/images to the default build code and override the options where necessary. Don't export the kernel image, it isn't required by any board. While at it, change the file extension for the sysupgrade images to bin. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ipq806x: drop kernel 4.4 leftoversMathias Kresin2018-01-0910-3628/+0
| | | | | | | | Remove the kernel 4.4 specific devicetree source files. Fixes: 3a3564ead5e4 ("ipq806x: remove v4.4 support") Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: fix Archer C7v4 5GHz MAC-addressDavid Bauer2018-01-091-1/+4
| | | | | | | | | | | The TP-Link firmware uses (primary_mac-1) as MAC-address for the 5GHz WiFi. This applies the same behaviour to LEDE. Currently, the MAC-address is retrieved from eth1, which does not exist on the Archer C7 v4. As a result from this, every C7 v4 with LEDE carries the same MAC-Address on the 5GHz WiFi. Signed-off-by: David Bauer <mail@david-bauer.net>
* 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: add missing soc compatibles to dtsMathias Kresin2018-01-092-2/+2
| | | | | | Add SoC compatibles where missing. Signed-off-by: Mathias Kresin <dev@kresin.me>
* 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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 04:04:20 +0000