summaryrefslogtreecommitdiff
path: root/target/linux/brcm63xx
Commit message (Collapse)AuthorAgeFilesLines
* brcm63xx: image: trim revision code used for --rsa-signatureJo-Philipp Wich2016-12-141-3/+3
| | | | | | | | | | | | | | | | | The imagetag RSA signature field may not exceed 20 characters, so trim the Git hash portion from the REVISION variable in order to ensure that the resulting string fits within this field. The current revision values may be longer than 20 chars, especially when building within a dirty tree. In this case, the revision will look like "r2435+75-b4aa3c8" which, combined with the "LEDE-" prefix, is 21 chars long. Fixes the following error spotted by the buildbots: Error: RSA Signature (rsa_signature,r) too long. make[4]: *** [.../lede-brcm63xx-generic-NEUFBOX6-squashfs-cfe.bin] Error 1 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* brcm63xx: Livebox 1: add userspace board supportDaniel Gonzalez Cabanelas2016-11-213-0/+12
| | | | | | | | | | Fix configuration files for the Livebox 1 routers. - Add status led - Set eth0 as the LAN port, for coherence with RedBoot and comfortability. - Add led triggers Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: Livebox 1: relocate the kernel to fix bootDaniel Gonzalez Cabanelas2016-11-212-2/+2
| | | | | | | | Fix Image generation for the Livebox 1 - missing "relocate-kernel", wrong "LOADADDR", fix it Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: Livebox 1: fix part probe nameDaniel Gonzalez Cabanelas2016-11-211-1/+1
| | | | | | | | Fix the DTS file for the Livebox 1 routers: - part probe wrong, it should be RedBoot (uppercase matters) Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: Livebox 1: fix led namingDaniel Gonzalez Cabanelas2016-11-211-5/+5
| | | | | | | | Fix the DTS file for the Livebox 1 routers: - leds are totally wrong, fix them. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: Livebox 1: use button 1 as failsafe buttonDaniel Gonzalez Cabanelas2016-11-211-3/+3
| | | | | | | | Fix the DTS file for the Livebox 1 routers: - no failsafe button, use button 1 for this purpose Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* treewide: dts: use keycode defines from input dt-bindingMathias Kresin2016-11-131-1/+1
| | | | | | | | | | | | | | | | | | | | | All compiled device tree files not mentioned are binary identical to the former ones. Fix the obvious decimal/hex confusion for the power key of ramips/M2M.dts. Due to the include of the input binding header, the BTN_* node names in: - ramips/GL-MT300A.dts - ramips/GL-MT300N.dts - ramips/GL-MT750.dts - ramips/Timecloud.dts will be changed by the compiler to the numerical equivalent. Move the binding include of lantiq boards to the file where they are used the first time to hint the user where the values do come from. Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: dts: fix dtc compiler warningsMathias Kresin2016-11-124-4/+4
| | | | | | | | | | | Fixes invalid device tree parameters. Drop the mvsw61xx node used in mvebu device tree source files. It looks like some kind of ethernet switch cargo cult. Neither the marvell,88e6352 nor the marvell,88e6172 compatible strings can be found in any LEDE file or in the kernel sources. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: update kernel 4.4 to version 4.4.30Stijn Segers2016-11-021-1/+1
| | | | | | | | | | This patch bumps the 4.4 kernel from .28 to .30 and refreshes the patches. Compile-tested on ar71xx, x86/64, ramips/mt7621, brcm47xx and kirkwood. Run-tested on ar71xx & ramips/mt7621, brcm47xx and kirkwood (last two confirmed by P. Wassi). Signed-off-by: Stijn Segers <francesco.borromini@inventati.org>
* switch to the new usbport LED triggerRafał Miłecki2016-10-191-2/+2
| | | | | | | This makes init.d script handle existing UCI entries using the new trigger. It also switches all targets to use its package. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: update kernel 4.4 to version 4.4.20Álvaro Fernández Rojas2016-09-151-1/+1
| | | | | | | Refresh patches for all targets that support kernel 4.4. Compile-tested on brcm2708 only. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: Backport pending appended DTB handling patchesDaniel Gimpelevich2016-09-121-2/+2
| | | | | | | | | | Backport patches from upstream Linux kernel which are making the kernel stores the appended dtb not in the same resisters as defined in the UHI specification, use a separate variable on MIPS. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> [some modifications] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: mtd: backport Macronix sector size fixMathias Kresin2016-09-031-1/+1
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* build: fix subtarget descriptionsFelix Fietkau2016-09-041-4/+4
| | | | | | Move Target/Description above the target.mk include Signed-off-by: Felix Fietkau <nbd@nbd.name>
* brcm63xx: switch to board based failsafe networkingJonas Gorski2016-08-131-37/+0
| | | | Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: backport mtd of node changes from upstreamJonas Gorski2016-08-1312-23/+608
| | | | | | | Should fix parser data containing uninitialized values for of probed physmap flashes, which could break e.g. the redboot parser. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: fix CT-536p/CT-5621T supportDaniel Gonzalez2016-08-012-2/+2
| | | | | | | | | | | Fix support for the Comtrend CT-536+, CT-5361 and CT-5621T routers support. Currently the firmware is broken for these routers, because there is a missing bar in the code at the DTS file avoiding to match with DTS stuff at the kernel. This causes the router boots without ethernet connectivity. The status led also has a typo. Signed-off-by: Daniel Gonzalez <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: fix build with per-device rootfsFelix Fietkau2016-07-311-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* image: add a helper variable for getting kernel/rootfs from within image ↵Felix Fietkau2016-07-311-11/+11
| | | | | | Build/* templates Signed-off-by: Felix Fietkau <nbd@nbd.name>
* brcm63xx: fix HG556a C buttondani2016-07-241-1/+1
| | | | | | | One button of the HG556a-C has the wrong GPIO pin defined in the dts file, fix it Signed-off-by: Daniel Gonzalez <dgcbueu@gmail.com>
* image.mk: clean up redundant code related to DEVICE_DTSFelix Fietkau2016-07-151-2/+0
| | | | | | | | It is used by a core build template, so the variable should be initialized and added to DEVICE_VARS in the core. Same for DEVICE_DTS_DIR Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: update kernel 4.4 to version 4.4.15Hauke Mehrtens2016-07-131-1/+1
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm63xx: fix image generation with offsets/blocksizes != 64KJonas Gorski2016-07-091-2/+2
| | | | | | | | | | | Defer the CFE_EXTRAs evaluation to allow overriden BLOCK_SIZE and IMAGE_OFFSET take effect, and replace the unused IMAGE_SIZE with IMAGE_OFFSET in DEVICE_VARS. This fixes image generation for targets using different offsets or blocksizes. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: fix CVG834G compatible stringJonas Gorski2016-07-091-1/+1
| | | | | | | The CVG834G claimed to be a BCM6348, but is actually BCM3368. Since we don't test against it, this was harmless. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* kernel: Move append-dtb to common image-commandsBen Whitten2016-06-221-6/+2
| | | | | | This build step is used by various targets, move it to a common section. Signed-off-by: Ben Whitten <ben.whitten@gmail.com>
* brcm63xx: simplify block size and image offset optionsÁlvaro Fernández Rojas2016-06-211-34/+45
| | | | | | | | Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: add sysupgrade imagesÁlvaro Fernández Rojas2016-06-212-20/+31
| | | | | | | | | | Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: merge DSL-274X-F1 profilesJonas Gorski2016-06-211-16/+6
| | | | | | | The only difference is a field in the image tag header, so just define two images for it instead of treating them as separate devices. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: move the bootargs into the dtb filesJonas Gorski2016-06-2184-3/+334
| | | | | | Instead of using a fixed commandline, allow one per device. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: use upstreamed compatible name for the periph intcJonas Gorski2016-06-2111-11/+11
| | | | | | | This makes the eventual migration to bmips easier, as dts files will require less changes. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: fix external IRQsDaniel Gonzalez2016-06-211-9/+9
| | | | | | | | | | | | | External IRQs are currently broken, fix the BCM6345_EXT_IRQ driver. Since the adoption of the new driver irq-bcm6345-ext, in Chaos Calmer, external IRQs don't work. It seems there were some minor errors at the initial development of the driver. This patch fixes the ticket https://dev.openwrt.org/ticket/21613 Signed-off-by: Daniel Gonzalez <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: fix single profile selectionÁlvaro Fernández Rojas2016-06-211-0/+1
| | | | | | | Fixes commit c6990347. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* kernel: rename B53 symbols to avoid upstream kernel conflictRafał Miłecki2016-06-201-6/+6
| | | | | | | | | In kernel 4.7 there is upstreamed b53 driver using (mostly?) the same symbols as our b53 does. Change our symbols so both drivers can coexist in kernel tree. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> Acked-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: improve image/MakefileÁlvaro Fernández Rojas2016-06-081-2/+1
| | | | | | | - Use KERNEL_INITRAMFS_SUFFIX for customizing initramfs name. - Modifying $(PROFILES) is no longer needed. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: fix typo image/MakefileÁlvaro Fernández Rojas2016-06-051-1/+1
| | | | | | This typo was introduced in c6990347 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: add initial support for Netgear EVG2000Graham Fairweather2016-06-038-1/+195
| | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the Netgear EVG2000 VoIP Gateway to the bcm63xx targets. This device was not sold to the general public, but rather is/was provided by telcos to customers in Sweden, Australia, Singapore and other parts of asia. Known issues: - Unable to detect 53115 switch. This appear to be a problem with probing for the PHY using MDIO and results in error 5. Doesn't seem to be a problem with the configuration, and could use someone with experience to have a look at it. - Uses the b43 driver as using the OpenWRT/LEDE broadcom-wl driver fails to load the firmware for the 4322, so 802.11n is not supported. More info on the device and the research can be found at: https://wiki.openwrt.org/toh/netgear/evg2000 https://wikidevi.com/wiki/Netgear_EVG2000 https://github.com/Xotic750/mirror-lede/tree/evg2000 https://forum.openwrt.org/viewtopic.php?id=63950 Signed-off-by: Graham Fairweather <xotic750@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: set DSL-274XB-F1 ath9k LED as active highÁlvaro Fernández Rojas2016-06-0335-102/+103
| | | | | | D-Link DSL-274XB rev F1 has an active high ath9k LED. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: set HG556a A/B ath9k LED as active highÁlvaro Fernández Rojas2016-06-0324-61/+63
| | | | | | Huawei HG556a has an active high ath9k LED. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: add support for inverting ath9k LED polarityÁlvaro Fernández Rojas2016-06-032-9/+12
| | | | | | | Some devices with ath9k WiFi require changing the default active low polarity to high in order to correctly operate the WiFi status LEDs. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: remove obsolote preinit scripts and fix preinit iface scriptÁlvaro Fernández Rojas2016-06-034-84/+23
| | | | | | | | | | These scripts were causing ip issues in the latest version of LEDE: https://gist.github.com/Noltari/6d20d8bcbe236caf516c0a73f5477d00 Fixes preinit iface script by making eth0 the default ifname and only changing it to eth1 for the devices that specifically need it. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: move profiles definitions to image/MakefileÁlvaro Fernández Rojas2016-06-0328-1359/+1072
| | | | | | This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: refresh kernel patches and configÁlvaro Fernández Rojas2016-06-034-12/+19
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: drop linux 4.1 supportÁlvaro Fernández Rojas2016-06-03162-16487/+0
| | | | | | Switch to linux 4.4 now that it has been enough tested. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: switch to linux 4.4Álvaro Fernández Rojas2016-06-031-1/+2
| | | | | | Boot tested on AR-5381u, AR-5387un and WAP-5813n Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: fix F@ST2704V2 image generationÁlvaro Fernández Rojas2016-06-011-1/+1
| | | | | | This device needs the firmware padded to 4MB. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: update kernel 4.1 to version 4.1.20Hauke Mehrtens2016-03-181-1/+1
| | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 49035
* kernel: update kernel 4.4 to version 4.4.6Hauke Mehrtens2016-03-171-1/+1
| | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 49032
* brcm63xx: fix BCM3368 interrupt controller addressesJohn Crispin2016-03-101-2/+2
| | | | | | | | | Looks like the addresses for BCM3368 were wrongly defined when DT support was introduced. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 48980
* brcm63xx/lzma-loader: fix O32 ABI conformanceJohn Crispin2016-03-101-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | According to the calling convention of the o32 ABI the caller function must reserve stack space for $a0-$a3 registers in case the callee needs to save its arguments. The assembly code of the loader does not reserve stack space for these registers thus when the 'loader_main' function needs to save its arguments, those will be stored in the 'workspace' area instead of the stack. Because the workspace area is also used by other part of the code, the saved register values gets overwritten and this often leads to failed kernel boots. Fix the code to reserve stack space for the registers to avoid this error. Signed-off-by: Gabor Juhos <juhosg@openwrt.org> [noltari: apply the fix for brcm63xx too] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 48979
* kernel: update kernel 4.4 to version 4.4.3Hauke Mehrtens2016-02-252-4/+4
| | | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48783
generated by cgit v1.1 at 2024-12-23 16:53:53 +0000