aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* brcm47xx: bump kernel to 4.4Rafał Miłecki2016-10-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Kernel 4.4 was ready for brcm47xx for almost a year now but I kept postponing the bump due to problems with Linksys WRT300N v1.0. OpenWrt and LEDE with 4.4 were hanging at the booting with the: > Starting program at 0x80001000 (the last CFE message). This was a permanent state, "make distclean" wasn't helping, I spent hours debugging this and I was reliably reproducing the issue every time. I also reported it on linux-mips ML in the thread: > BCM4704 stopped booting with 4.4 (due to vmlinux size?) After ~month I started working on WRT300N again. I got hangs as expected every time I switched from 4.1 to 4.4. I started experimenting with: 1) TRX content (I tried dropping rootfs partition) 2) BZ_TEXT_START of lzma-loader 3) Flashing other variants of image: lzma compressed kernel (without a loader), gzip compressed one, uncompressed one. At some point I got rootfs-less image booting and after that I couldn't reproduce problem anymore, even with a complete firmware. It seems like hardware was in some locked/unstable state that got magically fixed. I have LEDE working now, tested it even with "make distclean", it seems we can bump kernel now. I'll keep testing it on WRT300N for some time. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* brcm47xx: build also TRX image for Linksys WRT300N V1Rafał Miłecki2016-10-241-0/+1
| | | | | | | Linksys WRT300N V1 has pretty bugged CFE bootloader (it crashes in a lot of situations) that doesn't accept .bin image. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* brcm47xx: open code Makefile entries for all devicesRafał Miłecki2016-10-241-115/+527
| | | | | | | If we want to use some of new features like per device rootfs we will need this to specify them there. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* mvebu: add support for the Linksys WRT3200ACM (Rango)Imre Kaloz2016-10-2411-16/+491
| | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mvebu: add missing status LEDs for Linksys WRT1200AC and WRT1900ACv2Imre Kaloz2016-10-241-1/+8
| | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org>
* kernel: update kernel 4.4 to version 4.4.27Álvaro Fernández Rojas2016-10-231-2/+2
| | | | | | | Refresh patches for all targets that support kernel 4.4. compile/run-tested on brcm2708/bcm2710 only. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm53xx: include b43 in Tenda AC9 imageRafał Miłecki2016-10-201-1/+1
| | | | | | There is some (poor?) support for BCM43217 in b43. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* lantiq: enable cpu temp driver for all vr9 boardsMathias Kresin2016-10-196-20/+4
| | | | | | | Only present on v1.2 vr9 SoCs but the driver takes care to not load on boards having a v1.1 SoC. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix thermal sensors driverMathias Kresin2016-10-191-5/+21
| | | | | | | | | | | | | | | | | | | | Read the temperature including the decimale place from the CGU_GPHY1_CR register. Decrement the temperature read from the register by 38.0 degree celsius. The temperature range of the sensor is -38.0 to +154 °C and the register value 0 is equal to -38.0 °C. This fixes the report of unrealistic temperatures as seen on all tested boards. Give the SoC a few milliseconds to get the first temperature value. On some rare occasions there is no temperature value in the register when read the first time after activation. This leads to a reported temperature of -38.0 °C on boot. Only version 1.2 of the vr9 SoC has a temperature sensor. Add a check to make sure the driver doesn't load on v1.1 vr9 SoCs. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: Sanitize device tree filesAndreas Eberlein2016-10-1956-656/+668
| | | | | | | | | | The device tree file of ARV752DPW uses numbers/hex values for gpio states and input event codes. This cleans it up and uses the available macros from header files. This way the functions are easier to read and comprehend. Signed-off-by: Andreas Eberlein <foodeas@aeberlein.de> [sanitize all device tree files] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: Fix buttons for ARV752DPWAndreas Eberlein2016-10-191-5/+5
| | | | | | | | The GPIO for reset switch is wrong in definition. Further the key codes for the two additional buttons are ineffective. Both is fixed here. Signed-off-by: Andreas Eberlein <foodeas@aeberlein.de>
* lantiq: use new build code for DGN3500Mathias Kresin2016-10-191-99/+36
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: drop lzma-loaderMathias Kresin2016-10-1924-2792/+0
| | | | | | It isn't used any more. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: rework VG3503J imageMathias Kresin2016-10-193-79/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the new image build code and remove the lzma loader. The lzma loader was used to cheat the signature validation of the bootloader and I found another way to do this. To migrate boards already using LEDE/OpenWrt to the new image the following steps need to be done once: VR9 # run reset_uboot_config VR9 # reset VR9 # setenv ethaddr AA:BB:CC:DD:EE:FF VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000 VR9 # saveenv VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin VR9 # erase 0xb0020000 $(filesize) VR9 # cp.b 0x81000000 0xb0020000 $(filesize) The mac address is printed on the label at the bottom of the case. The following steps are need to be done during first install: VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000 VR9 # saveenv VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin VR9 # erase 0xb0020000 $(filesize) VR9 # cp.b 0x81000000 0xb0020000 $(filesize) The image uses the uImage firmware splitter now instead of hardcoded kernel and rootfs partitions. The firmware partition size was extended to use flash space that was reserved for partitions required only by the ECI firmware. Due to the changes an upgrade to a later LEDE revision from a running LEDE is supported now. A default switch config was added and the device uses the same MAC addresses as the ECI firmware now instead of the same for all VG3503J. Signed-off-by: Mathias Kresin <dev@kresin.me>
* bcm53xx: include usbport trigger for devices with USBRafał Miłecki2016-10-191-0/+1
| | | | | | | We don't have any code for enabling it automatically yet but it allows adding entries manually to the /etc/config/system. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: drop usbdev LED triggerRafał Miłecki2016-10-199-472/+5
| | | | | | It was LEDE's trigger that was replaced by upstream usbport one. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* switch to the new usbport LED triggerRafał Miłecki2016-10-1927-134/+134
| | | | | | | 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>
* ipq806x: add back end-of-UBI marker for a few factory images (FS#228)Felix Fietkau2016-10-181-0/+2
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: Add support to TP-Link EAP120Henryk Heisig2016-10-1810-1/+168
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* ar71xx: set EU region code for TP-Link TL-WA901ND v4Matthias Schiffer2016-10-151-0/+1
| | | | | | | | | | | | | There is no US firmware for the TL-WA901ND v4 yet, so we'll just unconditionally set the EU region for now. This makes LEDE flashable on these devices again. The format of the region string is slightly different from the one used on the Archer C7 that is generated by mktplinkfw (the second half of the region string is missing), but it's similar enough to make it work. Tested-by: Jannis Pinter <jannis@pinterjann.is> Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ramips: add support for Planex VR500.YuheiOKAWA2016-10-157-1/+112
| | | | | | | | | | | | SOC: MT7621A RAM: 256MiB NOR: MX25L51245G Non Wireless Router. Issue: soft reboot problem. SPI Flash do not exit 4byte address mode. Signed-off-by: Yuhei Okawa <tochiro.srchack@gmail.com>
* imx6: inittab: Use login.sh wrapper so we can configure console passwordPetr Štetiar2016-10-151-2/+2
| | | | | | | | In dc92917 there was introduced login.sh wrapper which allows configuration of console passwords via UCI system ttylogin config option. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ar71xx: add support for the Airtight C-60Christian Lamparter2016-10-1513-14/+260
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the Airtight C-60. SOC: Atheros AR9344 rev 2 (CPU:560.000MHz) RAM: 128 MiB NOR: MX25L3205D 4MiB NAND: ST Micro NAND 32MiB 3,3V 8-bit SW-NET: AR8327N (2 Ports) WLAN1: Dual-Band AR9340 Rev:2 (built-in SoC) WLAN2: Dual-Band AR9300 Rev:4 PCIe Chip The switch is setup for an accesspoint: LAN1: (gigabit) is the wan-port. LAN2: (fast ethernet) is bridged with the br-lan. Flashing Guide (via initramfs): 1. Connect a PC to the serial port of the C-60. power up the C-60. Enter u-boot command prompt: #> nand erase #> setenv bootcmd "bootm 0x9f060000" #> saveenv #> setenv ipaddr 192.168.1.1 #> setenv netmask 255.255.255.0 #> setenv serverip 192.168.1.100 #> setenv bootfile lede-ar71xx-nand-c-60-initramfs-kernel.bin #> tftpboot #> bootm 2. Wait for the C-60 to boot LEDE. On the root prompt. Enter: # ubiformat /dev/mtd4 # ubiattach -p /dev/mtd4 3. After that copy the sysupgrade.tar onto the router and run: # sysupgrade sysupgrade.tar to flash the image. Special thanks to Chris Blake <chrisrblake93@gmail.com>. He provided a C-60 unit and he helped with debugging the switch, LEDs and platfrom support. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* generic: ar8216: improve ar8xxx_is_possible checkChristian Lamparter2016-10-151-6/+6
| | | | | | | | | | | | | | | | | The commit "generic: ar8216: add sanity check to ar8216_probe" (774da6c7a40320a320b28d71291c0e61fcf7bc8a) stated that PHY IDs should be checked at address 0-4. However, the PHY 4 was never check by the loop. This patch extends the check to be similar to the Atheors SDK. It tries all 4 ports and skips unconnected PHYs if necessary. If it cannot find any familiar PHYs, it will prevent the phy driver from initializing. This patch is necessary for the C-60. It doesn't have a PHY at port 3, so this caused the check in ar8xxx_is_possible to fail. As a result, the ethernet ports on the C-60 didn't work. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq806x: C2600: change leds colour nameHenryk Heisig2016-10-152-13/+12
| | | | Signed-off-by: Henryk Heisig hyniu@o2.pl
* ipq806x: add support for indicating the boot and upgrade state using four ledsHenryk Heisig2016-10-155-15/+54
| | | | Signed-off-by: Henryk Heisig hyniu@o2.pl
* lantiq: use wpad-mini for WBMR boardsMathias Kresin2016-10-152-20/+2
| | | | | | | | | | The WBMR boards are the only ones in the whole tree selecting the wpad and hostapd-utils package by default. Remove the wps uci-default script as well, there is no obvious reason why the wps config need to be set only for this board. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix ARV452CQW keysMathias Kresin2016-10-151-1/+1
| | | | | | Fix the typo in the gpio-keys-polled compatible string. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: use rfkill for wps button on wlan only boardsMathias Kresin2016-10-157-29/+8
| | | | | | | | | | | | | All of the touched boards don't have an ethernet port. Allow to use the wps button on these boards to enable the wireless radio after boot. The force enabled wireless for the DCH-M225 is removed. It is reckless to bring up an unencrypted wireless network by default these days. Using the wps button to bring up the radio seam to me the better approach. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: use rootfs splitter and new image build code for BR-6475NDMathias Kresin2016-10-152-43/+11
| | | | | | | Use the edimax uImage splitter instead of the fixed size rootfs partition. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: move edimax images to the new build codeMathias Kresin2016-10-153-32/+37
| | | | | | | | | | | | | | | | Images installed via TFTP recovery or the Edimax webinterface of the 3g-6200n(l) are writting with the edimax header to flash. Use only one image type for these boards. The migration to the factory only images need to be done via TFTP recovery. Use the same start address for the 3g-6200n(l) factory images as the stock firmware images. Thanks to Jan Dostrasil for reporting all the issues of the 3g-6200nl and the patient testing of all changes. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: mtdsplit_uimage: fix Edimax parserMathias Kresin2016-10-151-13/+7
| | | | | | | | | | | | | | According to the author the code was added to in preparation for adding support for a new board. The patch for the board was never send and the code never really tested. The edimax header starting with the edimax magic is put in front of the uImage header. There is no special uImage header used. Means, default magic and the type field is set to kernel as usual. Signed-off-by: Mathias Kresin <dev@kresin.me> edimax parser fix
* kernel: mtdsplit_uimage: fix rootfs offsetMathias Kresin2016-10-151-1/+1
| | | | | | | | The return value of the find_header function need to be added to the uimage_size, otherwise mtd_find_rootfs_from() might search for a rootfs within a custom header and fails. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: improve edimax 6200n/nl supportMathias Kresin2016-10-154-12/+20
| | | | | | | | | | Assign the reset functionality to the wps/reset buttons. Use the wlan switch of the 6200n to enable/disable wlan. Add the internet led of the 6200nl and use the led for boot status indication Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix edimax 6200nl switch configMathias Kresin2016-10-152-2/+1
| | | | | | | | | | | | | With 3a9752bbd2bc00e407b5dcad21789720f40abf0e and later changes to ramips_set_preinit_iface() the default vlan config applied during preinit was changed. These changes were made without updating the default network config to ensure that vlan interfaces used for lan/wan are still configured. Fix the issue by using the default all LAN portmap and disabling not connected switch ports using portdisable device tree parameter. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: tag the CPU switch portMathias Kresin2016-10-151-1/+1
| | | | | | | | | | | | With de5102651501e51c036f88fe9c4dbf6974e5158a the explicit tagging of the CPU port was removed. This leads to a not working default network config, with vlans enabled but disabled CPU tagging, for boards where all switch ports are having the same role. In case the ports are having different roles set, tagging is is set implicit for the CPU port by ucidef_add_switch(). Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: remove fixed lan/wan interface for switch configsMathias Kresin2016-10-151-1/+0
| | | | | | | | | | Don't set the lan/wan interface when using ucidef_add_switch. This results into a wan interface albeit all ports a annotated as lan ports. ucidef_add_switch takes care of setting the correct lan/wan interface according to the annotation of the ports. Signed-off-by: Mathias Kresin <dev@kresin.me>
* brcm2708: fix image generation with imagebuilderÁlvaro Fernández Rojas2016-10-131-1/+5
| | | | | | | COPYING is not present in $(LINUX_DIR) on imagebuilder and prevents a successful image creation. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ar71xx: move dragino2 from legacy to genericKarl Palsson2016-10-133-8/+10
| | | | | | Tested on real hardware with r1804. Signed-off-by: Karl Palsson <karlp@etactica.com>
* apm821xx: replace recovery image for the MBL with initramfsChristian Lamparter2016-10-134-118/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch "images: bump default rootfs size to 256 MB" a1f83bad606411a561e8e60110c71232b1a28aa2 caused a crash during boot for the recovery images. This is because both variants of the MyBook Live only have 256MB of RAM and for the recovery option, the ext4 rootfs was simply stored in the RAMDISK. This patch replaces recovery image for the MBL with an initramfs kernel. In order to boot the initramfs (for recovery or development): 0. copy the initramfs and device tree into tftp's server directory # cp *-initramfs-kernel.bin to /tftp-server/mbl.bin # cp *-ext4-kernel.dtb to /tftp-server/fdt.bin 1. Connect the MyBook Live (Duo) serial port. (Warning! Use a 3.3v level shifter). 2. Hit Enter during u-boot and insert these three lines: # setenv serverip 192.168.1.254; setenv ipaddr 192.168.1.1; # tftp ${kernel_addr_r} mbl.bin; tftp ${fdt_addr_r} fdt.bin # run addtty addmisc; bootm ${kernel_addr_r} - ${fdt_addr_r} Where 192.168.1.254 is your TFTP server. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: 64: enable pci hotplug and acpipnpYousong Zhou2016-10-131-7/+9
| | | | | | | | | | | | | | | | | | | | | | This will allow dynamically adding/removing at least virtio-net pci devices which are quite the norm in cloud environment with QEMU/KVM netdev_add bridge,id=wan2,br=br-wan,helper=/home/yousong/.usr/libexec/qemu-bridge-helper device_add virtio-net-pci,id=devwan2,netdev=wan2,mac=11:22:33:22:11:00 The config was formed by selecting target x86/64 first, then select CONFIG_HOTPLUG_PCI and CONFIG_HOTPLUG_PCI_ACPI with make kernel_menuconfig CONFIG_TARGET=subtarget The following text tries to explain how the current config was formed 1. CONFIG_PCI_LABEL and CONFIG_ATA_PIIX were removed because they were already enabled in x86 platform config 2. CONFIG_ATA_SFF was removed because it was enabled in generic config 3. CONFIG_NLS was removed because it will be selected by CONFIG_PCI_LABEL Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* tools: remove old mkdosfs symlink from dosfstoolsÁlvaro Fernández Rojas2016-10-124-4/+4
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ar71xx: add userspace support for D-Link DIR-869 A1, generate imagesFlorian Beier2016-10-116-1/+25
| | | | | | Signed-off-by: Florian Beier <beier.florian@gmail.com> [Matthias Schiffer: fix factory image, improve commit message] Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: add kernel support for D-Link DIR-869 A1Matthias Schiffer2016-10-117-0/+193
| | | | Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: add back SEAMA header checksum fix (as used on ramips)Matthias Schiffer2016-10-111-0/+17
| | | | | | | | The D-Link DIR-869 A1 doesn't accept images with the jffs2 marker added after the checksummed range, so we need to include it in the checksum and fix it on first boot. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: avoid double lzma compression of kernel for SEAMA imagesMatthias Schiffer2016-10-111-1/+1
| | | | | | | | Use relocation loader instead of lzma loader. Tested on D-Link DIR-869 A1. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: add relocation loaderMatthias Schiffer2016-10-112-0/+15
| | | | Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: clean up SEAMA image build codeMatthias Schiffer2016-10-111-34/+18
| | | | | | | | | | | Split seama-factory and seama-sysupgrade into smaller pieces (similar to the ramips code) to make the image generation more flexible. Also use standard pad-offset instead of adding a block of zeros at the beginning of the image that is later cut off again. Standard pad-rootfs can be used as the seal header doesn't contain an image size or checksum. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* lantiq: fix lantiq-dsl output spamMathias Kresin2016-10-111-1/+1
| | | | | | | | | | | | | | | | | In case the adsl/vdsl service is disabled intentional, the output is cluttered with the following message multiple times if the status of the dsl line is queried: killall: vdsl_cpe_control: no process killed If the dsl line status is queried by LuCI, the logfile is spammed with the message. Fix the issue by using killall in quite mode. In quite mode killall still returns a non-zero value if the to be killed process can not be found so that existing logic based on the return value still works. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: build image for Archer C7 v2 ILAmir Rachum2016-10-091-1/+11
| | | | | | | TP-Link uses a different region coding mechanism for IL firmware for the Archer C7 v2. Instead of of setting the region, they set a different TPLINK_HWREV. Signed-off-by: Amir Rachum <amir@rachum.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 02:31:06 +0000