default initramfs for 5.4 kernel is larger than 4M, causing build error
for oversized initramfs image.
disable these images because we have no mechanism for ignoring initramfs
errors and the squashfs image will be larger than initramfs anyway.
Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
(cherry picked from commit d7d46da938)
Before this commit, it was assumed that mkhash is in the PATH. While
this was fine for the normal build workflow, this led to some issues if
make TOPDIR="$(pwd)" -C "$pkgdir" compile
was called manually. In most of the cases, I just saw warnings like this:
make: Entering directory '/home/.../package/gluon-status-page'
bash: line 1: mkhash: command not found
bash: line 1: mkhash: command not found
bash: line 1: mkhash: command not found
bash: line 1: mkhash: command not found
bash: line 1: mkhash: command not found
bash: line 1: mkhash: command not found
bash: line 1: mkhash: command not found
bash: line 1: mkhash: command not found
[...]
While these were only warnings and the package still compiled sucessfully,
I also observed that some package even fail to build because of this.
After applying this commit, the variable $(MKHASH) is introduced. This
variable points to $(STAGING_DIR_HOST)/bin/mkhash, which is always the
correct path.
Signed-off-by: Leonardo Mörlein <me@irrelefant.net>
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
The majority of our targets provide a default value for the variable
SUPPORTED_DEVICES, which is used in images to check against the
compatible on a running device:
SUPPORTED_DEVICES := $(subst _,$(comma),$(1))
At the moment, this is implemented in the Device/Default block of
the individual targets or even subtargets. However, since we
standardized device names and compatible in the recent past, almost
all targets are following the same scheme now:
device/image name: vendor_model
compatible: vendor,model
The equal redundant definitions are a symptom of this process.
Consequently, this patch moves the definition to image.mk making it
a global default. For the few targets not using the scheme above,
SUPPORTED_DEVICES will be defined to a different value in
Device/Default anyway, overwriting the default. In other words:
This change is supposed to be cosmetic.
This can be used as a global measure to get the current compatible
with: $(firstword $(SUPPORTED_DEVICES))
(Though this is not precisely an achievement of this commit.)
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Signed-off-by: CN_SZTL <cnsztl@project-openwrt.eu.org>
IMAGE_SIZE is widely used in many targets. Declare it in the default template to
clean up redundant code. This also prevents deriving IMAGE_SIZE unintentionally
from the previously defined device.
While at it, remove duplicate KERNEL_SIZE declaration.
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
WIZnet WizFi630s board name is written slightly different it its OEM
OpenWrt firmware. This causes an incompatibility warning during flashing
with sysupgrade. This patch is adding the vendor board name to the
supported devices list to avoid this warning. For initial flashing you
can use sysupgrade via command line or luci beside of TFTP.
Do not keep the OEM configuration during sysupgrade.
Signed-off-by: Tobias Welz <tw@wiznet.eu>
For the TP-Link 4M devices with tplink-v2-image recipe
(mktplinkfw2.c), there are two different flash layouts based
on the size of the (u)boot partition:
device uboot OEM firmware OpenWrt (incl. config)
tl-wr840n-v5 0x20000 0x3c0000 0x3d0000
tl-wr841n-v14 0x10000 0x3d0000 0x3e0000
In both cases, the 0x10000 config partition is used for the firmware
partition as well due to the limited space available and since it's
recreated by the OEM firmware anyway.
However, the TFTP flashing process will only copy data up to the
size of the initial (OEM) firmware size. Therefore, while we can
use the bigger partition to have additional erase blocks on the
device, we have to limit the image sizes to the TFTP limits.
So far, only one layout definition has been set up in mktplinkfw2.c
for 4M mediatek devices. This adds a second one and assigns them
to the devices so the image sizes are correctly restrained.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
ZyXEL Keenetic has a USB port. Thus, DWC2 USB controller driver should
be in the default image for this device.
Fixes: a7cbf59e0e ("ramips: add new device ZyXEL Keenetic as kn")
Signed-off-by: Alexey Dobrovolsky <dobrovolskiy.alexey@gmail.com>
[fixed whitespace issue]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
(backported from commit 0a182fcba6)
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Now that check-size uses IMAGE_SIZE by default, we can skip the argument from
image recipes to reduce redundancy.
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
[do not touch ar71xx]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: increase HiWiFi HC5962 kernel partition to 4M
Increase kernel partition because 2M is insufficient for 4.19
Because the partition changes, previous version of OpenWrt cannot upgrade to this version
Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* ramips: use all reserved space for HiWiFi HC5962
Idea was from ad6c6361f9 ("ath79: enable all space on Netgear ar9344-based WNDR routers")
These stock partitons: "backup", "hw_panic", "overly", firmware_backup", "opt"
do not contain any device-specific data and can be used for /overlay, resulting in
121M space
Users should erase those partitions with command `mtd erase <partition name>` prior to
upgrading to this version
Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
Co-authored-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* ramips: add xiaomi_miwifi-r3 support
Specification:
- CPU: 580 MHz
- Flash size: 128 MiB NAND
- RAM size: 128 MiB DDR2
- Wireless No1: SoC-integrated: MT7620A 2x2 MIMO 802.11b/g/n (2.4 GHz)
- Wireless No2: On-board chip: MT7612E 2x2 MIMO 802.11a/n/ac (5 GHz)
- Switch: MT7620 built-in 10/100 switch w/ vlan support
- USB: 2.0 x1
Flash instructions:
1. access ssh via https://wiki.openwrt.org/toh/xiaomi/mir3
2. in ssh:
nvram set flag_last_success=1
nvram set boot_wait=on
nvram set uart_en=1
nvram commit
mtd write lede-ramips-mt7620-miwifi-r3-squashfs-kernel1.bin kernel1
mtd write lede-ramips-mt7620-miwifi-r3-squashfs-rootfs0.bin rootfs0
reboot
If you want to revert back to stock fw while on LEDE:
insert usb stick (FAT/FAT32) with stock fw renamed to miwifi.bin
fw_setenv flag_last_success 0
power off the device
hold the reset button and power on the device, keep holding the reset button until yellow led starts blinking.
Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
* ramips: add mt7620-nand driver for NAND flash
This add the mt7620-nand driver
and enable nand ubifs for subtarget mt7620
Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
Co-authored-by: Chen Minqiang <ptpt52@gmail.com>
Specification:
- CPU: 580 MHz
- Flash size: 128 MiB NAND
- RAM size: 128 MiB DDR2
- Wireless No1: SoC-integrated: MT7620A 2x2 MIMO 802.11b/g/n (2.4 GHz)
- Wireless No2: On-board chip: MT7612E 2x2 MIMO 802.11a/n/ac (5 GHz)
- Switch: MT7620 built-in 10/100 switch w/ vlan support
- USB: 2.0 x1
Flash instructions:
1. access ssh via https://wiki.openwrt.org/toh/xiaomi/mir3
2. in ssh:
nvram set flag_last_success=1
nvram set boot_wait=on
nvram set uart_en=1
nvram commit
mtd write lede-ramips-mt7620-miwifi-r3-squashfs-kernel1.bin kernel1
mtd write lede-ramips-mt7620-miwifi-r3-squashfs-rootfs0.bin rootfs0
reboot
If you want to revert back to stock fw while on LEDE:
insert usb stick (FAT/FAT32) with stock fw renamed to miwifi.bin
fw_setenv flag_last_success 0
power off the device
hold the reset button and power on the device, keep holding the reset button until yellow led starts blinking.
Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
Increase kernel partition because 2M is insufficient for 4.19
Because the partition changes, previous version of OpenWrt cannot upgrade to this version
Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
Specifications:
* SoC: MT7621AT
* RAM: 128MB
* Flash: 16MB NOR SPI flash
* WiFi: MT7615N (2.4GHz) and MT7615N (5Ghz)
* LAN: 5x1000M
* Firmware layout is Uboot with extra 96 bytes in header
* Base PCB is AP-MTKH7-0002
* LEDs Power Green,Power Orange,Internet Green,Internet Orange
* LEDs "2.4G" Green & "5G" Green connected directly to wifi module
* Buttons Reset,WPS,WIFI
Flash instruction:
Upload image via emergency recovery mode via Windows "not working with Linux"
Push and hold reset button (on the bottom of the device) until power led starts flashing (about 10 secs or so) while plugging in the power cable.
Give it ~30 seconds, to boot the recovery mode GUI
Connect your client computer to LAN1 of the device
Set your client IP address manually to 192.168.0.2 / 255.255.255.0.
Call the recovery page for the device at http://192.168.0.1
Use the provided emergency web GUI to upload and flash a new firmware to the device
MAC addresses:
lan factory 0xe000 *:55 (label)
wan factory 0xe006 *:58
2.4 GHz factory 0x0004 *:56
5.0 GHz factory 0x8004 *:57
Signed-off-by: Alan Luck <luckyhome2008@gmail.com>
This commit sync ramips source code from openwrt master.
1. ramips: gsw_mt7621: disable PORT 5 MAC RX/TX flow control by default
2. ramips: allow to set switchdev by board in ramips_set_preinit_iface
3. kernel: fix typos in KernelPackage description
* generic: support mtd-mac-address-ascii
It supports formats of both 001122334455 and 00:11:22:33:44:55
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* ramips: add JDCloud
Co-authored-by: Yousong Zhou <yszhou4tech@gmail.com>
