aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* ramips: add support for Vonets VAR11N-300Andrew Crawley2017-12-215-1/+105
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The VAR11N-300 is a tiny wireless-N device with a hardwired Ethernet cable, one extra Ethernet port, and an internal antenna, based on the MediaTek MT7620n chipset. Specs: - MT7620n WiSoC @ 600MHz - 32 MB SDRAM - 4 MB SPI flash - 2T2R 2.4GHz WiFi-N - 1 attached 10/100 Ethernet cable (LAN) - 1 10/100 Ethernet port (WAN) - 1 attached USB / barrel 5vdc power cable - 5 LEDs (see notes below) - 1 reset button - 1 UART (3 pads on board) Installation: The stock firmware does not support uploading new firmware directly, only checking the manufacturer's site for updates. This process may be possible to spoof, but the update check uses some kind of homebrew encryption that I didn't investigate. Instead, you can install via a backdoor: 1. Set up a TFTP server to serve the firmware binary (lede-ramips-mt7620-var11n-300-squashfs-sysupgrade.bin) 2. Factory reset the device by holding the reset button for a few seconds. 3. Open the web interface (default IP: 192.168.253.254) 4. Log in with the "super admin" credentials: username `vonets`, password `vonets26642519`. 5. On the "Operative Status" page, click the text "System Uptime", then quickly click the uptime value. 6. If successful, an alert dialog will appear reading "Ated start", and the device will now accept telnet connections. If the alert does not appear, repeat step 5 until it works (the timing is a bit tricky). 7. Telnet to the device using credentials "admin / admin" 8. Retrieve the firmware binary from the tftp server: `tftp -l lede.bin -r lede-ramips-mt7620-var11n-300-squashfs-sysupgrade.bin -g <tftp-server-ip>` 9. Write the firmware to flash: `mtd_write write lede.bin /dev/mtd4` 10. Reboot Tested: - LAN / WAN ethernet - WiFi - LAN / WAN / status LED GPIOs (see notes below) - Reset button - Sysupgrade Notes: LEDs: The board has 5 LEDs - two green LEDs for LAN / WAN activity, one blue LED for WiFi, and a pair of "status" LEDs connected to the same GPIO (the blue LED lights when the GPIO is low, and the green when it's high). I was unable to determine how to operate the WiFi LED, as it does not appear to be controlled by a GPIO directly. Recovery: The default U-boot installation will only boot from flash due to a missing environment block. I generated a valid 4KB env block using U-boot's `fw_setenv` tool and wrote it to flash at 0x30000 using an external programmer. After this, it was possible to enter the U-boot commandline interface and download a new image via TFTP (`tftpboot 81b00000 <image-filename>`), but while I could boot this image sucessfully (`bootm`), writing it to flash (`cp.linux`) just corrupted the flash chip. The sysupgrade file can be written to flash at 0x50000 using an external programmer. Signed-off-by: Andrew Crawley <acrawley@gmail.com>
* ramips: add helper variable for boardnameMathias Kresin2017-12-212-224/+226
| | | | | | | | | | | | | Add a helper variable which contains the boardname separated from the vendor name. It allows to switch to a device tree compatible string based boardname, by keeping the $board:colour:function syntax in scripts handling/adding config for LEDs. Boards not using the device tree compatible string as based boardname are unaffected by the change, since none of them uses a comma in the boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: sync image filename with boardnameMathias Kresin2017-12-213-4/+9
| | | | | | | | | | | | | Use <manufacturer>_<modelname> as image name for board using the devicetree compat string as boardname. Replace the underline of the device define, to keep the SUPPORTED_DEVICES in sync with a devicetree compat string based boardname. Override the default SUPPORTED_DEVICES for board which are having an userspace boardname with an underline. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fallback to generic board detectMathias Kresin2017-12-214-15/+7
| | | | | | | Fallback to the generic board detection if no case for the current board exists. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: drop LinkIt Smart 7688 Duo userspace supportMathias Kresin2017-12-214-13/+3
| | | | | | | | | | The LinkIt Smart 7688/LinkIt Smart 7688 Duo are identical beside the extra ATmega32U4 - accessible via UART - on the the Duo. Since all relevant hardware is identical, drop the Duo special handling in userspace. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: Update kernel 4.9 to 4.9.70Hauke Mehrtens2017-12-1930-262/+172
| | | | | | Runtime tested on lantiq. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: fix polarity in gpio-export nodeMathias Kresin2017-12-1811-16/+11
| | | | | | | | If we need to set the initial output value to GPIOF_OUT_INIT_HIGH (1) to enable something, the pin is ACTIVE_HIGH. The same applies to GPIOF_OUT_INIT_LOW (0) and ACTIVE_LOW. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: fix lan ports on ens202extMarty E. Plummer2017-12-181-0/+1
| | | | | | | | | In the stock firmware both eth0 and eth1 are set to br-lan, add this behavior to our images. Fixes: FS#1084 Signed-off-by: Marty E. Plummer <hanetzer@protonmail.com>
* brcm63xx: fix Sercomm AD1018 status ledJonas Gorski2017-12-171-1/+1
| | | | | | | | The status led part was missed when changing the board name to *-nor. Fixes: e12c72bb52eb ("brcm63xx: Add Sercomm AD1018 support") Reported-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* lantiq: sync image filename with boardnameMathias Kresin2017-12-162-185/+227
| | | | | | | | | | | | | 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. While at it, normalise the image filenames by using only lower case characters and bin as file extension for sysupgrade images. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: drop unused variable from image build codeMathias Kresin2017-12-161-3/+0
| | | | | | | Remove the DEVICE_PROFILE variable. The variable isn't used at all. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use the generic board detectMathias Kresin2017-12-161-19/+0
| | | | | | | Drop the target specific detection function in favour of the generic one provided by base-files. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add missing model namesMathias Kresin2017-12-161-0/+1
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: remove the former board name from device tree modelMathias Kresin2017-12-1660-60/+60
| | | | | | | Remove the former used board name from the device model property and use the model name as it is. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use the compatible string as board nameMathias Kresin2017-12-169-67/+131
| | | | | | | | | | | Use the first compatible string as board name in userspace. Add the new board name as well as the former used board name to the image metadata to keep compatibilty with already deployed installations. Don't add the former used boardname for boards which exists only in master or evaluation boards. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: drop SoC name from eval boards compatible stringMathias Kresin2017-12-1611-11/+11
| | | | | | Keep it in the same format as used for the other eval boards. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add compatible strings to dts filesMathias Kresin2017-12-1653-0/+59
| | | | | | The compatible string is mandetory for devicetree source file. Signed-off-by: Mathias Kresin <dev@kresin.me>
* x86: Add support for kernel 4.14Hauke Mehrtens2017-12-169-16/+710
| | | | | | | | This adds basic support for kernel 4.14, this was tested in qemu only. The subtarget configuration was refresh with kernel 4.14 and the options needed to make it compile on kernel 4.9 were added manually. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: add kmod-crypto-ecdhHauke Mehrtens2017-12-162-0/+50
| | | | | | | | | | In kernel 4.14 kmod-bluetooth depends on kmod-crypto-ecdh, add kmod-crypto-ecdh to LEDE. Both packages also depend on the kmod-crypto-kpp package. To build this we have to fix the dependency of CRYPTO_ECDH which has a typo. This patch is already accepted upstream. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: generic: Add kernel 4.14 supportHauke Mehrtens2017-12-16131-8/+25622
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds initial support for kernel 4.14 based on the patches for kernel 4.9. In the configuration I deactivated some of the new possible security features like: CONFIG_REFCOUNT_FULL CONFIG_SLAB_FREELIST_HARDENED CONFIG_SOFTLOCKUP_DETECTOR CONFIG_WARN_ALL_UNSEEDED_RANDOM And these overlay FS options are also deactivated: CONFIG_OVERLAY_FS_INDEX CONFIG_OVERLAY_FS_REDIRECT_DIR I activated this: CONFIG_FORTIFY_SOURCE CONFIG_POSIX_TIMERS CONFIG_SLAB_MERGE_DEFAULT CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED I am not sure if I did the porting correct for the following patches: target/linux/generic/backport-4.14/020-backport_netfilter_rtcache.patch target/linux/generic/hack-4.14/220-gc_sections.patch target/linux/generic/hack-4.14/321-powerpc_crtsavres_prereq.patch target/linux/generic/pending-4.14/305-mips_module_reloc.patch target/linux/generic/pending-4.14/611-netfilter_match_bypass_default_table.patch target/linux/generic/pending-4.14/680-NET-skip-GRO-for-foreign-MAC-addresses.patch Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: refresh configurationHauke Mehrtens2017-12-163-16/+3
| | | | | | | Just refresh the kernel configuration, some options are removed because they are now in the generic kernel configuration. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: generic: add some more 4.9 configure optionsHauke Mehrtens2017-12-161-0/+9
| | | | | | | These are taken from the x86 target and should make support kernel 4.9 and 4.14 in the x86 target easier. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: add on-chip thermal sensors and cpuid supportPhilip Prindeville2017-12-162-1/+33
| | | | | | | | | | | Cover temperature sensors for all mainstream 64-bit processors, including AMD 10h and 15h families, Intel iCore, Xeon, Atom, and Via Nano. Also add CPUID support for user-space applications to detect CPU type. Include the on-chip sensors for 64-bit CPU's in the generic profile in case someone builds a 32-bit kernel to run on a Xeon SoC, etc. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* x86: refresh settings for 4.9.59Philip Prindeville2017-12-161-7/+1
| | | | Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* brcm63xx: backport mdio-bus reset gpio supportJonas Gorski2017-12-1613-96/+416
| | | | | | | Backport the mdio-bus reset gpio support from 4.12 and use it instead of toggling the reset ourself. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: backport enet cleanup patchesJonas Gorski2017-12-1614-36/+415
| | | | | | Align with upstream version, mostly non-fixes and small clean ups. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: register serial through device treeJonas Gorski2017-12-16167-363/+1144
| | | | | | | Register serial consoles through device tree instead of through board data. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: add uart nodesJonas Gorski2017-12-1610-0/+224
| | | | | | | Now that we can register uarts through device-tree, add them to the dtsi files. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: add clkdev lookup supportJonas Gorski2017-12-1617-73/+793
| | | | | | | Add clockdev lookup support for easier providing of clocks for devices. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: Add Sercomm AD1018 supportDaniel Gonzalez Cabanelas2017-12-167-0/+251
| | | | | | | | | | | | | | | | | | | | Add support for the Sercomm AD1018 router This a BCM6328 based board, 128 MB RAM, 128 MiB NAND flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port (not soldered). The board also has an FXS chip (Si32177) connected via SPI (SS2#), without support in LEDE. Since NAND flash chips aren't still supported in brcm63xx, the support is for now added to work only with SPI flash chips. Therefore hardware modding, soldering a new SPI flash chip, is required to make the board work with LEDE (tested and working OK). The flash at dts is intentionally left without partitioning to let the user choose a NOR chip of any size (8, 16 or 32 MB). Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: renamed ad1018 to ad1018-nor to signify the modification] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* at91: create sdcard image for sama5Sandeep Sheriker Mallikarjun2017-12-162-0/+79
| | | | | | | | | create sdcard image using gen_at91_sdcard_img.sh for sama5 platform and sdcard image partition layout is: P0: Boot (fat32) - contains(at91bootstrap,u-boot,zImage & dtb) p1: Rootfs (ext4) Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* ar71xx: fix invalid pointer dereference in rb95x_nand_scan_fixup()Gabor Juhos2017-12-161-0/+4
| | | | | | | | | | | | Since Linux 4.6, mtd->priv no longer points to the NAND specific structure. Under 4.9 it contains NULL, thus using it to access chip->options causes an invalid pointer dereference (FS#1200). Update the code to use the mtd_to_nand() helper under 4.9 to obtain the address of the chip specific data. Fixes: 7bbf4117c6fe ("ar71xx: Add kernel 4.9 support") Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* ar71xx: fix invalid pointer dereference in c60_nand_scan_fixup()Gabor Juhos2017-12-151-0/+4
| | | | | | | | | | | | | | | | Since Linux 4.6, mtd->priv no longer points to the NAND specific structure. Under 4.9 it contains NULL, thus using it to access the fields of the nand_chip structure causes an invalid pointer dereference. Update the code to use the mtd_to_nand() helper under 4.9 to obtain the address of the chip specific data. Compile tested only. Fixes: 7bbf4117c6fe ("ar71xx: Add kernel 4.9 support") Signed-off-by: Gabor Juhos <juhosg@freemail.hu> Tested-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: fix compiler warning in mtdsplit_minor.c under 4.4Gabor Juhos2017-12-151-0/+11
| | | | | | | | | | | | | | | | | | When mtdsplit_minor.c is compiled under Linux 4.4, the compiler drops the following warning: CC drivers/mtd/mtdsplit/mtdsplit_minor.o drivers/mtd/mtdsplit/mtdsplit_minor.c:106:14: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types] .parse_fn = mtdsplit_parse_minor, ^ drivers/mtd/mtdsplit/mtdsplit_minor.c:106:14: note: (near initialization for 'mtdsplit_minor_parser.parse_fn') The second parameter of the parser function must not have a 'const' qualifier in 4.4. The 001-mtdsplit_backport.patch removes the qualifier from other partition parsers. Update it to handle mtdsplit_minor.c as well. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* ar71xx: fix LED name typo for GL-AR300Mkyson Lok2017-12-151-1/+1
| | | | | | It shouldn't use double colon characters. Signed-off-by: kyson Lok <kysonlok@gmail.com>
* Revert "ar71xx: TL-WR1043N v4/v5: add orange WAN LED support"John Crispin2017-12-141-19/+3
| | | | | | | | | | This reverts commit 256990cbc0157feb8a9f37efeebf0330ab73727f. this commit caused a compile error "TL_WR1043_V5_GPIO_LED_WANORANGE" is undefined. Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx: TL-WR1043N v4/v5: add orange WAN LED supportTim Thorpe2017-12-141-3/+19
| | | | | | | Add missing definitions for the orange WAN LED on the TL-WR1043N(D) v4 and v5. Minor format correction on a constant for consistency. Signed-off-by: Tim Thorpe <tim@tfthorpe.net>
* ar71xx: generate BR region-code factory image for TP-Link TL-WR940NHenryk Heisig2017-12-141-1/+2
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* ar71xx: Fix switch port numbering on MIkrotik RB951Ui-2nD and RB493GJoão Chaínho2017-12-141-4/+4
| | | | | | | This patch fixes the switch port numbering on Mikrotik RB951Ui-2nD (hAP). Also fixes the switch port numbering shown on LuCI for Mikrotik RB493G. Signed-off-by: João Chaínho <joaochainho@gmail.com>
* apm821xx: use x86's upgrade scripts for MyBook LiveChristian Lamparter2017-12-142-19/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | Advantages: - preserves existing partition layout. On the hard-drive. Only the boot and rootfs partition will be overwritten. Disadvantages: - The upgrade process takes much longer to run. from 2-3 seconds to 15-25 seconds. 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-rootfs.img.gz has to be written manually onto the disk. Please don't forget to backup your configuration in this cases. Note2: This patch requires "base-files: upgrade: make get_partitions() endian agnostic" Note3: If your current installation does not host the two changes, sysupgrading will wipe the existing partition layout. Don't forget to backup your data! Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: MyBook Live convert to DT PHYChristian Lamparter2017-12-142-0/+12
| | | | | | Changes MyBook Live to use DT PHY probing and the broadcom phy driver. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: convert to dt based diag LED scriptChristian Lamparter2017-12-145-31/+49
| | | | | | | | | | | Please note that users with a Netgear WNDR4700 will need to update the device-tree partition manually. For instructions, please refere to commit 49856a4bb581 ("apm821xx: make it possible to update the dtb partition on the WNDR4700") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* base-files: unify get_dt_led helper functionChristian Lamparter2017-12-145-40/+14
| | | | | | | | | | | | | | Lantiq and IPQ806X (which includes IPQ40XX) both define the same custom function {ipq806x|lantiq}_get_dt_led. This patch moves the function into the base-file package at lib/functions/leds.sh to make it more accessible for other targets as well. Cc: Mathias Kresin <dev@kresin.me> Cc: John Crispin <john@phrozen.org> Cc: Hannu Nyman <hannu.nyman@iki.fi> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* brcm63xx: fix an OOPS when accessing the basemode register on 6368Jonas Gorski2017-12-131-1/+1
| | | | | | | | | | The bcm6368 pinctrl driver passed the wrong variable to devm_regmap_field_alloc, causing it to blow up when later trying to access the field. Fixes #1211. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* ar71xx: fix lzma-loader build with glibcJonas Gorski2017-12-131-1/+1
| | | | | | | | | | | | | | | | For an unknown reason gcc tries to link in crti.o when building with a glibc toolchain (this does not happen with other targets). Prevent this by telling gcc explicitly to not do that. Fixes the following build error: /home/jonas/git/lede/staging_dir/toolchain-mips_24kc_gcc-5.5.0_glibc/lib/gcc/mips-openwrt-linux-gnu/5.5.0/../../../../mips-openwrt-linux-gnu/lib/crti.o: In function `_init': (.init+0x18): relocation truncated to fit: R_MIPS_GOT16 against `__gmon_start__' /home/jonas/git/lede/staging_dir/toolchain-mips_24kc_gcc-5.5.0_glibc/lib/gcc/mips-openwrt-linux-gnu/5.5.0/../../../../mips-openwrt-linux-gnu/lib/crti.o: In function `_init': (.init+0x28): relocation truncated to fit: R_MIPS_CALL16 against `__gmon_start__' collect2: error: ld returned 1 exit status Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* treewide: add only one device when appending to TARGET_DEVICESLuis Araneda2017-12-1210-50/+216
| | | | | | | | | This will avoid some conflicts when doing a git rebase or merge, specially when adding support to a new device. Signed-off-by: Luis Araneda <luaraneda@gmail.com> [drop brcm47xx changes which rename the images] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: fix board detection with newer RouterBOOT versionsGabor Juhos2017-12-122-0/+86
| | | | | | | | | | | | | | | Recent RouterBOOT version (at least version 3.41 on RB911G-5HPacD) use "Board=" kernel parameter instead of "board=" to pass the board name to the kernel. Due to this change the board detection code is not working on the devices shipped with the new RouterBOOT version. Because the kernel is unable to identify these boards they become unusable despite that they are supported by the current code. Update the prom_init code to convert the 'Board' kernel parameter to 'board'. After this change, the board detection works also with the new RouterBOOT versions. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* brcm47xx: remove versions from linksys-e1000 targetMoritz Warning2017-12-111-2/+2
| | | | | | | | | | The target name does not need to included a revision if all revisions are supported. This target supports all revisions (v1, v2, v2.1). Signed-off-by: Moritz Warning <moritzwarning@web.de> [Keep the version numbers in the device title, it doesn't harm] Signed-off-by: Mathias Kresin <dev@kresin.me>
* brcm47xx: use proper region code in image nameMoritz Warning2017-12-111-9/+9
| | | | | | | Replace 'north-america' by 'na' and remove 'other-regions' in image files for Netgear WGR614 v10. Signed-off-by: Moritz Warning <moritzwarning@web.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 12:32:31 +0000