aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* sdk: switch base feed url to git.openwrt.orgJo-Philipp Wich2018-01-041-1/+1
| | | | | | | As LEDE is rebranding to OpenWrt now, adjust the base feed Git reference accordingly. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* x86: preinit: use board_name on Sm Super ServersPhilip Prindeville2018-01-041-1/+8
| | | | | | | | | Supermicro puts "Super Server" into their product_name DMI value for a whole slew of products, making this value about as useful as not having been filled in at all. Instead, fall back on the board_name instead. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* x86: preinit: make name rewrite into reusable functionPhilip Prindeville2018-01-041-6/+10
| | | | | | | | There might be other places (such as vendor-supplied preinit scripts) where we wish to take a DMI name and clean it up in a consistent way, so make the sed command into a function. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* kernel: bump 4.14 to 4.14.11Stijn Tintel2018-01-0314-41/+42
| | | | | | | | | | | | | | | Rename unwinder config symbols to match upstream changes. Refresh patches. Update patch that no longer applies: 202-reduce_module_size.patch Also enable CONFIG_PAGE_TABLE_ISOLATION. This feature was backported from 4.15 to the 4.14 stable series. It is enabled by default, so enable it in OpenWrt as well. Compile-tested on x86/64. Runtime-tested on x86/64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: move CONFIG_KASAN to generic configStijn Tintel2018-01-027-4/+3
| | | | | | | | | | While bumping 4.14, the kernel build failed due to missing CONFIG_KASAN symbol. Move it to generic config instead of defining it for all arm64 and x86/64 targets. It was only added in 4.0, so not needed in config-3.18. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* layerscape: activate fpu featureHauke Mehrtens2018-01-021-1/+1
| | | | | | | | The CPU sub type was set to a CPU version with FPU, but the FPU feature was not activated before, so a soft float toolchain was created. Activate also the FPU feature to create the correct toolchain. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* at91: sama5: activate fpuHauke Mehrtens2018-01-021-0/+2
| | | | | | | This activates neon and VFPv4 support for this target. The CPU support these feature so also use them. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.9 to 4.9.73Kevin Darbyshire-Bryant2018-01-0212-69/+80
| | | | | | | | Refresh patches. Runtime tested: ar71xx - Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* bcm53xx: use iflag=skip_bytes for dd command during sysupgradeRafał Miłecki2017-12-291-2/+2
| | | | | | | | | | | Since BusyBox 1.25.0 dd command supports iflag=skip_bytes which allows skipping requested amount of bytes without reducing blocksize. Thanks to this we can leave default blocksize and let dd work more efficiently. On Netgear R6250 "dd skip=58 iflag=skip_bytes" can be 5 times faster than "dd bs=58 skip=1" when extracting TRX out of CHK. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* brcm47xx: image: build firmware for Asus WL-500g DeluxeRafał Miłecki2017-12-291-0/+8
| | | | | | | | It's a device based on BCM5365P (0x5365 package 0x00). This SoC has USB 1.1 controller but device has two USB 2.0 parts. They are handled by PCI-based controllers: 1106:3038 UHCI and 1106:3104 EHCI. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add early support for kernel 4.14Rafał Miłecki2017-12-2920-0/+1702
| | | | | | Don't switch to it by default yet as it requires more testing. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: fix Omega2 compatible stringMathias Kresin2017-12-293-1/+3
| | | | | | | Change the compatibel from Omega to Omega2 and add the compatible string where missing. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix widora neo diag ledMathias Kresin2017-12-291-2/+4
| | | | | | | The diag LED is named widora:orange:wifi and can't be derived from the boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix dts compatible stringThomas Nixon2017-12-292-2/+2
| | | | | | | | | | This was broken in 7bab49fd ("lantiq: add compatible strings to dts files"), causing for the dm200 garbled serial output during boot, and likely other issues. Signed-off-by: Thomas Nixon <tom@tomn.co.uk> [fix the compat string of the P2601HNFX as well] Signed-off-by: Mathias Kresin <dev@kresin.me>
* bcm53xx: make USB packages compatible with kernels 4.13+Rafał Miłecki2017-12-291-2/+6
| | | | | | In kernels 4.13+ modules are located in an extra "broadcom" subdir. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add upstream patch fixing SPI controller driverRafał Miłecki2017-12-294-127/+214
| | | | | | | | | | | | That patch fixes handling SPI messages with two writing transfers. It's important when using e.g. by m25p80 driver which uses one transfer for opcode and another one for data. Thanks to that fix we can now drop m25p80 workaround patch. It means one less hack and also a better flash writing performance as there is no more data buf copying. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ag71xx: Fix rx ring buffer stall on small packets flood on qca956x and qca953x.Vittorio Gambaletta2017-12-293-1/+22
| | | | | | Backported from Code Aurora QSDK Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
* x86: add NVMe support for motherboards w/ M.2 slotPhilip Prindeville2017-12-261-0/+3
| | | | | | | | A lot of 1U x86_64 servers have NVMe support, which is lower-power and higher speed than SSD or CFast drives, etc. The drivers required to make this work are trivial. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* kernel: bump 4.4 to 4.4.108Kevin Darbyshire-Bryant2017-12-261-1/+1
| | | | | | Refresh patches. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: bump 4.9 to 4.9.72Kevin Darbyshire-Bryant2017-12-2613-39/+39
| | | | | | | | Refresh patches. Runtime tested: ar71xx - Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* linux: unbreak host tools build for 4.14Jonas Gorski2017-12-251-1/+1
| | | | | | | | Remove a stray -Wp left in host_c_flags causing build failures for newer 4.14 versions. Reported-by: Michael Marley <michael@michaelmarley.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm2708: use x86's upgrade scripts for all rpi targetsChristian Lamparter2017-12-251-9/+93
| | | | | | | | | | | | | | | Advantages: - preserves existing partition layout on the sd-card. Only the boot and rootfs partition will be overwritten. Please note that sysupgrade will refuse to upgrade, if the existing installation has an incompatible partition layout. Future changes to the bootfs and/or rootfs partition size will likely cause breakage to the sysupgrade procedure. In these cases, the ext4-sdcard.img.gz will have to be written to the sdcard manually. Please don't forget to backup your configuration in this case. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* brcm2708: convert to dt-based board-detectionChristian Lamparter2017-12-256-71/+20
| | | | | | | | | | | | Use the values populated by the generic board detect function. The first compatible from the device tree source file will be the board name in userspace. The model property from the device tree source file will be the model name. Change the board name where used in the userspace and drop the target specific board detect, to use the generic one. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* brcm2708: add compatible stringsChristian Lamparter2017-12-251-0/+70
| | | | | | | | | | | | | | | | This patch adds the compatible string for the various RPIs from 4.14 upstream. Note: The 4.14 upstream does not include the compute modules. If the CM* would just house the SoC, it could in theory use the "raw" chip compatible string. However, these CM boards also come with RAM and eMMC. So they have to have a proper comaptible. For now, "raspberrypi,compute-module-{1|3}" will be good enough. Note2: The original CM was renamed to CM1 when CM3 was released. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* brcm2708: convert to metadataChristian Lamparter2017-12-252-17/+7
| | | | | | | | | | This patch converts all the raspberrypi images to utilize the common metadata-based image verification. Note: the CM1 and CM3 currently use the same "rpi-cm" boardname. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ar71xx: spi-rb4xx: balance clk_prepare_enable() callGabor Juhos2017-12-241-2/+2
| | | | | | | | | | | | | Commit c312cef223dd ("ar71xx: spi-rb4xx fix.") replaced the clk_enable() call with clk_prepare_enable() to meet the common clock framework requirements. However it did not change the clk_disable() call in the error patch which thus leads to imbalance. Fix the code by using the correct counterpart of clk_prepare_enable() in both places. Fixes: c312cef223dd ("ar71xx: spi-rb4xx fix.") Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* kernel/4.14: add missing newline character to UBI messagesGabor Juhos2017-12-242-3/+3
| | | | | | | | | | | | | | | A few UBI messages lacks the trailing newline character which leads to ugly lines in the bootlog like this: [ 6.649159] UBI error: no valid UBI magic found inside mtd6[ 6.667751] Freeing unused kernel memory: 2196K Add a newline character to the end of the messages to fix it. After the fix the line from above looks better in the log: [ 6.609182] UBI error: no valid UBI magic found inside mtd6 [ 6.627599] Freeing unused kernel memory: 2132K Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* kernel/4.9: add missing newline character to UBI messagesGabor Juhos2017-12-242-3/+3
| | | | | | | | | | | | | | | A few UBI messages lacks the trailing newline character which leads to ugly lines in the bootlog like this: [ 6.649159] UBI error: no valid UBI magic found inside mtd6[ 6.667751] Freeing unused kernel memory: 2196K Add a newline character to the end of the messages to fix it. After the fix the line from above looks better in the log: [ 6.609182] UBI error: no valid UBI magic found inside mtd6 [ 6.627599] Freeing unused kernel memory: 2132K Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* kernel/4.4: add missing newline character to UBI messagesGabor Juhos2017-12-242-4/+4
| | | | | | | | | | | | | | | A few UBI messages lacks the trailing newline character which leads to ugly lines in the bootlog like this: [ 6.649159] UBI error: no valid UBI magic found inside mtd6[ 6.667751] Freeing unused kernel memory: 2196K Add a newline character to the end of the messages to fix it. After the fix the line from above looks better in the log: [ 6.609182] UBI error: no valid UBI magic found inside mtd6 [ 6.627599] Freeing unused kernel memory: 2132K Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* kernel: bump 4.4 to 4.4.107Kevin Darbyshire-Bryant2017-12-2317-64/+64
| | | | | | | | | | Refresh patches. Update patch that no longer applied: oxnas/0072-mtd-backport-v4.7-0day-patches-from-Boris.patch Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Tested-by: Rosen Penev <rosenp@gmail.com>
* lantiq: remove DSL_ChipSetHWVersion from status informationMartin Schiller2017-12-231-4/+2
| | | | | | | | | | | | The value DSL_ChipSetHWVersion is fetched from the dsl frontend via the dsl_control service, but not really provided by the dsl frontend firmware and for now always "UNKNOWN". The lantiq support told us that this information wouldn't be provided in the foreseeable future, so let's remove this useless "UNKNOWN" information. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* ramips: fix Linkit smart 7688 supportMathias Kresin2017-12-233-24/+8
| | | | | | | | | | Use a more appropriate compatible string. Fix the wireless led GPIO and add the default wireless trigger. Use the wireless LED for boot state indication as well. Remove the GPIO pinmux for pins not exposed on the board. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for TP-Link TL-MR3420 v5Henryk Heisig2017-12-236-0/+109
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link TL-MR3420 v5 are simple N300 router with 5-port FE switch and non-detachable antennas. Its very similar to TP-Link TL-WR841N V13. Specification: - MT7628N/N (580 MHz) - 64 MB of RAM (DDR2) - 8 MB of FLASH - 2T2R 2.4 GHz - 5x 10/100 Mbps Ethernet - 2x external, non-detachable antennas - USB 2.0 Port - UART (J1) header on PCB (115200 8n1) - 8x LED, 2x button, power input switch Flash instruction: The only way to flash LEDE image in mr3420v5 is to use tftp recovery mode in U-Boot: 1. Configure PC with static IP 192.168.0.225/24 and tftp server. 2. Rename "lede-ramips-mt7628-tplink_tl-mr3420-v5-squashfs-tftp-recovery.bin" to "tp_recovery.bin" and place it in tftp server directory. 3. Connect PC with one of LAN ports, press the reset button, power up the router and keep button pressed for around 6-7 seconds, until device starts downloading the file. 4. Router will download file from server, write it to flash and reboot. Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* ramips: move common tplink image build code into own recipeMathias Kresin2017-12-231-8/+20
| | | | | | | | Move common tplink image build code into own recipe. Include the common parts instead of including a full build recipe and overwriting former set varaibles. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: move console loglevel to genericTomasz Maciej Nowak2017-12-232-1/+1
| | | | | | | Move CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7 to generic, to make it consistent across all targets. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* kernel: add missing config symbols for 4.14Stijn Tintel2017-12-211-0/+4
| | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ar71xx: add support for MikroTik RouterBOARD 921GS-5HPacD r2 (mANTBox 15s)Roger Pueyo Centelles2017-12-216-3/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the MikroTik RouterBOARD 921GS-5HPacD r2 (mANTBox 15s), an outdoor sector antenna with a built-in 802.11ac wireless router. Additionally, it adds a new profile for devices with >= 128 MB NAND flash and 802.11ac to the ar71xx/mikrotik subtarget. See https://mikrotik.com/product/RB921GS-5HPacD-15S for more info. Specifications: - SoC: Qualcomm Atheros QCA9558 (720 MHz) - RAM: 128 MB - Storage: 128 MB NAND - Wireless: external QCA9822 802.11a/ac 2x2:2 - Ethernet: 1x 1000/100/10 Mbps, integrated, via AR8031 PHY, passive PoE in - SFP: 1x host Working: - Board/system detection - NAND storage detection - Wireless - Ethernet - 1x user LED - Reset button - Sysupgrade Untested: - SFP cage (probably not working) Installation: - Boot initramfs image via TFTP and then flash sysupgrade image Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ar71xx: fix spelling in mach-rb922.cRoger Pueyo Centelles2017-12-211-1/+1
| | | | Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ar71xx: fix rb922gs_nand_scan_fixup()Roger Pueyo Centelles2017-12-211-1/+5
| | | | | | | | | Apply code from commits 9e1bc27e6d67fa29791eb0fac5e5f0066d12a761 (ar71xx: Fix UBIFS work on Mikrotik RB95x devices) and 665bb2749906aff4d4ec607a308353fa30cb1b3a (ar71xx: fix invalid pointer dereference in rb95x_nand_scan_fixup()) to RB92x devices too. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* apm821xx: convert to device-tree board detectionChristian Lamparter2017-12-2110-81/+41
| | | | | | | | | | | | | This patch converts all apm821xx devices to the device-tree board-detection method. All instances of the legacy boardnames (mbl,mr24,...) are converted to "vendor,device" identifier. The custom board-detection code in apm821xx.sh is removed as it no longer serves any purpose. Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: enable metadata for packagingChristian Lamparter2017-12-213-93/+10
| | | | | | | | | | This patch enables metadata-supported image verification for all apm821xx supported devices. Since this method comes with a built-in image verification tool (fwtool), the previous image checks can be removed. Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: align device names with vendor_device formatChristian Lamparter2017-12-211-10/+10
| | | | | | | | | | Currently, the device name handle does not include the manufacturer. This can make it hard do differentiate between products from different vendors that have the same product name. As the handle is used to derive the image name. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: dts: rename devices dts files to include the manufacturerChristian Lamparter2017-12-216-5/+5
| | | | | | | | | | | This patch rename all the DT source files in order to match upstream's "manufacturer-device.dts" format. Please note that the DEVICE_DTB isn't changed. This is because the u-boot of the MyBook Live defines the fdt_file variable to be "apollo3g/apollo3g.dtb". Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add product names to the dt compatible for MerakiChristian Lamparter2017-12-212-2/+2
| | | | | | | | | | Meraki choose to use their product's codename as the main compatible string. Mathias Kresin commented that this is a poor choice as this will confuse the users and devs once the device-tree compatible is used for board-detection and possible the image name. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: dts: append SoC compatible to DTSChristian Lamparter2017-12-214-2/+4
| | | | | | | | | | | | | | | | | | | | | This patch appends the "apm,bluestone" or "amcc,apollo3g" machine compatible string to the current device tree source. Please note that unlike other archs the PPC DT code does not regard the machine's compatible string as a priority list. This is explained in the kernel's usage-model.txt as follows: "PowerPC uses a slightly different scheme where it calls the .probe() hook from each machine_desc, and the first one returning TRUE is used. However, this approach does not take into account the priority of the compatible list, and probably should be avoided for new architecture support." For this reason, the "apm,bluestone" compatible string can't be added to the WNDR4700. As otherwise the target specific pci fix-up code will get ignored and this causes the ath9k WIFI to not get initialized. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: replace DEVICE_{PROFILE|NAME} with BOARD_NAMEChristian Lamparter2017-12-211-10/+6
| | | | | | | | | | | | | | | | | | | | | This patch sets the BOARD_NAME variable on each affected apm821xx device. The existing DEVICE_PROFILE and DEVICE_NAME assignments are deprecated as they no longer serve any purpose. The BOARD_NAME variable is used by the sysupgrade-tar method to specifiy a directory overwrite for the sysupgrade-$dir directory in the generated tar file. Keeping the original boardname in this context will be necessary for targets that utilize the sysupgrade-tar method. Otherwise, sysupgrade on an previous installation will not recognize the newly generated images. This step is necessary since an upcoming patch realigns the existing shortname for a device with a proper "manufacturer_device" identifier. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: replace whitespace with tabsChristian Lamparter2017-12-211-1/+1
| | | | Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: explicitly build the rootfs.img.gz targetChristian Lamparter2017-12-211-2/+2
| | | | | | | | | | | | | | | The commit 87b668765e1 ("image: when using the new image build code, gzip ext4 images by default") forced that all targets that select the ext4 as the root filesystem to always compress the generated rootfs. This is fine, but this method doesn't not allow to append the metadata on a per-target base. Therefore this patch changes the rootfs image production rule to generate the gzip step manually. This way the metadata can be appended at a later date. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ramips: fix devicetree compat stringsMathias Kresin2017-12-215-5/+5
| | | | | | | | | | | | "PandoraBox" is not the name of the manufacturer, it's a firmware made by the manufacturer actually. Their official English name is "D-Team". PBR-M1 is the only one they use "PandoraBox" as a brand name. Their other products are using "Newifi" as their trademark (including Y1 and Y1S which used to be OEM products for Lenovo). Signed-off-by: Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for newifi d2Jackson Ming Hu2017-12-216-0/+177
| | | | | | | | | | | | | | | | | | | | | | | | | | | Previously Newifi D2 could only use PandoraBox M1's firmware. It works fine, but LED GPIO is different. As a result, a separated DTS file for this device should be implemented. Hardware spec: * CPU: MTK MT7621A * RAM: 512MB * ROM: 32MB SPI Flash * WiFi: MTK MT7603+MT7612 * Button: 2 buttons (reset, wps) * LED: 3 single-color LEDs (USB, WiFi 2.4GHz, WiFi 5GHz) & 2 dual-color LEDs (Power, Internet) * Ethernet: 5 ports, 4 LAN + 1 WAN Installation method: Same as Newifi D1, users may need to request unlock code from the device manufacturer. Otherwise, a SPI flash programmer may be necessary to get the firmware flashed. After the device is unlocked, press and hold reset button before power cable plugs in. Then go to http://192.168.1.1 to upload and flash the firmware package. Signed-off-by: Jackson Ming Hu <huming2207@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-08 16:32:59 +0000