aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* ramips: preliminary support for 4.14Roman Yeryomin2018-02-1577-24/+27451
| | | | | | | | - removed upstreamed patches - 0901-spansion_nand_id_fix.patch is disabled, not clear if it's needed Signed-off-by: Roman Yeryomin <roman@advem.lv> Signed-off-by: John Crispin <john@phrozen.org>
* iwinfo: update to latest git HEADDaniel Golle2018-02-151-3/+3
| | | | | | 223e09b add support for expected throughput Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: fix reporting effective VLAN ID on MT7621 switchesJo-Philipp Wich2018-02-141-2/+21
| | | | | | | | | | | | On MT7621, the REG_ESW_VLAN_VTIM reads are undefined, causing swconfig to always report `vid: 0` in swconfig show output. Since a 4K VLAN table is used on this platform, the VLAN ID always correponds to the actual VLAN table index so provide a specific MT7621 implementation of the get_vid callback which returns the table index as VLAN ID. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: properly map pvid for vlans with remapped vid on mt7530/762x switchesJo-Philipp Wich2018-02-141-1/+7
| | | | | | | | | | | | | Currently, untagged port primary vlan IDs are set to the VLAN table index, and not the actual VLAN ID, breaking configurations with IDs deviating from the VLAN index. Fix the issue by resolving the per-port pvid property to the target VLAN ID value before committing to the hardware. Fixes FS#991, FS#1147, FS#1341 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: don't clobber vlans with remapped vid on mt7530/762x switchesJo-Philipp Wich2018-02-141-36/+53
| | | | | | | | | | | | | Avoid overwriting vlan entries with remapped vid in later iterations of the vlan enumeration loop of mt7530_apply_config(). Fix the problem by refactoring the code to first reset the entire table, then reprogram only vlans with members to prevent overwriting configured vlans with unconfigured ones. Fixes FS#1147, FS#1341 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* at91: fix image building with CONFIG_TARGET_MULTI_PROFILEJo-Philipp Wich2018-02-143-16/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current image build code has a number of race conditions and interface contract violations in the custom image build steps: - Build/install-zImage, solely used by at91, relies on $(PROFILE_SANITIZED) which is not available when building with CONFIG_TARGET_MULTI_PROFILE - Build/at91-sdcard, which may run concurrently, creates scratch files at fixed locations and manipulates target files directly which can lead to file corruption and other unexpected failures Rename the install-zImage macro to at91-install-zImage and move it to the at91 image Makefile since this target is the sole user. Also utilize "$@" as output file name and switch the usage of $(PROFILE_SANITIZED) to $(DEVICE_NAME) in order to fix naming under multi profile builds. Fix the at91-sdcard macro to construct scratch file paths relative to "$@", which is guaranteed to be unique and store the final artifact output in "$@" as well, instead of inside $(BIN_DIR). The generic image build code takes care of moving a build steps "$@" output to the final destination in a concurrency-safe manner. Finally remove the broken install-zImage from the generic image-commands Makefile. Fixes: d7a679a036 ("at91: Install zImage.") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mediatek: bump to v4.14John Crispin2018-02-1491-19755/+1482
| | | | | | | This drops support for all the !emmc EVB and adds banannaPi-R2 Also drop mtkhnat until the nftables offoad driver is ready Signed-off-by: John Crispin <john@phrozen.org>
* ipq806x: add support for GL.iNet GL-B1300Dongming Han2018-02-148-2/+341
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for GL.iNet GL-B1300 Specification: - SOC: IPQ4028 / QCA Dakota - RAM: 256 MiB - FLASH: 32 MiB - ETH: Qualcomm Atheros QCA8075 Gigabit Switch (2 x LAN, 1 x WAN) - USB: 1 x 3.0 (via Synopsys DesignWare DWC3 controller in the SoC) - WLAN1: Qualcomm Atheros QCA4028 2.4GHz 802.11bgn 2:2x2 - WLAN2: Qualcomm Atheros QCA4028 5GHz 802.11a/n/ac 2:2x2 - INPUT: one reset and one WPS button - LEDS: 3 leds: Power, WIFI(only for 2.4G currently), and one reserved - UART: 1 x UART on PCB (3.3V, TX, RX, GND) - 115200 8N1 Installation: Method 1: - use serial port to stop uboot - uboot command: run lf Method 2: - push down reset button and power on - wait until three leds constantly on then release - upgrade by uboot web at http://192.168.1.1 Note: - the sysupgrade image need to be renamed to lede-gl-b1300.bin in both method. - the sysupgrade image can be automatically downloaded if tftp server at 192.168.1.2 have that file. - the wifi led will be flashing when writing image. Signed-off-by: Dongming Han <handongming@gl-inet.com>
* ubox: update to latest git HEADJohn Crispin2018-02-142-3/+3
| | | | | | | | | | 128bc35 logread: fix reconnect logd logic 66347ec logread: move the code setting up the request blob out of the main loop 975a258 logread: move output connection setup code out of main loop b81bea7 logread: cleanup pid file handling d73e7d2 ubox: Replace strerror(errno) with %m format. Signed-off-by: John Crispin <john@phrozen.org>
* archs38: add HSDK boardEvgeniy Didin2018-02-143-4/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Synopsys DesignWare HSDK (which stands for ARC HS Development Kit) is the latest and greatest development platform that sports quad-core ARC HS38 in real silicon. Most noticeable features of the board are: * Quad-core ARC HS38 CPU running at 1GHz * 4Gb of DDR * Built-in Vivante GPU (well supported via open source Etnaviv drivers) * Built-in Wi-Fi/Bluetooth module (RedPine RS-9113) And as usual we have: * [micro] SD-card slot * 2 USB 2.0 ports * 1Gbit Ethernet port * Built-in Digilent JTAG probe * Serial port accessible via micro-USB port For more information about HSDK board visit: https://www.synopsys.com/dw/ipdir.php?ds=arc-hs-development-kit Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> CC: Alexey Brodkin <abrodkin@synopsys.com> CC: Hauke Mehrtens <hauke@hauke-m.de> CC: John Crispin <john@phrozen.org>
* archs38: switch to kmod-usb2Evgeniy Didin2018-02-141-1/+1
| | | | | | | | | | | We have managed to get USB 2.0 working good enough on all archs38 platforms so we're ready to switch to much faster USB 2.0. Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> CC: Alexey Brodkin <abrodkin@synopsys.com> CC: Hauke Mehrtens <hauke@hauke-m.de> CC: John Crispin <john@phrozen.org>
* generic: swconfig: reduce lock duration on sysfs filesKevin Darbyshire-Bryant2018-02-141-8/+12
| | | | | | | | sysfs attributes 'port_mask' & 'speed_mask' held locks whilst doing mundane tasks such as sprintf. Refactor code to reduce length of time locks are held unnecessarily. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* generic: swconfig: add mode led attributeKevin Darbyshire-Bryant2018-02-141-12/+125
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add sysfs 'mode' attribute to swconfig controlled LEDs. swconfig 'link state' LEDs blink in the presence of port traffic. This behaviour becomes more obvious as switches start to support get_port_stats() e.g. commits 0369e358916ef092a1644334f5dd1412051b68a4, 3056d09b4046e0eb0f6de0f3f5432cd9fa86fc51, 4ddbc43cc15c2fa128a2f169964ef7eb508cf2c5, 4d8a66d9346373c2a7fcac5bdae3f662a9dbd9df. This blinking can be confusing/distracting if the switch has other LEDs used to indicate traffic. Provide a 'mode' sysfs attribute that controls the blink on traffic behaviour. mode - either "none" (LED is off) or a space separated list of one or more: link: LED's normal state reflects whether the link is up (has carrier) or not tx: LED blinks on transmitted data rx: LED blinks on receive data Note that 'link' considers any port speed mask that may be applicable. e.g. if an LED is configured to indicate 1Gbit link speed and mode is set to 'link rx tx' but the port is connected at 100Mbit then the LED will not light or blink. A mode of 'tx rx' will blink in the presence of traffic only if the port matches the rate (if configured) This maintains compatibility with existing behaviour. Attribute is 'link tx rx' by default for backwards compatible behaviour. Many thanks to Thibaut Varene for providing a more sensible led_event routine after I had mangled the original, and other coding style hints. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Acked-by: Thibaut VARENE <hacks@slashdirt.org>
* mwlwifi: downgrade to version 10.3.4.0-20180118Hauke Mehrtens2018-02-132-58/+6
| | | | | | | Some people reported problems with the current development version, so go back to the latests more or less release. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mwlwifi: fix compile problem with kernel 4.14Hauke Mehrtens2018-02-131-0/+92
| | | | | | | vfs_write() is not exported on kernel 4.14 any more and kernel_write() should be used instead. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mwlwifi: use PKG_SOURCE_DATE instead of versionHauke Mehrtens2018-02-131-2/+2
| | | | | | | | | Using PKG_SOURCE_DATE instead of PKG_VERSION will make the build system generate the version based on the date and the git hash. This way the tar file name changes when the git hash changes and this avoids problems when someone forgets to change the version, but changes the git hash. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mwlwifi: Update to latest commit 20180208Chris Breuer2018-02-131-3/+3
| | | | | | | | | | | | | | | | | | | Changes since last merge into OpenWrt since 2017-12-14: - Added debugfs file tx_hist. - Added debugfs file fixed_rate. - Added debugfs file ba_hist. - Modified the way to establish BA stream. - Added code to control BF type. - Added functions to check/dump dhcp packet. - Upgrade 88W8964 firmware to 9.3.2.4. - Added debugfs file coredump. - Corrected the way to transmit multicast packets. - Change driver version to 10.3.4.0-20180118. - Corrected the way to get qos control. - Assigned broadcast dhcpoffer to another queue. - Separated broadcast and multicast packets. Bump to latest commit 20180206 Signed-off-by: Chris Breuer <github@chrisbreuer.de>
* mvebu: Migrate uci config to new PCIe pathHauke Mehrtens2018-02-131-0/+41
| | | | | | | | | | | | | | | | | | | | The name of the PCIe controller node in device tree changed between kernel 4.9 and kernel 4.14. Migrate the configuration when an update from kernel 4.9 to 4.14 or back is done to the new name to make the existing wifi configuration compatible with the new names. This replaces the "pcie-controller" part with "pcie" on all nodes if the file exists in sys fs. This is not done in the uci-defualts, because they are getting executed to late in the boot process. The kernel module gets loaded before the uci-defaults scripts are executed. When the mwlwifi driver gets loaded it will trigger an event via hotplug to detect new devices and as the paths are not in the uci configuration they will be added again. When the migration is done before the script will detect that they are already there. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: Add support for kernel 4.14Hauke Mehrtens2018-02-1329-0/+3893
| | | | | | | | | | Add support for kernel 4.14 to the mvebu target. This also replaces the old sfp and phylink patches with new versions from Russell's clearfog-4.13 branch http://git.arm.linux.org.uk/cgit/linux-arm.git/log/?h=clearfog-4.13 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: move files to files-4.9 and files-4.4 folderHauke Mehrtens2018-02-134-0/+568
| | | | | | | | This is needed to prevent copying it into kernel 4.14. These device tree files are already integrated into kernel 4.14 and we would like to use the upstream versions only. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211: move wifi detect hotplug script to laterHauke Mehrtens2018-02-131-2/+2
| | | | | | | | | Make it easily possible to add a custom script in front of this hotplug script which adds new devices. This is needed for the mvebu target in which we want to migrate the old configuration before new devices are getting detected. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: ubifs: create use file system format 4 by defaultHauke Mehrtens2018-02-132-0/+64
| | | | | | | | | | | | | | | | | | | Instead of creating an ubifs file system with format version 5 by default on empty UBI volumes use the older format 4 by default. This will make it possible to mount these file systems also on older kernel versions. When a user wants to do a sysupgrade from kernel 4.14 to kernel 4.9 the old kernel has to read the file system created by the more recent kernel which currently does not work for ubifs. This fixes the problem by creating file systems which are compatible with older kernel versions by default. Kernel 4.14 will still be able to read and write UBI FS file system version 5, it will just not be used when a ubifs partition is created implicitly on an empty UBI volume. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Add missing config optionsHauke Mehrtens2018-02-131-0/+5
| | | | | | These were found when compiling the new octeontx target. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm63xx: drop root parameter from cmdlineJonas Gorski2018-02-1388-88/+88
| | | | | | | | | | | The root= parameter overrides the automatic rootfs detection by partition name, so drop it. Fixes boot from flash after renumeration changes of partitions due to parser changes. Fixes FS#1350. Fixes: a27d59bb4274 ("brcm63xx: switch to new partition layout specification") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* target.mk: let profile remove from DEFAULT_PACKAGESPhilip Prindeville2018-02-131-0/+2
| | | | | | | In a profile, specifying -pkg in the list of PACKAGES will suppress it even if it appears in the target's DEFAULT_PACKAGES list. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* ipq806x: switch to full dual-boot for the nbg6817 sysupgrade supportStefan Lippers-Hollmann2018-02-131-3/+23
| | | | | | | | | | | | | | Instead of writing to the currently booted partition set, this implements full dual-boot support for sysupgrade by always writing to the other, currently inactive, partition set and toggling the dualflag after a successful flash. The currently active/ booted partition set is determined by parsing /proc/cmdline for its rootfs parameter (supplied by the DTS), instead of reading from the 0:DUAL_FLAG mtd, in order to prevent (potentially) bricking both partition sets. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: request the first free loop device dynamically for the nbg6817 ↵Stefan Lippers-Hollmann2018-02-131-4/+5
| | | | | | | | | | | | sysupgrade Instead of hardcoding /dev/loop0, it's safer to query for the first free loop device and assign that dynamically. While /dev/loop0 is a reasonable assumption immediately following "losetup --detach-all", detaching the mounted overlay is no longer strictly necessary once dual-boot support has been added for the nbg6817. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: use absolute the device path in $kernel for the nbg6817 sysupgradeStefan Lippers-Hollmann2018-02-131-4/+4
| | | | | | | Harmonize the variable usage for $kernel and $rootfs to always contain the full device path, instead of just its basename. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: support new location of USB PHY kernel moduleLuis Araneda2018-02-131-1/+3
| | | | | | | PHY drivers were grouped into vendor specific directories by upstream commit 0b56e9a7e8358e59b21d8a425e463072bfae523c Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* i2c.mk: sort kernel modulesLucian Cristian2018-02-131-62/+66
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* hwmon.mk: sort kernel modulesLucian Cristian2018-02-131-100/+109
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* can.mk: sort modulesLucian Cristian2018-02-131-95/+96
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* crypto.mk: sort kernel modulesLucian Cristian2018-02-131-347/+359
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* fs.mk: sort kernel modulesLucian Cristian2018-02-131-69/+77
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* firewire.mk: sort kernel modulesLucian Cristian2018-02-131-14/+16
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* build: cleanup leftover qconf filesAlif M. Ahmad2018-02-131-1/+1
| | | | | | | | | | ``make xconfig`` toplevel target will invoke ``make qconf`` inside ./scripts/config directory, which results a ``qconf`` executable. This commit removes leftover ``qconf`` executable during ``make config-clean``. Signed-off-by: Alif M. Ahmad <alive4ever@live.com>
* ar71xx: add more registers to ar71x_regs.hJulien Dusser2018-02-133-11/+388
| | | | | | | | | | Add more registers and flags to ar71x_regs.h for QCA955x and QCA956x SoCs. Values come from Qualcomm Atheros u-boot code. Patches can be merged into 622-MIPS-ath79-add-more-register-defines-for-QCA956x-SoC.patch Signed-off-by: Julien Dusser <julien.dusser@free.fr>
* ramips: add support for D-Link DAP-1522 A1George Hopkins2018-02-138-10/+174
| | | | | | | | | | | | | | | | | | D-Link DAP-1522 is a wireless bridge/access point with 4 LAN ports and a dual-band wireless chipset. Specifications: - Ralink RT2880 - 32 MB of RAM - 4 MB of Flash - 4x 10/100/1000 Mbps Ethernet (RTL8366SR) - 802.11abgn (RT2850) Flash Instructions: 1. Download lede-ramips-rt288x-dap-1522-a1-squashfs-factory.bin 2. Open the web interface and upload the image Signed-off-by: George Hopkins <george-hopkins@null.net>
* mtd: add fixwrg commandGeorge Hopkins2018-02-134-3/+233
| | | | | | Add a command to fix WRG headers, based on wrgg.c. Signed-off-by: George Hopkins <george-hopkins@null.net>
* kernel: mtdsplit: split by WRG headerGeorge Hopkins2018-02-131-3/+18
| | | | | | | Support splitting WRG images, which can be found in older D-Link devices. Signed-off-by: George Hopkins <george-hopkins@null.net>
* kernel: add missing symbolJohn Crispin2018-02-132-0/+2
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* uqmi: bump package releaseKoen Vandeputte2018-02-131-1/+1
| | | | | | fixes: da8990e717e1 ("uqmi: use built-in command for data-link verification") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: Add eTactica EG-200 supportKarl Palsson2018-02-1313-1/+140
| | | | | | | | | | | | | | EG-200 is a DIN rail mountable device with one ethernet port, wifi, an RS-485 port, and an internal USB attached uSD card reader. Two leds, "modbus" and "etactica" are managed by userspace applications in factory firmware. Flash instruction: Original firmware is based on OpenWrt. Use sysupgrade image directly in vendor GUI. Signed-off-by: Karl Palsson <karlp@etactica.com>
* uqmi: use built-in command for data-link verificationKoen Vandeputte2018-02-131-1/+19
| | | | | | | | | | | uqmi contains a command for directly querying the modem if there is a valid data connection, so let's use it. This avoids the cases were all previous tests are succesful, but the actual data link is not up for some reasons, leading to states were we thought the link was up when it actually wasn't .. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* uqmi: use correct value for connection checkingKoen Vandeputte2018-02-131-4/+8
| | | | | | | | | | | | | | Originally, the implementation only checked if uqmi command execution succeeded properly without actually checking it's returned data. This lead to a pass, even when the returned data was indicating an error. Rework the verification to actually check the returned data, which can only be correct if the uqmi command itself also executed correctly. On command execution success, value "pdh_" is a pure numeric value. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* uqmi: use general method for state cleaningKoen Vandeputte2018-02-131-10/+4
| | | | | | | | | | Debugging shows that using the general method properly cleans on each run, while the method specifying the client-ID shows "No effect" even while in connected state. Fixes several connectivity issues seen on specific modems. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: use new image build code for WHR-G300NINAGAKI Hiroshi2018-02-132-42/+21
| | | | | | | | The tftp.bin image for Buffalo WHR-G300N was not built, so I was fixed it after rewriting to new image build code. And the code for factory-EU.bin was broken, so I deleted it. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mediatek: remove the CPU_SUBTYPEJohn Crispin2018-02-131-1/+0
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* cns3xxx: remove linux 4.9 supportKoen Vandeputte2018-02-1329-1607/+13
| | | | | | | | - Remove kernel 4.9 support - Apply specific 4.14 changes directly to source - Refreshed all Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* target: Remove nomips16 option.Rosen Penev2018-02-131-3/+1
| | | | | | There is no target with a CPU subtype of nomips16. Signed-off-by: Rosen Penev <rosenp@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-08 12:59:53 +0000