aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ath79: remove useless phy-handle nodesChuanhong Guo2018-08-062-20/+1
| | | | | | | phy-handle is used to poll link status. They are useless when we need fixed-link on these interfaces. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* kernel: modules: fix kmod-regmap reduxChristian Lamparter2018-08-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Jonas Gorski commented on the previous patch: |This is actually the wrong fix and papers over an issue in one of our |local patches. | |We intentionally allow regmap to be built as a module, see | |/target/linux/generic/hack-4.14/259-regmap_dynamic.patch |[...] |[The regulator code] optionally supports regmap thanks to the stubs |provided if regmap is disabled - which breaks if you compile regmap |as a module. In order to mitigate this issue, this patch reverts the previous patch and replaces the existing IS_ENABLED(CONFIG_REGMAP) with IS_REACHABLE(CONFIG_REGMAP). This solves this particular issue as the regulator code will now automatically fallback to the regmap stubs in case the kmod-regmap module is enabled, but nothing else sets CONFIG_REGMAP=y. Note: There's still a potential issue that this patch doesn't solve: If someone ever wants to make a OpenWrt kernel package for a regulator module that requires the REGMAP feature for a target that doesn't set CONFIG_REGMAP=y but has CONFIG_REGULATOR=y, the resulting kmod-regulator-xyz package will not work on the target. Luckily, there aren't any in-tree OpenWrt kernel module packages for regulators at the moment. On the bright side: regmap is a critical part nowadays and all new and upcoming architectures require it by default. This will likely only ever be a problem for legacy targets and devices that cannot afford to enable REGMAP. Cc: Jonas Gorski <jonas.gorski@gmail.com> Cc: John Crispin <john@phrozen.org> Fixes: d00913d1215b ("kernel: modules: fix kmod-regmap") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* mt7620: gsw: make IntPHY and ExtPHY share mdio addr 4 possibleChen Minqiang2018-08-061-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | To share mdio addr for IntPHY and ExtPHY, as described in the documentation (MT7620_ProgrammingGuide.pdf). (refer: http://download.villagetelco.org/hardware/MT7620/MT7620_ProgrammingGuide.pdf) when port4 setup to work as gmac mode, dts like: &gsw { mediatek,port4 = "gmac"; }; we should set SYSCFG1.GE2_MODE==0x0 (RGMII). but SYSCFG1.GE2_MODE may have been set to 3(RJ-45) by uboot/default so we need to re-set it to 0x0 before this changes: gsw: 4FE + 2GE may not work correctly and MDIO addr 4 cannot be used by ExtPHY after this changes: gsw: 4FE + 2GE works and MDIO addr 4 can be used by ExtPHY Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
* ramips: fix gigabit switch PHY access on MDIODaniel Gimpelevich2018-08-061-1/+2
| | | | | | | | | | When PHY's are defined on the MDIO bus in the DTS, gigabit support was being masked out for no apparent reason, pegging all such ports to 10/100. If gigabit support must be disabled for some reason, there should be a "max-speed" property in the DTS. Reported-by: James McKenzie <openwrt@madingley.org> Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* ramips: remove superfluous & confusing DT bindingDaniel Gimpelevich2018-08-065-7/+24
| | | | | | | | | | | Mediatek has a reference platform that pairs an MT7620A with an MT7530W, where the latter responds on MDIO address 0x1f while both chips respond on 0x0 to 0x4. The driver special-cases this arrangement to make sure it's talking to the right chip, but two different ways in two different places. This patch consolidates the detection without the current requirement of both tests to be separately satisfied in the DTS. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* ramips: add support for Edimax BR-6478AC v2Daniel Gimpelevich2018-08-066-1/+243
| | | | | | | | | | | | | | | | | | | | | | | | Roll-up of patches by Rohan Murch, Hans Ulli Kroll, and James McKenzie. Taken from https://forum.openwrt.org/viewtopic.php?id=67192 and updated. Specification: - System-On-Chip: MT7620A - CPU/Speed: 580 MHz - Flash-Chip: Macronix MX25L6405D - Flash size: 8192 KiB - RAM: 64 MiB - Wireless No1: SoC-integrated: MT7620A 2.4GHz 802.11bgn - Wireless No2: On-board chip: MT7612E 5GHz 802.11ac - Switch: Mediatek MT7530W Gigabit Switch - USB: Yes 1 x 2.0 Installation: 1. Download sysupgrade.bin 2. Open vendor web interface 3. Choose to upgrade firmware 4. After reboot connect via ethernet at 192.168.1.1 Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* ramips: move partitions into partition table nodeAlex Maclean2018-08-04257-6412/+7454
| | | | | | | | Starting with kernel 4.4, the use of partitions as direct subnodes of the mtd device is discouraged and only supported for backward compatiblity reasons. Signed-off-by: Alex Maclean <monkeh@monkeh.net>
* ramips: unify partition node names in dts filesMathias Kresin2018-08-043-12/+17
| | | | | | | Use partition@ as name for all partition nodes. Add a label where necessary. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix whitespace and comment issues in dtsMathias Kresin2018-08-0428-86/+82
| | | | | | | | Fix space vs. tabs issue and trainling whitespaces. Use C style comments or drop the comments if they explain what is already to see in the devicetree parameters. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix dtc warningsMathias Kresin2018-08-04232-492/+27
| | | | | | Fix individual boards dtc warnings or obvious mistakes. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix hnat dtc warningMathias Kresin2018-08-041-11/+11
| | | | | | | | | | The hardware NAT node has the same reg/unit as the ethernet node. One of them need to be a child of the other. Make the hardware NAT node a child of the ethernet node since the it "reference" the netdev in its properties. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix pci/pcie related dtc warningsMathias Kresin2018-08-0466-684/+575
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add the ranges property to the PCI bridges where missing. Add the unit address to PCI bridge where missing. Rework the complete rt3883 pci node. Drop the PCI unit nodes from the dtsi. They are not used by any dts file and should be rather in the dts than in the SoC dtsi. Express the PCI-PCI bridge in a clean devicetree syntax. The ralink,pci-slot isn't used by any driver, drop it. Move the pci interrupt controller out of the pci node. It doesn't share the same reg and therefore should be an independent/SoC child node. Move the pci related rt3883 pinctrl setting to the dtsi instead of defining the very same for each rt3883 board. If the device_type property is used for PCI units, the unit is treated as pci bridge which it isn't. Drop it for PCI units. Reference pci-bridges or the pci node defined in the dtsi instead of recreating the whole node hierarchy. It allows to change the referenced node in the dtsi without the need to touch all dts. Fix the PCI(e) wireless unit addresses. All our PCI(e) wireless chips are the first device on the bus. The unit address has to be the bus address instead of the PCI vendor/device id. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: use ralink,nr-gpio instead of ralink,num-gpiosMathias Kresin2018-08-0410-27/+27
| | | | | | | | | | | Since commit c1e7738988f5 ("checks: add gpio binding properties check") dtc treats any *-gpios and *-gpio property as phandle at least during checks. The only whitelisted property is nr-gpio. Use ralink,nr-gpio in favour of ralink,num-gpios to get rid of false positive warnings. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix cpu interrupt controller dtc warningsMathias Kresin2018-08-048-8/+8
| | | | | | | The cpu interrupt controller doesn't have a reg property, hence we can't use a unit address in the node name. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix cpu related dtc warningsMathias Kresin2018-08-049-2/+34
| | | | | | We need a reg property if we are using a unit address. Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: convert gpio-export to platform driverRené van Dorst2018-08-043-21/+12
| | | | | | | | | | | | Without this patch you will get an error "gpio-export probe deferral not supported" when you try to export i2c expander gpio pins. gpio-export is probed long before i2c-bus and i2c expander are created and it doesn't retry it so none pins are exported. Signed-off-by: René van Dorst <opensource@vdorst.com> apply the change to all instances of the gpio exports patch Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath79: really fix TP-Link Archer C7 v2 MAC addressMathias Kresin2018-08-042-2/+1
| | | | | | | | | | | | | | | | | | | | Revert 290c54473ead ("ath79: fix TP-Link Archer C7 v2 wlan1 MAC address") which obviously aims to have a distinct MAC address per interface. Unfortunally it doesn't match what is used by the stock firmware and we shouldn'z use MAC Adresses not reserverd for/assigned to a particular board. The correct MAC adress increments for this board are: wlan0 (5GHz) : -1 wlan1 (2.4GHz) : 0 eth1 (LAN) : 0 eth0 (WAN) : 1 Fixes: FS#408 Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: bump 4.14 to 4.14.60Koen Vandeputte2018-08-0325-186/+121
| | | | | | | | | | | | Refreshed all patches Removed upstreamed patches: - 500-ext4-fix-check-to-prevent-initializing-reserved-inod.patch Compile-tested on: cns3xxx, imx6, x86_64 Runtime-tested on: cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.117Koen Vandeputte2018-08-039-12/+12
| | | | | | | | | Refreshed all patches Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* brcm63xx: switch to 4.14Jonas Gorski2018-08-021-1/+1
| | | | | | | Kernel 4.14 support has been present for quite some time, so let's give it wider testing. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: drop b43 from devices with unsupported wifiJonas Gorski2018-08-021-2/+2
| | | | | | | | The internal wifi isn't supported, so drop b43 from devices that only have it. Fixes FS#1698 Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: copy SR102 support patch to 4.14 as wellJonas Gorski2018-08-021-0/+68
| | | | | | | It seems to have been missed when the patch was accepted. Fixes: d59126040701 ("brcm63xx: initial support for Sky SR102 router") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: drop bogus SPROM section from SR102Jonas Gorski2018-08-021-10/+3
| | | | | | | | The integrated SoC wifi will likely never be supported, and if, it will go through DT with the sprom contents there. Fixes: d59126040701 ("brcm63xx: initial support for Sky SR102 router") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* ar71xx: add support for TP-LINK CPE510 V2.0Andrew Cameron2018-08-022-2/+22
| | | | | | | | Adds Support for the TP-LINK CPE510 V2.0 by TP-Link. The hardware is almost the same as the CPE510 V1.0 Follow the same processes as for the CPE510 V1.0 Signed-off-by: Andrew Cameron <apcameron@softhome.net>
* Revert "ar71xx: ag71xx: Prevent kernel oops for board def"Jo-Philipp Wich2018-08-011-15/+1
| | | | | | | | | | | This reverts commit 7a3e133751870a3431e2430386a77a002eb24117. This change reportedly breaks connectivity on some ar71xx devices, so revert it for now. Ref: https://github.com/openwrt/openwrt/pull/1217#issuecomment-409708087 Reported-by: Hannu Nyman <hannu.nyman@iki.fi> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* Revert "ar71xx: ag71xx: Add connect message: fixed phy"Jo-Philipp Wich2018-08-011-7/+0
| | | | | | | | | | | This reverts commit 0b9f4e880807e3cfd22d12b929202e1edcdc577c. This change reportedly breaks connectivity on some ar71xx devices, so revert it for now. Ref: https://github.com/openwrt/openwrt/pull/1217#issuecomment-409708087 Reported-by: Hannu Nyman <hannu.nyman@iki.fi> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* Revert "ar71xx: ag71xx_phy: Fix compilation for debug messages"Jo-Philipp Wich2018-08-011-4/+2
| | | | | | | | This reverts commit 2655fbe8efb2a596aa8db92cffa817e3bf0c64ea. The patch introduces syntax errors, revert it for now. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: cr3000: cleanup board definitionDaniel F. Dickinson2018-08-011-16/+23
| | | | | | | | | | | | | 1) Add comments so it's clear why we did things; this may prevent someone (e.g. me) from sinking time into fixing things that aren't broken and/or were done for reason. 2) Drop mdio 0 probe/register; we don't use ag1xx mdio bus 0. 3) Cosmetic reording of some code (tested) that makes the defintion more clear. Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
* ar71xx: cr3000: Use correct company nameDaniel F. Dickinson2018-08-013-3/+3
| | | | | | It's 'PowerCloud Systems' not 'PowerCloud'. Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
* ar71xx: cr3000: Drop support for defunct cloudDaniel F. Dickinson2018-08-011-11/+2
| | | | | | | | | The CR3000 stock firmware is now irrelevant as it required a now defunct cloud service. Therefore only build images that use the entire flash (overwriting stock firwmare-specific partitions that no longer matter), previously called 'nocloud' images. Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
* ath79: Forward port support for CR3000Daniel F. Dickinson2018-08-014-3/+194
| | | | | | | | | | | | | | | | | | | | | | | | The PowerCloud Systems CR3000 was a cloud-managed CPE for a now defunct NaaS offering. It was previously supported under the ar71xx branch and this forward ports that support with some notable differences: 1) Since reverting to stock firmware is now irrelevant there is is only a single openwrt image generated which uses the entire flash rather than preserving PowerCloud-specific partitions that are unneeded to openwrt-- those partitions will be erased and used by the openwrt image. 2) Rather than use a non-standard probe order for the ethernet devices, this image uses a set of 'ip link set ethX name ethY' commands very early in preinit (before the network is used at all), in order to have the the switch and Wan use the same ethernet names as in previous images. 3) /etc/config/wireless will need to be regenerated as the path to the wireless device has changed due to differences in ath79 DT for ar93x compared to ar71xx images. 4) eth0 is wan and eth1 is lan (switch) Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
* kernel: bump 4.9 to 4.9.116Koen Vandeputte2018-08-0151-605/+334
| | | | | | | | | | | | | | | | | | | | | | | | | Refreshed all patches Remove upstreamed patches. - 103-MIPS-ath79-fix-register-address-in-ath79_ddr_wb_flus.patch - 403-mtd_fix_cfi_cmdset_0002_status_check.patch - 001-4.11-01-mtd-m25p80-consider-max-message-size-in-m25p80_read.patch - 001-4.15-08-bcm63xx_enet-correct-clock-usage.patch - 001-4.15-09-bcm63xx_enet-do-not-write-to-random-DMA-channel-on-B.patch - 900-gen_stats-fix-netlink-stats-padding.patch Introduce a new backported patch to address ext4 breakage, introduced in 4.9.112 - backport-4.9/500-ext4-fix-check-to-prevent-initializing-reserved-inod.patch This patch has been slightly altered to compensate for a new helper function introduced in later kernels. Also add ARM64_SSBD symbol to ARM64 targets still running kernel 4.9 Compile-tested on: ar71xx, bcm2710 Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: add missing ARM64_SSBD symbolStijn Tintel2018-07-316-0/+6
| | | | | | | | | In 4.14.57, a new symbol for Spectre v4 mitigation was introduced for ARM64. Add this symbol to all ARM64 targets using kernel 4.14. This mitigates CVE-2018-3639 on ARM64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: remove duplicate #define's in at803x Ethernet PHY driverDaniel Golle2018-07-312-20/+14
| | | | | | | | | | | AT803X_REG_CHIP_CONFIG and AT803X_BT_BX_REG_SEL have been defined upstream by commit f62265b53ef3 ("at803x: double check SGMII side autoneg") An existing local patch then added those exact same defines again which isn't necessary, so remove them. Fixes: f791fb4af450 ("kernel: add linux 4.9 support") Fixes: b3f95490b9be ("kernel: generic: Add kernel 4.14 support") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: re-add patch for AT8032 Ethernet PHYDaniel Golle2018-07-314-11/+81
| | | | | | | | | | The patch was wrongly removed by a kernel version bump to 4.9.105 in the believe that it was merged upstream thow it wasn't. This lead to unrecoverable link losses on devices which use those PHYs such as many ubnt single-port CPEs. Fixes: 7dca1bae82 (kernel: bump to 4.9.105) Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: add pending e1000e fixesStijn Tintel2018-07-314-0/+331
| | | | | | | | | | | | | | | The previous round of fixes for the 82574 chip cause an issue with emulated e1000e devices in VMware ESXi 6.5. It also contains changes that are not strictly necessary. These patches fix the issues introduced in the previous series, revert the unnecessary changes to avoid unforeseen fallout, and avoid a case where interrupts can be missed. The final two patches of this series are already in the kernel, so no need to include them here. Patchwork: https://patchwork.ozlabs.org/cover/881776/ Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: bump 4.14 to 4.14.59Stijn Tintel2018-07-3158-827/+176
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Drop patch that was superseded upstream: ramips/0036-mtd-fix-cfi-cmdset-0002-erase-status-check.patch Drop upstreamed patches: - apm821xx/020-0001-crypto-crypto4xx-remove-bad-list_del.patch - apm821xx/020-0011-crypto-crypto4xx-fix-crypto4xx_build_pdr-crypto4xx_b.patch - ath79/0011-MIPS-ath79-fix-register-address-in-ath79_ddr_wb_flus.patch - brcm63xx/001-4.15-08-bcm63xx_enet-correct-clock-usage.patch - brcm63xx/001-4.15-09-bcm63xx_enet-do-not-write-to-random-DMA-channel-on-B.patch - generic/backport/080-net-convert-sock.sk_wmem_alloc-from-atomic_t-to-refc.patch - generic/pending/170-usb-dwc2-Fix-DMA-alignment-to-start-at-allocated-boun.patch - generic/pending/900-gen_stats-fix-netlink-stats-padding.patch In 4.14.55, a patch was introduced that breaks ext4 images in some cases. The newly introduced patch backport-4.14/500-ext4-fix-check-to-prevent-initializing-reserved-inod.patch addresses this breakage. Fixes the following CVEs: - CVE-2018-10876 - CVE-2018-10877 - CVE-2018-10879 - CVE-2018-10880 - CVE-2018-10881 - CVE-2018-10882 - CVE-2018-10883 Compile-tested: ath79, octeon, x86/64 Runtime-tested: ath79, octeon, x86/64 Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: switch compatible property for RedBoot DT bindingMatt Merhar2018-07-303-3/+3
| | | | | | | | | | | | | | | This changes the DT binding's compatible property to "ecoscentric,redboot-fis-partitions", removing the existing reference to Red Hat. Per the documentation hosted at eCosCentric's website, eCosCentric is RedBoot's sole commercial maintainer since 2002, and the project has been under the stewardship of the Free Software Foundation since 2008. This also updates the property in the Inventel Livebox 1 .dts, the binding's only current user. Signed-off-by: Matt Merhar <mattmerhar@protonmail.com>
* brcm2708: fix w1 patchJohn Crispin2018-07-301-34/+23
| | | | | | this is now part of generic Signed-off-by: John Crispin <john@phrozen.org>
* ipq40xx: Limit usable channels for OpenMesh A62 PHYsSven Eckelmann2018-07-301-0/+2
| | | | | | | | | The OpenMesh A62 is a tri-band device (1x 2.4GHz, 2x 5GHz) with special filters in front of the RX+TX paths to the 5GHz PHYs. These filtered channel can in theory still be used by the hardware but the signal strength is reduced so much that it makes no sense. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ath79: fix irq assignment for pci-ar71xx driverMatt Merhar2018-07-301-3/+7
| | | | | | | | | | | | | | | | | | In the new DT-based pci-ar71xx driver, ar71xx_pci_irq_init() was being called before populating the PCI controller's device_node struct member. This led to no IRQ being assigned to connected PCI devices (e.g. ath9k cards) and caused them to be non-functional aside from simply being detected. The previous errors encountered in dmesg were: "irq: no irq domain found for /ahb/apb/pcie-controller@180c0000 !". /proc/interrupts listed an IRQ of 0 for the cards. While this has been only been tested on a yet-to-be-merged RouterStation Pro target, it should also fix the broken wifi people have reported for the ath79 WNDR3800 target. Signed-off-by: Matt Merhar <mattmerhar@protonmail.com>
* ar71xx: define switch for rb-952ui-5ac2ndThibaut VARÈNE2018-07-301-2/+2
| | | | | | | QCA9533 built-in switch can be configured Tested-by: Thibaut VARÈNE <hacks@slashdirt.org> Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* ipq40xx: fix booting secondary CPU coresMantas Pucka2018-07-302-21/+35
| | | | | | | 95672e04 broke booting secondary cores by removing 'qcom,saw' property from L2 cache node. kpssv2_release_secondary() requires it. Signed-off-by: Mantas Pucka <mantas@8devices.com>
* ar71xx: fix TL-WR1043N v5 port mappingJohn Crispin2018-07-301-1/+4
| | | | | | fixes 5660c8fb20 ("ar71xx: TL-WR1043N v5: fix mapping of LAN ports to labels on housing.") Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx: TL-WR1043N v5: fix mapping of LAN ports to labels on housing.Tim Thorpe2018-07-301-1/+1
| | | | | | Reversed the numbering of the LAN ports in Luci so as to match the port numbers on the housing. Signed-off-by: Tim Thorpe <tim@tfthorpe.net>
* ar71xx: TL-WR1043N v4/v5: add orange WAN LED supportTim Thorpe2018-07-301-3/+14
| | | | | | | | | | | Add missing definitions for the orange WAN LED on the TL-WR1043N(D) v4 and v5. Change the name of a MAC address offset constant to make it consistent with the format of the existing constants. Signed-off-by: Tim Thorpe <tim@tfthorpe.net>
* ath79: add support for tl-wr841n-v9Lucian Cristian2018-07-305-1/+175
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* ramips: add support for ELECOM WRC-2533GSTINAGAKI Hiroshi2018-07-304-0/+204
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ELECOM WRC-2533GST is a 2.4/5 GHz band 11ac rotuer, based on MediaTek MT7621A. Specification: - MT7621A (2-Core, 4-Threads) - 128 MB of RAM (DDR3) - 16 MB of Flash (SPI) - 4T4R 2.4/5 GHz wifi - MediaTek MT7615 - 5x 10/100/1000 Mbps Ethernet - 4x LEDs, 6 keys (2x buttons, 1x slide switch) - UART header on PCB - Vcc, GND, TX, RX from ethernet port side - baudrate: 57600 bps Flash instruction using factory image: 1. Connect the computer to the LAN port of WRC-2533GST 2. Connect power cable to WRC-2533GST and turn on it 3. Access to "https://192.168.2.1/" and open firmware update page ("ファームウェア更新") 4. Select the OpenWrt factory image and click apply ("適用") button 5. Wait ~150 seconds to complete flashing Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* x86: add support to set GRUB menu entry titleKjel Delaey2018-07-303-3/+6
| | | | | | | | $ make menuconfig Target Images -> Title for the menu entry in GRUB Signed-off-by: Kjel Delaey <kjel_delaey@hotmail.com>
* kirkwood: add support for Iomega Storcenter ix2-200Ademar Arvati Filho2018-07-307-5/+97
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Iomega Storcenter ix2-200 is a dual SATA NAS powered by a Marvell Kirkwood SoC clocked at 1GHz. It has 256MB of RAM and 32MB of flash memory, 3x USB 2.0 and 1x 1Gbit/s NIC Specification: - SoC: Marvell Kirkwood 88F6281 - CPU/Speed: 1000Mhz - Flash-Chip: Hynix NAND - Flash size: 32 MiB,erase size:16 KiB,page size:512,OOB size:16 - RAM: 256MB - LAN: 1x 1000 Mbps Ethernet - WiFi: none - 3x USB 2.0 - UART: for serial console Installation instructions - easy steps: 1. download factory.bin and copy into tftp server 2. access uboot environment with serial cable and run ``` setenv mainlineLinux yes setenv arcNumber 1682 setenv console 'console=ttyS0,115200n8' setenv mtdparts 'mtdparts=orion_nand:0x100000@0x000000(u-boot)ro,0x20000@0xA0000(u-boot environment)ro,0x300000@0x100000(kernel),0x1C00000@0x400000(ubi)' setenv bootargs_root 'root=' setenv bootcmd 'setenv bootargs ${console} ${mtdparts} ${bootargs_root}; nand read.e 0x800000 0x100000 0x300000; bootm 0x00800000' saveenv setenv serverip 192.168.1.1 setenv ipaddr 192.168.1.13 tftpboot 0x00800000 factory.bin nand erase 0x100000 $(filesize) nand write 0x00800000 0x100000 $(filesize) run bootcmd ``` 3. access openwrt by dhcp ip address assigned by your router (p.ex: 192.168.1.13) Installation steps nand bad blocks proof: 1. download initramfs-uImage and copy into usb ext2 partition ``` mkfs.ext2 -L ext2 /dev/sdh1 mount -t ext2 /dev/sdh1 /mnt cp initramfs-uImage /mnt/initramfs.bin umount /mnt ``` 2. access uboot environment with serial cable and run ``` setenv mainlineLinux yes setenv arcNumber 1682 setenv console 'console=ttyS0,115200n8' setenv mtdparts 'mtdparts=orion_nand:0x100000@0x000000(u-boot)ro,0x20000@0xA0000(u-boot environment)ro,0x300000@0x100000(kernel),0x1C00000@0x400000(ubi)' setenv bootargs_root 'root=' setenv bootcmd 'setenv bootargs ${console} ${mtdparts} ${bootargs_root}; nand read.e 0x800000 0x100000 0x300000; bootm 0x00800000' saveenv usb reset; ext2load usb 0:1 0x00800000 /initramfs.bin; bootm 0x00800000 ``` 3. log into openwrt and sysupgrade to install into flash ``` sysupgrade -n /tmp/sysupgrade.bin ``` 4. access openwrt by dhcp ip address assigned by your router (p.ex: 192.168.1.13) Signed-off-by: Ademar Arvati Filho <arvati@hotmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-12 19:58:49 +0000