Kevin Darbyshire-Bryant [Fri, 26 Jul 2019 13:19:22 +0000 (14:19 +0100)]
toolchain/fortify-headers: Update to 1.1
Update fortify-headers to 1.1
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Daniel Golle [Fri, 26 Jul 2019 21:45:47 +0000 (23:45 +0200)]
tools/mklibs: update to 0.1.44 and convert to Python 3
Since the switch to Python 3 build fails if CONFIG_USE_MKLIBS is set
("Strip unnecessary functions from libraries" in menuconfig) as
mklibs hasn't been converted to run on Python 3.
* update to most recent upstream version which brings some
reproducibility fixes
* converted to Python 3 using 2to3
* fixed mixed tab/spaces indentation
* fixed use of string.* functions
* some more minor fixes to make Python 3 happy
Fixes commit
19938c8de7 ("build: switch to Python 3")
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Biwen Li [Fri, 26 Jul 2019 08:23:53 +0000 (16:23 +0800)]
tfa-layerscape: fix create_pbl and byte_swap host build
- make create_pbl and byte_swap as host tools
- fix a bug that maybe use the cross compiler
to compile create_pbl and byte_swap:
# -a option appends the image for Chassis 3 devices in case of non secure boot
aarch64-openwrt-linux-musl-gcc -Wall -Werror -pedantic -std=c99 -O2
-DVERSION=v1.5(release):
reboot-10604-ge9216b3336 -D_GNU_SOURCE -D_XOPEN_SOURCE=700
-c -o create_pbl.o create_pbl.c
cc1: note: someone does not honour COPTS correctly, passed 0 times
LD create_pbl
/usr/bin/ld: create_pbl.o: Relocations in generic ELF (EM: 183)
/usr/bin/ld: create_pbl.o: Relocations in generic ELF (EM: 183)
/usr/bin/ld: create_pbl.o: Relocations in generic ELF (EM: 183)
create_pbl.o: error adding symbols: File in wrong format
collect2: error: ld returned 1 exit status
Makefile:43: recipe for target create_pbl failed
make[4]: *** [create_pbl] Error 1
plat/nxp/tools/pbl_ch2.mk:45: recipe for target pbl failed
make[3]: *** [pbl] Error 2
- add tfa- prefix to all tools in order to avoid future clashes with
other toolnames
Signed-off-by: Biwen Li <biwen.li@nxp.com>
[added missing HOST_CFLAGS, added tfa- prefix to the tools]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
NOGUCHI Hiroshi [Thu, 25 Jul 2019 23:11:48 +0000 (08:11 +0900)]
ramips: add support for Fon FON2601
FON2601 is a wireless router.
Specification:
- SoC: Mediatek MT7620A (580MHz)
- RAM: 128 MiB
- ROM: 16 MiB SPI Flash
- Wireless:
for 11b/g/n (upto 300 Mbps): MT7620A built-in WMAC
for 11a/n/ac (upto 867 Mbps): MT7662E
- Ethernet LAN: 1 port, upto 100 Mbps
- Ethernet WAN: 1 port, upto 1000 Mbps
- USB: 1 port (USB 2.0 host)
- LEDs: 4 (all can be controlled by SoC's GPIO)
- buttons: 1 (Displayed as "WPS" on enclosure)
- serial port: 57600n8
pins: Vcc(3.3V), Rx, Tx, GND
(left to right, viewed from outside of board)
Installation (only available via UART):
1. download sysupgrade binary image by wget command
2. write sysupgrade binary image to Flash
command is:
mtd write sysupgrade.bin firmware
3. reboot
Important Notice:
Only one button is displayed as "WPS" on enclosure.
However, it is configured as "reset" (factory resetting feature).
Signed-off-by: NOGUCHI Hiroshi <drvlabo@gmail.com>
[removed unrelated openwrt-keyring revert, missing -Wall for uimage_padhdr]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Tue, 4 Dec 2018 13:47:23 +0000 (14:47 +0100)]
autotools.mk: autoreconf: fix missing install-sh
I'm trying to create a package for libgpiod, which uses
AC_CONFIG_AUX_DIR macro, which is probably leading to the following
configure error:
autoreconf: running: /openwrt.git/staging_dir/host/bin/libtoolize --force
OpenWrt-libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `autostuff'.
OpenWrt-libtoolize: linking file `autostuff/ltmain.sh'
OpenWrt-libtoolize: putting macros in `m4'.
...
configure: error: cannot find install-sh, install.sh, or shtool in autostuff "."/autostuff
>From the build output it's clear, that libtoolize isn't installing
install-sh symlink, because libtoolize would install install-sh only if
it's being run with --install parameter. Corresponding part in
libtoolize:
if $opt_install; then
func_config_update config.guess \
"$pkgdatadir/config" "$auxdir" pkgconfig_header
func_config_update config.sub \
"$pkgdatadir/config" "$auxdir" pkgconfig_header
func_install_update install-sh \
"$pkgdatadir/config" "$auxdir" pkgconfig_header
fi
func_ltmain_update ltmain.sh \
"$pkgdatadir/config" "$auxdir" pkgconfig_header
Adding --install parameter to libtoolize fixes this build issue:
autoreconf: running: /openwrt.git/staging_dir/host/bin/libtoolize --install --force
OpenWrt-libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `autostuff'.
OpenWrt-libtoolize: linking file `autostuff/config.guess'
OpenWrt-libtoolize: linking file `autostuff/config.sub'
OpenWrt-libtoolize: linking file `autostuff/install-sh'
OpenWrt-libtoolize: linking file `autostuff/ltmain.sh'
OpenWrt-libtoolize: putting macros in `m4'.
Cc: Felix Fietkau <nbd@nbd.name>
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Thu, 25 Jul 2019 07:21:42 +0000 (09:21 +0200)]
wireless-regdb: set PKGARCH:=all
As it's an architecture-independent binary file.
Ref: https://github.com/openwrt/openwrt/pull/1521#issuecomment-
514687053
Suggested-by: Deng Qingfang <dengqf6@mail2.sysu.edu.cn>
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Mon, 18 Mar 2019 21:40:36 +0000 (21:40 +0000)]
wireless-regdb: prefer python provided by make variable
Usage of predefined make variables is preferred.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Zachary Riedlshah [Wed, 5 Jun 2019 10:58:19 +0000 (22:58 +1200)]
wireless-regdb: update to 2019.06.03
Fixes build issues on a python3 host (issues with the print statement
formatting in the current build).
Includes 100-regdb-write-firmware-file-format-version-code-20.patch and
other fixes.
Closes bugs.openwrt.org/index.php?do=details&task_id=1605.
Uses the tarball as requested.
Signed-off-by: Zachary Riedlshah <git@zacharyrs.me>
Petr Štetiar [Wed, 20 Mar 2019 08:52:58 +0000 (09:52 +0100)]
build: cleanup possibly dangling Python 2 host symlink
When bumping buildroot to Python 3, we need to assure, that Python
symlink in staging bin directory points to Python >= 3.5 as well.
We can't rely completly just on SetupHostCommand as its executed only in
cases when the $(STAGING_DIR_HOST)/bin/python doesn't already exist, so
we need to remove it before running SetupHostCommand.
Acked-by: Yousong Zhou <yszhou4tech@gmail.com>
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Tue, 19 Mar 2019 12:02:07 +0000 (13:02 +0100)]
build: switch to Python 3
This patch switches Python used in buildroot to Python 3 as Python 2.x
series is going to be EOL relatively soon[1].
"Being the last of the Python 2.x series, 2.7 will have an extended
period of maintenance. Specifically, 2.7 will receive bugfix support
until January 1, 2020. After the last release, 2.7 will receive no
support."
It seems like Python 3 is going to be needed in order to support Meson
build system which has gained some traction recently.
Build tested on following targets:
ath79/generic
imx6/generic
ipq40xx/generic
lantiq/xway
layerscape/armv7 (broken)
layerscape/armv8_32b (broken)
layerscape/armv8_64b (broken)
mvebu/cortexa72
ramips/mt7621
ramips/mt7620
sunxi/cortexa7
x86/64
Layerscape targets are unfortunately left broken as their ls-rcw
firmware package uses Python 2 and converting it to Python 3 would take
more then reasoanble amount of time (I've tried to fix it already) and
would be better fixed by someone who can even run test it.
Run tested on ath79 (Archer C7 v5), ipq40xx (nbg6617) and x86_64 (QEMU
and apu2).
1. https://www.python.org/dev/peps/pep-0373/
Ref: PR#1937
Cc: Yangbo Lu <yangbo.lu@nxp.com>
Cc: Mathew McBride <matt@traverse.com.au>
Acked-by: Yousong Zhou <yszhou4tech@gmail.com>
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Yangbo Lu [Wed, 19 Jun 2019 03:12:19 +0000 (11:12 +0800)]
layerscape: convert to python3 for rcw
Python 2.7 will not be maintained past 2020. Let's convert
to python3 for rcw. Also drop byte swapping since TF-A had
been already used which handled byte swapping instead.
Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
Petr Štetiar [Tue, 19 Mar 2019 12:34:26 +0000 (12:34 +0000)]
tools/scons: switch to Python 3
Build tested on ath79 with following packages from packages feed which
build depends on scons. None of them build anymore as it seems, that the
SConscripts are written for Python2.
* packages/net/iotivity (KO, doesn't build even with latest 1.3.1 release)
SyntaxError: invalid syntax
File "/openwrt/build_dir/target-mips_24kc_musl/iotivity-1.2.1/build_common/SConscript", line 40
print "\nError: Current system (%s) isn't supported\n" % host
LookupError: unknown encoding: string_escape:
File "/home/petr/testing/openwrt/build_dir/target-mips_24kc_musl/iotivity-1.3.1/SConstruct", line 28:
SConscript('build_common/SConscript')
* packages/net/smartsnmpd (KO, seems dead, no commit since 2015):
SyntaxError: Missing parentheses in call to 'print'
File "/openwrt/build_dir/target-mips_24kc_musl/smartsnmpd-2014-08-13/SConstruct", line 156
print "Can't find liblua or liblua5.1!"
* packages/utils/gpsd (KO, doesn't build even with latest 3.18.1 release):
AttributeError: 'list' object has no attribute 'keys':
File "/openwrt/build_dir/target-mips_24kc_musl/gpsd-3.18.1/SConstruct", line 1758:
all_manpages = list(base_manpages.keys()) + list(python_manpages.keys())
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Tue, 19 Mar 2019 10:30:34 +0000 (10:30 +0000)]
scripts/jungo-image: convert to Python 3 with 2-to-3
Let's convert the script to Python 3.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Tue, 19 Mar 2019 10:29:40 +0000 (10:29 +0000)]
scripts/dl_github_archive.py: convert to Python 3 with 2-to-3
Let's convert the script to Python 3.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Tue, 19 Mar 2019 10:31:22 +0000 (10:31 +0000)]
tools/b43-tools/b43-fwsquash: convert to Python 3 with 2-to-3
Let's convert the script to Python 3.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Jo-Philipp Wich [Thu, 25 Jul 2019 17:39:51 +0000 (19:39 +0200)]
openwrt-keyring: update to Git HEAD
8080ef3 usign: add 19.07 release build pubkey
e24fe0d usign: use distro agnostic comments
251ded7 usign: fix filename of Stijn's usign key
14f0efc gpg: update snapshots public signing key
14f845b gpg: replace my public GPG key
4f735b8 gpg: add OpenWrt 19.07 signing key
228f8da gpg: add OpenWrt 18.06 v2 signing key
36057d9 gpg: update LEDE 17.01 public signing key
f2989ab Add my public GPG and usign key
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
David Bauer [Thu, 25 Jul 2019 15:25:34 +0000 (17:25 +0200)]
ath79: remove lines-initial-states property
The lines-initial-states property was an early attempt to set the latch
bit of the shift register on driver probe. It is not implemented in the
driver and was rejected upstream. The latch bit was always set by a GPIO
hog, so this property is safe to drop.
Signed-off-by: David Bauer <mail@david-bauer.net>
Chuanhong Guo [Thu, 25 Jul 2019 14:17:51 +0000 (22:17 +0800)]
ramips: drop an empty case in 02_network
There's an empty case in 02_network introduced by last commit. Drop it.
Fixes: ee650ba46c ("ramips: remove needless setting of lan_mac to eth0 in 02_network")
Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
Adrian Schmutzler [Sun, 21 Jul 2019 00:05:53 +0000 (02:05 +0200)]
ramips: remove needless setting of lan_mac to eth0 in 02_network
This removes superfluous lines like
lan_mac=$(cat /sys/class/net/eth0/address)
Since lan_mac only sets the MAC address for eth0.1, these lines
can be safely removed as the address will be inherited from eth0
anyway.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Thu, 11 Jul 2019 21:39:10 +0000 (23:39 +0200)]
ramips: consistently use lower-case factory partition label
The vast majority of devices labels "factory" partition with lower
case. Convert the small fraction with capital letter to that and
merge another case in 02_network.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Thu, 11 Jul 2019 21:01:05 +0000 (23:01 +0200)]
ramips: consolidate MAC address cases in 02_network
This just merges some duplicate definitions and consolidates lines.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Signed-off-by: Chuanhong Guo <gch981213@gmail.com> [merge duplicated
cases for phicomm k2p]
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:40 +0000 (14:55 +0200)]
ramips: use kiB instead of B for IMAGE_SIZE
This cosmetical patch is just meant to make comparing/checking
IMAGE_SIZE values easier.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 22 Jul 2019 16:09:57 +0000 (18:09 +0200)]
ramips: remove ralink_default_fw_size_xxx variables
There are frequent examples of the ralink_default_fw_size_xxx
variables being used to "roughly" set flash size without caring
about the actual size of the firmware partition.
To discourage this behavior, this patch removes the variables and
just sets IMAGE_SIZE by its numeric value for each target.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:37 +0000 (14:55 +0200)]
ramips: remove default IMAGE_SIZE for ramips target
Currently, ramips target defines 0x7b0000 as default IMAGE_SIZE
for all devices in ramips target, i.e. this will be set if a
device does not specify IMAGE_SIZE itself.
From 92 devices using that default due to a "missing" IMAGE_SIZE,
14 were incorrect by a small amount (i.e. still "8M" flash) and
12 were completely off ("16M", "4M", ...).
This patch thus removes the _default_ IMAGE_SIZE and defines
IMAGE_SIZE for each device individually. This should indicate to
people supporting new devices that this parameter has to be cared
about.
For the present code, this patch is cosmetical.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:34 +0000 (14:55 +0200)]
ramips/rt305x: fix IMAGE_SIZE for all devices
This fixes IMAGE_SIZE for all devices based on the partition size
given in DTS:
DEVICE *.MK *.DTS VERDICT
7links_px-4885-4m (4M) 0x3b0000
7links_px-4885-8m - 0x7b0000 default
8devices_carambola - 0x7b0000 default
accton_wr6202 - 0x7b0000 default
airlive_air3gii (4M) 0x3b0000
alfa-network_w502u - 0x7b0000 default
allnet_all0256n-4m (4M) 0x3b0000
allnet_all0256n-8m - 0x7b0000 default
allnet_all5002 32448k 0x1fb0000
allnet_all5003 32448k 0x1fb0000
alphanetworks_asl26555-16m 15872k 0xf80000
alphanetworks_asl26555-8m 7744k 0x790000
arcwireless_freestation5 - 0x7b0000 default
argus_atp-52b 7808k 0x7a0000
asiarf_awapn2403 (4M) 0x3b0000
asiarf_awm002-evb-4m (4M) 0x3b0000
asiarf_awm002-evb-8m - 0x7b0000 default
asus_rt-g32-b1 (4M) 0x3b0000
asus_rt-n10-plus (4M) 0x3b0000
asus_rt-n13u - 0x7b0000 default
asus_wl-330n (4M) 0x3b0000
asus_wl-330n3g (4M) 0x3b0000
aximcom_mr-102n - 0x790000 wrong
aztech_hw550-3g - 0x7b0000 default
belkin_f5d8235-v2 7744k 0x790000
belkin_f7c027 7616k 0x770000
buffalo_whr-g300n
3801088 0x3a0000
dlink_dap-1350 7488k 0x750000
dlink_dcs-930 (4M) 0x3b0000
dlink_dcs-930l-b1 (4M) 0x3b0000
dlink_dir-300-b1 (4M) 0x3b0000
dlink_dir-300-b7 (4M) 0x7b0000 wrong
dlink_dir-320-b1 - 0x7b0000 default
dlink_dir-600-b1 (4M) 0x3b0000
dlink_dir-610-a1 (4M) 0x3b0000
dlink_dir-615-d (4M) 0x3b0000
dlink_dir-615-h1 (4M) 0x3b0000
dlink_dir-620-a1 - 0x7b0000 default
dlink_dir-620-d1 - 0x7b0000 default
dlink_dwr-512-b 7800k 0x7e0000 wrong
easyacc_wizard-8800 - 0x7b0000 default
edimax_3g-6200n 3648k 0x390000
edimax_3g-6200nl 3648k 0x390000
engenius_esr-9753 (4M) 0x3b0000
fon_fonera-20n - 0x7b0000 default
hame_mpr-a1 (4M) 0x3b0000
hame_mpr-a2 - 0x7b0000 default
hauppauge_broadway 7744k 0x790000
hilink_hlk-rm04 - 0x3b0000 wrong
hootoo_ht-tm02 - 0x7b0000 default
huawei_d105 (4M) 0x3b0000
huawei_hg255d 15744k 0xf60000
intenso_memory2move - 0x7b0000 default
jcg_jhr-n805r (4M) 0x3b0000
jcg_jhr-n825r (4M) 0x3b0000
jcg_jhr-n926r (4M) 0x3b0000
mofinetwork_mofi3500-3gn - 0x7b0000 default
netcore_nw718 3712k 0x3a0000
netgear_wnce2001 (4M) 0x350000 wrong
nexaira_bc2 - 0x7b0000 default
nexx_wt1520-4m (4M) 0x3b0000
nexx_wt1520-8m - 0x7b0000 default
nixcore_x1-16m 16064k 0xfb0000
nixcore_x1-8m 7872k 0x7b0000
olimex_rt5350f-olinuxino - 0x7b0000 default
olimex_rt5350f-olinuxino-evb - 0x7b0000 default
omnima_miniembplug - 0x7b0000 default
omnima_miniembwifi - 0x7b0000 default
petatel_psr-680w (4M) 0x3b0000
planex_mzk-dp150n (4M) 0x3b0000
planex_mzk-w300nh2 3648k 0x390000
planex_mzk-wdpr - 0x680000 wrong
poray_ip2202 - 0x7b0000 default
poray_m3 (4M) 0x3b0000
poray_m4-4m (4M) 0x3b0000
poray_m4-8m - 0x7b0000 default
poray_x5 - 0x7b0000 default
poray_x8 - 0x7b0000 default
prolink_pwh2004 - 0x7b0000 default
ralink_v22rw-2x2 (4M) 0x3b0000
sitecom_wl-351 (4M) 0x3b0000
skyline_sl-r7205 (4M) 0x3b0000
sparklan_wcr-150gn (4M) 0x3b0000
teltonika_rut5xx - 0xfb0000 wrong
tenda_3g150b (4M) 0x3b0000
tenda_3g300m (4M) 0x3b0000
tenda_w150m (4M) 0x3b0000
tenda_w306r-v2 (4M) 0x3b0000
trendnet_tew-638apb-v2 (4M) 0x3b0000
trendnet_tew-714tru - 0x7b0000 default
unbranded_a5-v11 (4M) 0x3b0000
unbranded_wr512-3gn-4m (4M) 0x3b0000
unbranded_wr512-3gn-8m - 0x7b0000 default
unbranded_xdx-rn502j (4M) 0x3b0000
upvel_ur-326n4g (4M) 0x3b0000
upvel_ur-336un - 0x7b0000 default
vocore_vocore-16m 16064k 0xfb0000
vocore_vocore-8m 7872k 0x7b0000
wansview_ncs601w - 0x7b0000 default
wiznet_wizfi630a (16M) 0xfb0000
zorlik_zl5900v2 - 0x7b0000 default
zyxel_keenetic (4M) 0x3b0000
zyxel_keenetic-start (4M) 0x3b0000
zyxel_nbg-419n (4M) 0x3b0000
zyxel_nbg-419n-v2 (8M) 0x7b0000
No verdict means that the device is correctly set.
Legend:
( ): Value is set via ralink_default_fw_size_xxM
[ ]: Value is derived from parent definition
- : Value is not set and derived from default definition
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:31 +0000 (14:55 +0200)]
ramips/rt288x,rt3883: fix IMAGE_SIZE for all devices
This fixes IMAGE_SIZE for all devices based on the partition size
given in DTS:
DEVICE *.MK *.DTS VERDICT
airlink101_ar670w (4M) 0x3c0000 wrong
airlink101_ar725w - 0x3B0000 wrong
asus_rt-n15 (4M) 0x3b0000
belkin_f5d8235-v1 7744k 0x7b0000 wrong
buffalo_wli-tx4-ag300n (4M) 0x3b0000
buffalo_wzr-agl300nh (4M) 0x3b0000
dlink_dap-1522-a1
3801088 0x3a0000
ralink_v11st-fe (4M) 0x003b0000
asus_rt-n56u - 0x007b0000 default
belkin_f9k1109v1 7224k 0x7a0000 wrong
dlink_dir-645 - 0x7b0000 default
edimax_br-6475nd 7744k 0x00790000
loewe_wmdr-143n - 0x7b0000 default
omnima_hpm 16064k 0x00fb0000
samsung_cy-swr1100 - 0x7b0000 default
sitecom_wlr-6000 7244k 0x713000
trendnet_tew-691gr - 0x007b0000 default
trendnet_tew-692gr - 0x007b0000 default
No verdict means that the device is correctly set.
Legend:
( ): Value is set via ralink_default_fw_size_xxM
[ ]: Value is derived from parent definition
- : Value is not set and derived from default definition
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:28 +0000 (14:55 +0200)]
ramips/mt76x8: fix IMAGE_SIZE for all devices
This fixes IMAGE_SIZE for all devices based on the partition size
given in DTS:
DEVICE *.MK *.DTS VERDICT
alfa-network_awusfree1 (8M) 0x7b0000
buffalo_wcr-1166ds - 0x7c0000 wrong
cudy_wr1000 (8M) 0x7b0000
d-team_pbr-d1 (16M) 0x0fb0000
duzun_dm06 - 0x7b0000 default
glinet_gl-mt300n-v2 16064k 0xfb0000
glinet_vixmini 7872k 0x7b0000
hilink_hlk-7628n (32M) 0x1fb0000
hiwifi_hc5661a (16M) 0xf70000 wrong
hiwifi_hc5861b 15808k 0xf70000
mediatek_linkit-smart-7688 (32M) 0x1fb0000
mediatek_mt7628an-eval-board (4M) 0x7b0000 wrong
mercury_mac1200r-v2 - 0x7c0000 wrong
netgear_r6120 15744k 0xf60000
onion_omega2 (16M) 0xfb0000
onion_omega2p (32M) 0x1fb0000
rakwireless_rak633 - 0x7b0000 default
skylab_skw92a 16064k 0xfb0000
tama_w06 15040k 0xeb0000
totolink_lr1200 7872k 0x7b0000
tplink_archer-c20-v4 7808k 0x7a0000
tplink_archer-c50-v3 7808k 0x7a0000
tplink_archer-c50-v4 7616k 0x770000
tplink_tl-mr3020-v3 7808k 0x7a0000
tplink_tl-mr3420-v5 7808k 0x7a0000
tplink_tl-wa801nd-v5 7808k 0x7a0000
tplink_tl-wr802n-v4 7808k 0x7a0000
tplink_tl-wr840n-v4 7808k 0x7a0000
tplink_tl-wr840n-v5 3904k 0x3d0000
tplink_tl-wr841n-v13 7808k 0x7a0000
tplink_tl-wr841n-v14 3968k 0x3e0000
tplink_tl-wr842n-v5 7808k 0x7a0000
tplink_tl-wr902ac-v3 7808k 0x7a0000
unielec_u7628-01-128m-16m 16064k 0xfb0000
vocore_vocore2 (16M) 0xfb0000
vocore_vocore2-lite (16M) 0x7b0000 wrong
wavlink_wl-wn570ha1 (8M) 0x7b0000
wavlink_wl-wn575a3 (8M) 0x7b0000
widora_neo-16m (16M) 0x0fb0000
widora_neo-32m (32M) 0x1fb0000
wiznet_wizfi630s (32M) 0x1fb0000
wrtnode_wrtnode2p (16M) 0x1fb0000 wrong
wrtnode_wrtnode2r (16M) 0x1fb0000 wrong
xiaomi_mir4a-100m 14976k 0xea0000
xiaomi_miwifi-nano (16M) 0xfb0000
zbtlink_zbt-we1226 (8M) 0x7b0000
zyxel_keenetic-extra-ii 14912k 0xe90000
No verdict means that the device is correctly set.
Legend:
( ): Value is set via ralink_default_fw_size_xxM
[ ]: Value is derived from parent definition
- : Value is not set and derived from default definition
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:24 +0000 (14:55 +0200)]
ramips/mt7621: fix IMAGE_SIZE for all devices
This fixes IMAGE_SIZE for all devices based on the partition size
given in DTS:
DEVICE *.MK *.DTS VERDICT
afoundry_ew1200 (16M) 0xfb0000
asiarf_ap7621-001 (16M) 0xfa0000 wrong
buffalo_wsr-1166dhp (16M) 0xf90000 wrong
buffalo_wsr-600dhp (16M) 0xfb0000
dlink_dir-860l-b1 (16M) 0xfb0000
d-team_newifi-d2 (32M) 0x1fb0000
d-team_pbr-m1 (16M) 0xfb0000
elecom_wrc-1167ghbk2-s 15488k 0xf20000
elecom_wrc-1900gst 11264k 0xb00000
elecom_wrc-2533gst 11264k 0xb00000
firefly_firewrt (16M) 0xfb0000
gehua_ghl-r-001 (32M) 0x1fb0000
gnubee_gb-pc1 (32M) 0x1fb0000
gnubee_gb-pc2 (32M) 0x1fb0000
hiwifi_hc5962 (32M) 0x2000000 wrong (kernel + ubi)
iodata_wn-ax1167gr 15552k 0xf30000
iodata_wn-gx300gr
7798784 0x770000
lenovo_newifi-d1 (32M) 0x1fb0000
linksys_re6500 - 0x7b0000 default
mediatek_ap-mt7621a-v60 (8M) 0x7b0000
mediatek_mt7621-eval-board (4M) 0xec0000 wrong (rootfs)
mikrotik_rb750gr3 [16128k] 0xfc0000
mikrotik_rbm11g [16128k] 0xFC0000
mikrotik_rbm33g [16128k] 0xFC0000
mqmaker_witi-256m (16M) 0xfb0000
mqmaker_witi-512m (16M) 0xfb0000
mtc_wr1201 16000k 0xfa0000
netgear_ex6150 14848k 0xe80000
netgear_r6220 28672k 0x1c00000
netgear_r6350 40960k 0x2800000
netgear_wndr3700-v5 15232k 0xee0000
netis_wf-2881 129280k 0x7E40000
phicomm_k2p 15744k 0xf60000
planex_vr500
66453504 0x3fb0000 wrong
samknows_whitebox-v8 (16M) 0xfb0000
storylink_sap-g3200u3 - 0x7b0000 default
telco-electronics_x1 16064k 0xfb0000
thunder_timecloud - 0xfb0000 wrong
totolink_a7000r 16064k 0xfb0000
tplink_re350-v1 6016k 0x5e0000
ubiquiti_edgerouterx - 0xfa00000 wrong (kernel1 + ubi)
ubiquiti_edgerouterx-sfp - 0xfa00000 wrong (kernel1 + ubi)
unielec_u7621-06-256m-16m 16064k 0xfb0000
unielec_u7621-06-512m-64m 65216k 0x3fb0000
wevo_11acnas (16M) 0xfb0000
wevo_w2914ns-v2 (16M) 0xfb0000
xiaomi_mir3g 32768k 0x7980000 wrong (kernel + ubi)
xiaomi_mir3p (32M) 0xf980000 wrong (kernel + ubi)
xzwifi_creativebox-v1 (32M) 0x1fb0000
youhua_wr1200js 16064k 0xfb0000
youku_yk-l2 (16M) 0xfb0000
zbtlink_zbt-we1326 (16M) 0xfb0000
zbtlink_zbt-we3526 (16M) 0xfb0000
zbtlink_zbt-wg2626 (16M) 0xfb0000
zbtlink_zbt-wg3526-16m (16M) 0xfb0000
zbtlink_zbt-wg3526-32m (32M) 0x1fb0000
No verdict means that the device is correctly set.
Legend:
( ): Value is set via ralink_default_fw_size_xxM
[ ]: Value is derived from parent definition
- : Value is not set and derived from default definition
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:19 +0000 (14:55 +0200)]
ramips/mt7620: fix IMAGE_SIZE for all devices
This fixes IMAGE_SIZE for all devices based on the partition size
given in DTS:
DEVICE *.MK *.DTS VERDICT
aigale_ai-br100 7936k 0x7c0000
alfa-network_ac1200rm 16064k 0xfb0000
alfa-network_tube-e4g 16064k 0xfb0000
asus_rp-n53 - 0x7b0000 default
asus_rt-ac51u (16M) 0xfb0000
asus_rt-n12p - 0xfb0000 wrong
asus_rt-n14u - 0xfb0000 wrong
bdcom_wap2100-sk 15808k 0xf70000
buffalo_whr-1166d 15040k 0xfb0000 wrong
buffalo_whr-300hp2 6848k 0x7b0000 wrong
buffalo_whr-600d 6848k 0x7b0000 wrong
buffalo_wmr-300 - 0x7b0000 default
comfast_cf-wr800n - 0x7b0000 default
dlink_dch-m225 6848k 0x6b0000
dlink_dir-510l - 0xde0000 wrong
dlink_dir-810l 6720k 0x690000
dlink_dwr-116-a1 - 0x7e0000 wrong
dlink_dwr-118-a1 - 0xfe0000 wrong
dlink_dwr-118-a2 - 0xfe0000 wrong
dlink_dwr-921-c1 (16M) 0xfe0000 wrong
dlink_dwr-921-c3 [(16M)] 0xfe0000 wrong
dlink_dwr-922-e2 (16M) 0xfe0000 wrong
dovado_tiny-ac - 0x7b0000 default
edimax_br-6478ac-v2 7616k 0x00790000 wrong
edimax_ew-7476rpc 7744k 0x00790000
edimax_ew-7478ac 7744k 0x00790000
edimax_ew-7478apc 7744k 0x00790000
elecom_wrh-300cr (16M) 0xdf0000 wrong
glinet_gl-mt300a (16M) 0xf80000 wrong
glinet_gl-mt300n (16M) 0xf80000 wrong
glinet_gl-mt750 (16M) 0xf80000 wrong
head-weblink_hdrm200 16064k 0xfb0000
hiwifi_hc5661 15872k 0xf80000
hiwifi_hc5761 15872k 0xf80000
hiwifi_hc5861 15872k 0xf80000
hnet_c108
16777216 0xfb0000 wrong
iodata_wn-ac1167gr 6864k 0x6b4000
iodata_wn-ac733gr3 6992k 0x6d4000
kimax_u25awf-h1 16064k 0xfb0000
kimax_u35wf 16064k 0xfb0000
kingston_mlw221 15744k 0xf60000
kingston_mlwg2 15744k 0xf60000
lava_lr-25g001 - 0xfe0000 wrong
lenovo_newifi-y1 (16M) 0xfb0000
lenovo_newifi-y1s (16M) 0xfb0000
linksys_e1700 - 0x7b0000 default
microduino_microwrt 16128k 0xfc0000
netgear_ex2700 (4M) 0x3b0000
netgear_ex3700 7744k 0x790000
netgear_wn3000rp-v3 - 0x7b0000 default
nexx_wt3020-4m (4M) 0x3b0000
nexx_wt3020-8m - 0x7b0000 default
ohyeah_oy-0001 (16M) 0xfb0000
phicomm_k2g 7552k 0x760000
phicomm_psg1208 - 0x7b0000 default
phicomm_psg1218a - 0x7b0000 default
phicomm_psg1218b - 0x7b0000 default
planex_cs-qr10 - 0x7b0000 default
planex_db-wrt01 - 0x7b0000 default
planex_mzk-750dhp - 0x7b0000 default
planex_mzk-ex300np - 0x730000 wrong
planex_mzk-ex750np - 0x730000 wrong
ralink_mt7620a-evb - 0x7b0000 default
ralink_mt7620a-mt7530-evb - 0x7b0000 default
ralink_mt7620a-mt7610e-evb - 0x7b0000 default
ralink_mt7620a-v22sg-evb - 0x7f80000 wrong
ravpower_wd03 (8M) 0x7b0000
sanlinking_d240 (16M) 0xfb0000
sercomm_na930 20m 0x1400000
tplink_archer-c20i - 0x7a0000 wrong
tplink_archer-c20-v1 - 0x7a0000 wrong
tplink_archer-c2-v1 - 0x7a0000 wrong
tplink_archer-c50-v1 - 0x7a0000 wrong
tplink_archer-mr200 - 0x7b0000 default
vonets_var11n-300 (4M) 0x3b0000
wrtnode_wrtnode (16M) 0xfb0000
xiaomi_miwifi-mini (16M) 0xf80000 wrong
youku_yk1 (32M) 0x1fb0000
yukai_bocco - 0x7b0000 default
zbtlink_we1026-5g-16m
16777216 0xfb0000 wrong
zbtlink_zbt-ape522ii - 0xf80000 wrong
zbtlink_zbt-cpe102 - 0x760000 wrong
zbtlink_zbt-wa05 - 0x760000 wrong
zbtlink_zbt-we2026 - 0x760000 wrong
zbtlink_zbt-we826-16m (16M) 0xfb0000
zbtlink_zbt-we826-32m (32M) 0x1fb0000
zbtlink_zbt-we826-e 32448k 0x1fb0000
zbtlink_zbt-wr8305rt - 0x7b0000 default
zte_q7 - 0x7b0000 default
zyxel_keenetic-omni - 0x7b0000 default
zyxel_keenetic-omni-ii - 0x7b0000 default
zyxel_keenetic-viva 16064k 0xfb0000
No verdict means that the device is correctly set.
Legend:
( ): Value is set via ralink_default_fw_size_xxM
[ ]: Value is derived from parent definition
- : Value is not set and derived from default definition
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:14 +0000 (14:55 +0200)]
ramips: support IMAGE_SIZE in kiB for Build/trx
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:55:02 +0000 (14:55 +0200)]
ramips: fix ralink_default_fw_size_16M
In ramips, there are the following predefined values for IMAGE_SIZE
ralink_default_fw_size_4M
3866624 3776k 0x3B0000
ralink_default_fw_size_8M
8060928 7872k 0x7B0000
ralink_default_fw_size_16M
16121856 15744k 0xF60000
ralink_default_fw_size_32M
33226752 32448k 0x1FB0000
Out of those, the "16M" value is obviously odd, as it provides more
room for the remaining partitions than the tree others.
Of the devices in all subtargets, there are actually > 50 that have
a firmware partition with 0xFB0000 size, while only 5 (!) have
0xF60000. From the former, many are set to
ralink_default_fw_size_16M anyway, although it is wrong at the
present point.
Consequently, it makes sense to change ralink_default_fw_size_16M
to 0xFB0000, and to update IMAGE_SIZE for the 5 devices with
0xF60000.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Mon, 15 Jul 2019 12:29:53 +0000 (14:29 +0200)]
ramips/rt305x: fix firmware partition size for some 4MB devices
allnet_all0256n-4m, tenda_w150m and unbranded_wr512-3gn-4m have
their firmware partition set to reg = <0x50000 0x3c8000>.
However, based on the 4MB flash, the size should be 0x3b0000.
After some research in the target's history, it looks like the
changed size has been a mistake when transferring device
partitions from Makefile to DTS in
770b28f146f.
This patch changes the named three devices back to 0x3b0000.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Chuanhong Guo [Thu, 25 Jul 2019 11:43:32 +0000 (19:43 +0800)]
ramips: fix mac addresses used by Phicomm K2P
Like most mt7621 boards, Phicomm K2P stores LAN/WAN mac addresses
at 0xe000/0xe006 of factory partition.
Phicomm uses lan_mac-1 as wan_mac, while our default case in 02_network
uses lan_mac+1.
Add a special case reading lan/wan mac address for Phicomm K2P.
Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
Kevin Darbyshire-Bryant [Sat, 11 May 2019 15:17:45 +0000 (16:17 +0100)]
dnsmasq: improve insecure DS warning
Log the failing domain in the insecure DS warning.
Patch has been sent upstream.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Kevin Darbyshire-Bryant [Sat, 9 Mar 2019 08:40:57 +0000 (08:40 +0000)]
dnsmasq: backport latest patches
Backport upstream patches pre 2.81rc for testing purposes.
Let's see what falls out!
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Roger Pueyo Centelles [Wed, 3 Jul 2019 13:39:03 +0000 (15:39 +0200)]
ramips: add kmod-mt7615e to Phicomm K2P images
Now that the mt76 driver supports the MT7615D chip found on these
devices, use it.
Also add the wpad-basic package.
Note: the driver supports operation on both the 2.4 GHz and the
5 GHz bands, but not yet concurrently.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
Kevin Darbyshire-Bryant [Wed, 5 Jun 2019 17:31:47 +0000 (18:31 +0100)]
kernel: netfilter add connmark savedscp support
savedscp is a method of storing the DSCP of an ip packet into conntrack
mark. In combination with a suitable tc filter action (conndscp but may
end up being integrated into connmark) DSCP values are able to be stored
on egress and restored on ingress across links that otherwise alter or
bleach DSCP.
This is useful for qdiscs such as CAKE which are able to shape according
to policies based on DSCP.
Ingress classification is traditionally a challenging task since
iptables rules haven't yet run and tc filter/eBPF programs are pre-NAT
lookups, hence are unable to see internal IPv4 addresses as used on the
typical home masquerading gateway.
The ingress problem is solved by the tc filter, but the tc people didn't
like the idea of tc setting conntrack mark values, though they are ok
with reading conntrack values and hence restoring DSCP from conntrack
marks.
x_tables CONNMARK with the new savedscp action solves the problem of
storing the DSCP to the conntrack mark.
It accepts 2 parameters. The mark is a 32bit value with usually one 1
bit set. This bit is set when savedscp saves the DSCP to the mark.
This is useful to implement a 'one shot'
iptables based classification where the 'complicated' iptables rules are
only run once to classify the connection on initial (egress) packet and
subsequent packets are all marked/restored with the same DSCP. A mark
of zero disables the setting of a status bit/s.
The mask is a 32bit value of at least 6 contiguous bits and represents
the area where the DSCP will be stored.
e.g.
iptables -A QOS_MARK_eth0 -t mangle -j CONNMARK --savedscp-mark 0xfc000000/0x01000000
Would store the DSCP in the top 6 bits of the 32bit mark field, and use
the LSB of the top byte as the 'DSCP has been stored' marker.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Kevin Darbyshire-Bryant [Wed, 5 Jun 2019 17:31:04 +0000 (18:31 +0100)]
iptables: add connmark savedscp support
iptables: connmark - add savedscp option
Naive user space front end to xt_connmark 'savedscp' option.
e.g.
iptables -A QOS_MARK_eth0 -t mangle -j CONNMARK --savedscp-mark 0xfc000000/0x01000000
Will save DSCP into the top 6 bits and OR 0x01 (ie set) the least
significant bit of most significant byte.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Petr Štetiar [Thu, 25 Jul 2019 07:45:03 +0000 (09:45 +0200)]
Revert "build: allow simple build system customization with local.mk"
This reverts commit
fe928c7a81810fd84210a5e9594b7fa8ce1064ce as it seems
to introduce build breakage when local.mk doesn't exist.
make --trace
toplevel.mk:216: target 'local.mk' does not exist
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Tomislav Požega [Thu, 18 Jul 2019 19:37:39 +0000 (21:37 +0200)]
ar71xx: fix WLAN LED names for Archer C7
Update WLAN LED colour identifier for both interfaces on Archer C7
Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
Tomislav Požega [Thu, 18 Jul 2019 15:59:37 +0000 (17:59 +0200)]
ar71xx: fix system LED names on Archer C5/C7
Move system LED board definitions of Archer C5/C7 to reflect
actual system LED colour used
Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
Tomislav Požega [Thu, 18 Jul 2019 14:55:58 +0000 (14:55 +0000)]
ar71xx: Archer C7 v1 LED names and RFKILL fixes
All leds on these boards are green. v1 has RFKILL GPIO 23 for production
units (it had GPIO 13 only for test phase units, and these are rather
very rare to find). As for the previous attempt to fix this and revert
due to WDR boards have blue leds, it was wrong: WDR board does not use
common setup (false).
Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
Tomislav Požega [Fri, 19 Jul 2019 04:04:54 +0000 (06:04 +0200)]
ar71xx: update qca-usb-quirks patch
Base address for USB0 has changed from 0x18116c94 on AR934X
to 0x18116d94 on QCA9558. CP Typo remained for years here...
Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
Petr Štetiar [Wed, 24 Jul 2019 14:00:39 +0000 (14:00 +0000)]
tfa-layerscape: fix fiptool host build
fiptool is a host tool, used in a firmware generation pipeline, but it's
not treated as such, leading to the build breakage on the hosts which
don't have {Open,Libre}SSL dev package installed:
In file included from fiptool.h:16:0,
from fiptool.c:19:
fiptool_platform.h:18:27: fatal error: openssl/sha.h:
No such file or directory
# include <openssl/sha.h>
So this patch promotes fiptool into the host tool with proper host
include and library paths under STAGING_DIR.
Ref: https://github.com/openwrt/openwrt/pull/2267
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Mon, 7 Jan 2019 00:57:01 +0000 (01:57 +0100)]
build: allow simple build system customization with local.mk
I tend to automate most of the boring and repetitive tasks like firmware
flashing, build config reconfiguration etc., so I always end up adding
`include local.mk` as a last line in my Makefile, where local.mk is
usually symlink to some other place, just to not accidentally delete it
during `git clean`.
Carrying this single uncommited modification along in the development
process is quite PITA, because it's causing problems during Git
workflow, while rebasing etc.
I hope, that I'm not alone using similar workflow, so I believe, that
this modification might be useful for others as well.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Adrian Schmutzler [Wed, 24 Jul 2019 15:05:02 +0000 (17:05 +0200)]
ath79: fix indent in 01_leds
Change capitalization from spaces to tabs in order to match
the style of the file.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
[fix capitalization in commit title, add short description]
Signed-off-by: David Bauer <mail@david-bauer.net>
Petr Štetiar [Mon, 22 Jul 2019 20:38:53 +0000 (22:38 +0200)]
mt76: fix kernel Oops by updating to the latest version
75656a4590a3 net: wireless: support of_get_mac_address new ERR_PTR error
Ref: https://github.com/openwrt/mt76/issues/299
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Jackson Lim [Sat, 20 Jul 2019 07:37:12 +0000 (15:37 +0800)]
ath79: add support for D-Link DIR-842 C2
Hardware spec of DIR-842 C2:
SoC: QCA9563
DRAM: 128MB DDR2
Flash: 16MB SPI-NOR
Switch: QCA8337N
WiFi 5.8GHz: QCA9888
WiFi 2.4Ghz: QCA9563
USB: 2.0
Flash instructions:
1. Upgrade the factory.bin through the factory web interface or
the u-boot failsafe interface.
The firmware will boot up correctly for the first time.
Do not power off the device after OpenWrt has booted.
Otherwise the u-boot will enter failsafe mode as the checksum
of the firmware has been changed.
2. Upgrade the sysupgrade.bin in OpenWrt.
After upgrading completes the u-boot won't complain about the
firmware checksum and it's OK to use now.
3. If you powered off the device before upgrading the sysupgrade.bin,
just upgrade the factory.bin through the u-boot failsafe interface
and then goto step 2.
Signed-off-by: Jackson Lim <jackcolentern@gmail.com>
[Reword reset-hog comment, fix formatting]
Signed-off-by: David Bauer <mail@david-bauer.net>
Hans Dedecker [Tue, 23 Jul 2019 12:47:56 +0000 (14:47 +0200)]
tools: libressl: fix compilation for non-glibc clib (FS#2400)
Fixes compilaton issue for non glibc clibs :
libtool: compile: gcc -DPACKAGE_NAME=\"libressl\" -DPACKAGE_TARNAME=\"libressl\" -DPACKAGE_VERSION=\"2.9.2\" "-DPACKAGE_STRING=\"libressl 2.9.2\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libressl\" -DVERSION=\"2.9.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_SYMLINK=1 -DHAVE_ERR_H=1 -DHAVE_ASPRINTF=1 -DHAVE_MEMMEM=1 -DHAVE_STRLCAT=1 -DHAVE_STRLCPY=1 -DHAVE_STRNDUP=1 -DHAVE_STRNLEN=1 -DHAVE_STRSEP=1 -DHAVE_TIMEGM=1 -DHAVE_SYSLOG=1 -DHAVE_ACCEPT4=1 -DHAVE_PIPE2=1 -DHAVE_POLL=1 -DHAVE_SOCKETPAIR=1 -DHAVE_EXPLICIT_BZERO=1 -DHAVE_GETAUXVAL=1 -DHAVE_GETAUXVAL=1 -DHAVE_DL_ITERATE_PHDR=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_VA_COPY=1 -DHAS_GNU_WARNING_LONG=1 -DSIZEOF_TIME_T=8 -I. -I../include -I../include/compat -DLIBRESSL_INTERNAL -D__BEGIN_HIDDEN_DECLS= -D__END_HIDDEN_DECLS= -I../crypto/asn1 -I../crypto/bn -I../crypto/ec -I../crypto/ecdsa -I../crypto/evp -I../crypto/modes -I../crypto -I/builds/pantacor/pv-platforms/openwrt-base/openwrt/staging_dir/host/include -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE -D_GNU_SOURCE -D__STRICT_ALIGNMENT -O2 -I/builds/pantacor/pv-platforms/openwrt-base/openwrt/staging_dir/host/include -fpic -Wall -std=gnu99 -fno-strict-aliasing -fno-strict-overflow -D_FORTIFY_SOURCE=2 -fstack-protector-strong -DHAVE_GNU_STACK -Wno-pointer-sign -MT compat/getprogname_linux.lo -MD -MP -MF compat/.deps/getprogname_linux.Tpo -c compat/getprogname_linux.c -o compat/getprogname_linux.o
compat/getprogname_linux.c: In function 'getprogname':
compat/getprogname_linux.c:32:2: error: #error "Cannot emulate getprogname"
#error "Cannot emulate getprogname"
^~~~~
Reported-by: Anibal Portero <anibal.portero@pantacor.com>
Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
DENG Qingfang [Mon, 22 Jul 2019 17:05:20 +0000 (01:05 +0800)]
ramips: enable Newifi D1 SD slot
Newifi D1 is shipped with an 8GB microSD card in its SD slot
Without SD driver users would not be able to use it unless manually installed
Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
Hans Dedecker [Mon, 22 Jul 2019 19:46:31 +0000 (21:46 +0200)]
netifd: update to latest git HEAD
899f168 system-linux: Coverity fixes
Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
Kevin Darbyshire-Bryant [Mon, 22 Jul 2019 13:38:54 +0000 (14:38 +0100)]
tools: libressl: fix build on MacOS
Making all in tests
depbase=`echo handshake_table.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DPACKAGE_NAME=\"libressl\" -DPACKAGE_TARNAME=\"libressl\" -DPACKAGE_VERSION=\"2.9.2\" -DPACKAGE_STRING=\"libressl\ 2.9.2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libressl\" -DVERSION=\"2.9.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_SYMLINK=1 -DHAVE_ERR_H=1 -DHAVE_READPASSPHRASE_H=1 -DHAVE_ASPRINTF=1 -DHAVE_MEMMEM=1 -DHAVE_READPASSPHRASE=1 -DHAVE_STRLCAT=1 -DHAVE_STRLCPY=1 -DHAVE_STRNDUP=1 -DHAVE_STRNLEN=1 -DHAVE_STRSEP=1 -DHAVE_TIMEGM=1 -DHAVE_GETPROGNAME=1 -DHAVE_SYSLOG=1 -DHAVE_POLL=1 -DHAVE_SOCKETPAIR=1 -DHAVE_ARC4RANDOM=1 -DHAVE_ARC4RANDOM_BUF=1 -DHAVE_ARC4RANDOM_UNIFORM=1 -DHAVE_TIMINGSAFE_BCMP=1 -DHAVE_CLOCK_GETTIME=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DSIZEOF_TIME_T=8 -I. -I../include -I../include/compat -DLIBRESSL_INTERNAL -D__BEGIN_HIDDEN_DECLS= -D__END_HIDDEN_DECLS= -I ../crypto/modes -I ../crypto/asn1 -I ../ssl -I ../tls -I ../apps/openssl -I ../apps/openssl/compat -D_PATH_SSL_CA_FILE=\"../apps/openssl/cert.pem\" -I/Users/kevin/wrt/staging_dir/host/include -D__STRICT_ALIGNMENT -O2 -I/Users/kevin/wrt/staging_dir/host/include -fpic -Wall -std=gnu99 -fno-strict-aliasing -fno-strict-overflow -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Qunused-arguments -Wno-pointer-sign -MT handshake_table.o -MD -MP -MF $depbase.Tpo -c -o handshake_table.o handshake_table.c &&\
mv -f $depbase.Tpo $depbase.Po
make[4]: *** No rule to make target `/Users/kevin/wrt/build_dir/host/libressl-2.9.2/crypto/.libs/libcrypto_la-cpuid-macosx-x86_64.o', needed by `handshake_table'. Stop.
make[3]: *** [all-recursive] Error 1
A similar error & clues from
https://gitlab.com/ymorin/buildroot/commit/
e783d60473944f8b39f1def45d8d6b483a062158
"
LibreSSL 2.9.1 now has a test that requires libtls.a, however, when building a
shared library only build, the --disable-static flag is passed to libressl,
which prevents the building of libtls.a.
With libtls.a not being built, the following error occurs:
libressl-2.9.1/tls/.libs/libtls.a', needed by 'handshake_table'. Stop.
There are three options to fix this:
1) Stick with autotools, and provide a patch that removes building anything in
the tests folder.
2) Pass --enable-static to LIBRESSL_CONF_OPTS
3) Change the package type to cmake, as a cmake build does not have this issue."
It appears we cannot change to cmake because cmake has a dependency on
an ssl library.
Take option 1 and do not build the tests.
Also take the opportunity to remove man page building as well.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Rafał Miłecki [Wed, 17 Jul 2019 09:32:55 +0000 (11:32 +0200)]
base-files: drop support for the platform_nand_pre_upgrade()
No target uses it anymore. All code from that callback was moved into
the platform_do_upgrade().
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Rafał Miłecki [Wed, 17 Jul 2019 09:32:54 +0000 (11:32 +0200)]
treewide: sysupgrade: get rid of platform_nand_pre_upgrade()
1) nand_do_upgrade() is always called by a target code
2) nand_do_upgrade() starts with calling platform_nand_pre_upgrade()
It means there is no need for the platform_nand_pre_upgrade() callback
at all. All code that was present there could bo moved & simplly called
by a target right before the nand_do_upgrade().
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Rafał Miłecki [Wed, 17 Jul 2019 06:02:05 +0000 (08:02 +0200)]
layerscape: sysupgrade: get rid of platform_pre_upgrade()
1) RAMFS_COPY_BIN and RAMFS_COPY_DATA can be defined at top of the file
like it's done for all other targets.
2) fw_printenv.lock can be created one step later in the
platform_do_upgrade(). It seems to be working well on many other
targets.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Hans Dedecker [Sun, 21 Jul 2019 21:25:15 +0000 (23:25 +0200)]
curl: update to 7.65.3
For changes in 7.65.3; see https://curl.haxx.se/changes.html#7_65_3
Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
Rafał Miłecki [Sun, 21 Jul 2019 09:23:32 +0000 (11:23 +0200)]
mac80211: brcm: backport first set of 5.4 brcmfmac changes
This doesn't include
9ff8614a3dbe ("brcmfmac: use separate Kconfig file
for brcmfmac") due to a few conflicts with backports changes.
An important change is:
[PATCH 2/7] brcmfmac: change the order of things in brcmf_detach()
which fixes a rmmod crash in the brcmf_txfinalize().
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Roman Yeryomin [Thu, 18 Jul 2019 16:35:50 +0000 (19:35 +0300)]
tools: libressl: update to 2.9.2 version
To keep in sync with OpenSSL 1.1.x branch version options.
Signed-off-by: Roman Yeryomin <roman@advem.lv>
Petr Štetiar [Fri, 19 Jul 2019 21:04:23 +0000 (23:04 +0200)]
firmware-utils: mkfwimage: fix build failure on macOS with gcc 9
Fixes following errors:
src/mkfwimage.c:279:8: error: format specifies type 'long' but the argument has type 'off_t' (aka 'long long') [-Werror,-Wformat]
d->stats.st_size,
^~~~~~~~~~~~~~~~
src/mkfwimage.c:280:8: error: format specifies type 'long' but the argument has type 'long long' [-Werror,-Wformat]
d->partition_length - d->stats.st_size);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/mkfwimage.c:378:6: error: format specifies type 'unsigned long' but the argument has type 'long long' [-Werror,-Wformat]
d->stats.st_size - d->partition_length);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Reported-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Fri, 19 Jul 2019 19:34:16 +0000 (21:34 +0200)]
firmware-utils: mkfwimage: fix more errors reported by gcc-6/7/9
src/mkfwimage.c:276:8: error: format '%lld' expects argument of type 'long long int', but argument 4 has type '__off_t' {aka 'const long int'} [-Werror=format=]
src/fw.h:71:36: error: format '%llu' expects argument of type 'long long unsigned int', but argument 6 has type '__off_t' {aka 'long int'} [-Werror=format=]
inlined from 'main' at src/mkfwimage.c:543:12:
/string_fortified.h:106:10: error: '__builtin_strncpy' output truncated before terminating nul copying 4 bytes from a string of the same length [-Werror=stringop-truncation]
inlined from 'write_part' at src/mkfwimage.c:235:2,
string_fortified.h:106:10: error: '__builtin_strncpy' specified bound 16 equals destination size [-Werror=stringop-truncation]
inlined from 'main' at src/mkfwimage.c:477:5:
string_fortified.h:106:10: error: '__builtin_strncpy' specified bound 256 equals destination size [-Werror=stringop-truncation]
inlined from 'main' at src/mkfwimage.c:496:5:
string_fortified.h:106:10: error: '__builtin_strncpy' specified bound 4096 equals destination size [-Werror=stringop-truncation]
inlined from 'main' at src/mkfwimage.c:481:5:
string_fortified.h:106:10: error: '__builtin_strncpy' specified bound 4096 equals destination size [-Werror=stringop-truncation]
inlined from 'main' at src/mkfwimage.c:485:5:
string_fortified.h:106:10: error: '__builtin_strncpy' specified bound 16 equals destination size [-Werror=stringop-truncation]
Runtested on ath79 and UBNT Bullet M XW.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Kevin Darbyshire-Bryant [Fri, 19 Jul 2019 15:54:17 +0000 (16:54 +0100)]
firmware-utils: mkfwimage: fix more errors
Fix 4 errors reported by gcc 9
3 mismatched format type errors
1 unused variable error
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Petr Štetiar [Fri, 19 Jul 2019 13:52:46 +0000 (15:52 +0200)]
firmware-utils: mkfwimage: provide human readable error
While looking at the ath25 build breakage of 19.07 images today I've
encountered following error:
mkfwimage -B XS5 -v [...] ath25-ubnt5-squashfs-sysupgrade.bin.new
ERROR: Failed creating firmware layout description - error code: -2
Which is barely human readable and needs poking into the source code, so
this patch makes the error more verbose and usable by mere mortals.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Fri, 19 Jul 2019 14:10:35 +0000 (16:10 +0200)]
firmware-utils: mkfwimage: enable extra compiler checks and fix them
Let's enforce additional automatic checks enforced by the compiler in
order to catch possible errors during compilation.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Hauke Mehrtens [Sun, 7 Jul 2019 17:07:40 +0000 (19:07 +0200)]
ath10k-ct: Revert back to version 4.19
Version 5.2 shows a error when registering the devive for me.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Hauke Mehrtens [Sun, 7 Jul 2019 11:48:20 +0000 (13:48 +0200)]
ath10k-ct: switch to version 5.2
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Hauke Mehrtens [Sun, 7 Jul 2019 11:38:37 +0000 (13:38 +0200)]
ath10k-ct: remove patches for old versions
the ath10k-ct package ships multiple versions of the ath10k-ct driver,
OpenWrt currently only uses the version 4.19, but we still ship some
patches for older versions. Remove all patches only touching older
versions and also remove the patch for older versions from patches which
do the same changes to multiple versions of ath10k-ct.
This removes some unneeded patches, the end binary should stay the same.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Hauke Mehrtens [Sun, 7 Jul 2019 11:30:03 +0000 (13:30 +0200)]
ath10k-ct: update to version 2019-06-13
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Hauke Mehrtens [Sat, 6 Jul 2019 22:08:20 +0000 (00:08 +0200)]
mac80211: Update to version 5.2-rc7
This updates mac80211 to version 5.2-rc7, this contains all the changes
to the wireless subsystem up to Linux 5.2-rc7.
* The removed patches are applied upstream
* b43 now uses kmod-lib-cordic
* Update the nl80211.h file in iw to match backports version.
* Remove the two backports from kernel 4.9, they were needed for mt76,
but that can use the version from backports now, otherwise they
collide and cause compile errors.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
INAGAKI Hiroshi [Sun, 16 Jun 2019 16:23:32 +0000 (01:23 +0900)]
ath79: modify device name of I-O DATA WN-AC1600DGR2
The hardware of I-O DATA WN-AC1600DGR3 has completely compatibility
with WN-AC1600DGR2, so modify the device name of WN-AC1600DGR2 to show
the images for DGR2 also support DGR3.
Specification of WN-AC1600DGR3:
- SoC : Qualcomm Atheros QCA9557
- RAM : DDR2 128 MiB
- Flash : SPI-NOR 16 MiB
- WLAN : 2.4/5 GHz
- 2.4 GHz : QCA9557 (SoC), 2T2R
- 5 Ghz : QCA9880, 3T3R
- Ethernet : 5x 10/100/1000 Mbps
- Switch : QCA8337N
- LEDs/Input : 6x/6x (4x buttons, 1x slide-switch)
- UART : through-hole on PCB
- J1: Vcc, GND, TX, RX from ethernet port side
- 115200n8
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
Adrian Schmutzler [Sun, 5 May 2019 16:46:09 +0000 (18:46 +0200)]
ath79: Add support for TP-Link Archer C60 v2
TP-Link Archer C60 v2 is a dual-band AC1350 router,
based on Qualcomm/Atheros QCA9561 + QCA9886.
Specification:
- 775/650/258 MHz (CPU/DDR/AHB)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH (SPI NOR)
- 3T3R 2.4 GHz
- 2T2R 5 GHz
- 5x 10/100 Mbps Ethernet
- 7x LED, 2x button
- UART header on PCB
Flash instruction (WebUI):
Download *-factory.bin image and upload it via the firmwary upgrade
function of the stock firmware WebUI.
Flash instruction (TFTP):
1. Set PC to fixed IP address 192.168.0.66
2. Download *-factory.bin image and rename it to tp_recovery.bin
3. Start a tftp server with the file tp_recovery.bin in its root
directory
4. Turn off the router
5. Press and hold reset button
6. Turn on router with the reset button pressed and wait ~15 seconds
7. Release the reset button and after a short time the firmware should
be transferred from the tftp server
8. Wait ~30 second to complete recovery
Flash instruction (under U-Boot, using UART):
tftp 0x81000000 ...-sysupgrade.bin
erase 0x9f030000 +$filesize
cp.b $fileaddr 0x9f030000 $filesize
reset
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler [Sun, 5 May 2019 16:36:43 +0000 (18:36 +0200)]
ath79: Add support for TP-Link Archer C60 v1
TP-Link Archer C60v1 is a dual-band AC1350 router,
based on Qualcomm/Atheros QCA9561+QCA9886.
Specification:
- 775/650/258 MHz (CPU/DDR/AHB)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH (SPI NOR)
- 3T3R 2.4 GHz
- 2T2R 5 GHz
- 5x 10/100 Mbps Ethernet
- 7x LED, 2x button
- UART header on PCB
Flash instruction (WebUI):
Download *-factory.bin image and upload it via the firmwary upgrade
function of the stock firmware WebUI.
Flash instruction (TFTP):
1. Set PC to fixed ip address 192.168.0.66
2. Download *-factory.bin image and rename it to tp_recovery.bin
3. Start a tftp server with the file tp_recovery.bin in its root directory
4. Turn off the router
5. Press and hold Reset button
6. Turn on router with the reset button pressed and wait ~15 seconds
7. Release the reset button and after a short time
the firmware should be transferred from the tftp server
8. Wait ~30 second to complete recovery.
Flash instruction under U-Boot, using UART:
1. tftp 0x81000000 ...-sysupgrade.bin
2. erase 0x9f020000 +$filesize
3. cp.b $fileaddr 0x9f020000 $filesize
4. reset
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Andrew Cameron [Wed, 26 Jun 2019 21:40:54 +0000 (16:40 -0500)]
ath79: add support for TP-Link CPE510-v2/v3
TP-Link CPE510-v2/v3 is an outdoor wireless CPE for 5 GHz with
one Ethernet port based on Atheros AR9344
Specifications:
- Based on the same underlying hardware as the TP-Link CPE510
- Power, LAN, and 4 green LEDs
- 1 10/100Mbps Shielded Ethernet Port (Passive PoE in)
- Built-in 13dBi 2x2 dual-polarized directional MIMO antenna
- Adjustable transmission power from 0 to 23dBm/200mw
Flashing instructions:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Signed-off-by: Andrew Cameron <apcameron@softhome.net>
[whitespace fixes]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Pramod Pancha [Fri, 5 Jul 2019 17:45:19 +0000 (13:45 -0400)]
ath79: add support for Trendnet TEW-823DRU
Trendnet TEW-823DRU is a dual-band AC1750 router.
The router is based on Qualcomm/Atheros QCA9558 + QCA9880.
Specification:
720 MHz CPU
256 MB of RAM
16 MB of FLASH
3T3R 2.4 GHz
3T3R 5 GHz
5x 10/100/1000 Mbps Ethernet
Firmware can be flashed from the web interface. Tested on 3 routers
with no issues.
Signed-off-by: Pramod Pancha <pancha@vill.com>
[whitespace fixes]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Christoph Krapp [Tue, 16 Jul 2019 18:47:49 +0000 (20:47 +0200)]
ath79: add support for TP-Link RE355 v1 and RE450 v1
Specification:
SoC: Qualcomm Atheros QCA9558
RAM: 64/128MiB
Flash: 8MiB SPI-NOR
Wifi:
- 2.4GHz: 3T3R (QCA9558)
- 5GHz: 3T3R (QCA9880)
LAN: 1x 10/100/1000 Mbps
UART:
- TP1: Tx
- TP2: Rx
- TP3: Gnd
- TP4: 3v3
Flash instructions:
Flash factory image through stock firmware WEB UI.
Signed-off-by: Christoph Krapp <achterin@googlemail.com>
Georgi Vlaev [Wed, 17 Apr 2019 18:17:45 +0000 (21:17 +0300)]
ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
Petr Štetiar [Wed, 17 Jul 2019 21:04:22 +0000 (23:04 +0200)]
mtd: cleanup unused code and variables in fis.c
While compile checking mtd changes in PR#1359 I've noticed following
compiler warnings and cleaned them up:
fis.c: In function 'fis_remap':
fis.c:143:25: warning: variable 'redboot' set but not used [-Wunused-but-set-variable]
struct fis_image_desc *redboot = NULL;
^~~~~~~
fis.c:142:25: warning: variable 'fisdir' set but not used [-Wunused-but-set-variable]
struct fis_image_desc *fisdir = NULL;
^~~~~~
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Daniel Gimpelevich [Sat, 1 Sep 2018 02:28:35 +0000 (19:28 -0700)]
ath79: add support for Bluesocket BSAP1880 board
This board was used in dual-band 802.11n enterprise access points, models
BSAP-1800v2 and BSAP-1840, introduced in 2010 by Bluesocket, which was
acquired by Adtran in 2011, who has now EOL'ed them. They differed only in
that the BSAP-1840's antennae were detachable, while the BSAP-1800v2's were
inside the case. They have an external RJ-45 console port, which works with
standard Cisco 72-3383-01 console cables.
Specification:
- System-On-Chip: AR7161
- CPU/Speed: 600 MHz
- Flash-Chip: Macronix MX25L12845E
- Flash size: 16 MiB
- RAM: 64 MiB
- Wireless No1: Lite-On WN2601A card: AR9160/AR9103 2.4GHz 802.11bgn
- Wireless No2: Lite-On WN2502A card: AR9160/AR9106 5GHz 802.11an
- PHY: Vitesse VSC8601, Rev. B
Installation:
1. Connect to the serial console using a terminal that supports YMODEM at
115200 bps, 8 data bits, no parity, 1 stop bit
2. Interrupt the bootloader using its password, which is: r00t
3. Issue the "fis init" command, confirming if prompted
4. Look at the length of the openwrt-ath79-generic-*-squashfs-kernel.bin
file, and substitute it below, instead of where I have "LeNgTh"
5. Issue the following command, and upload this file using YMODEM protocol
load -r -v -b 0x80060000 -m ymodem
6. Issue the following commands, substituting as mentioned above:
fis create -b 0x80060000 -l LeNgTh vmlinux_2
load -r -v -b 0x80100000 -m ymodem
7. Using YMODEM, upload openwrt-ath79-generic-*-squashfs-rootfs.bin
8. Issue the "fis free" command, and for the first range in its response,
use a hexadecimal calculator to subtract the start from the end in order
to substitute it below, with the leading "0x" to specify it in
hexadecimal, instead of where I have "LeNgTh"
9. Issue the following commands, substituting as mentioned above:
fis create -b 0x80100000 -l LeNgTh -e 0 -r 0 rootfs
reset
10.Wait for the status LED to go solid green
Tested-by: Brian Gonyer <bgonyer@gmail.com>
Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
[fixed obsolete $ARGV in platform_do_upgrade]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Daniel Gimpelevich [Wed, 26 Jun 2019 19:56:47 +0000 (12:56 -0700)]
ath79: widen RedBoot directory search and add PHY
The Bluesocket BSAP1880 board has a Vitesse PHY, for which the driver was
not being included, and its RedBoot directory block is earlier in the
flash than the search was allowing. This commit prepares for supporting it.
Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Daniel Gimpelevich [Wed, 26 Jun 2019 19:39:37 +0000 (12:39 -0700)]
ath79: support "rgmii-id" PHY mode in ag71xx
The ag71xx code did not include a case for the "rgmii-id" PHY mode in the
code. There are devices that need this mode, so I'm adding it.
Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Daniel Gimpelevich [Sat, 1 Sep 2018 01:14:24 +0000 (18:14 -0700)]
mtd: add CRC signature to RedBoot partition map
The code for calculating the CRC32 signatures for RedBoot FIS partitions
was already included, but for unknown reasons, it was never invoked. Some
bootloaders enforce checking these for loaded kernels, so they should be
written. This patch does so.
Tested-by: Brian Gonyer <bgonyer@gmail.com>
Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Martin Schiller [Tue, 28 May 2019 10:50:15 +0000 (12:50 +0200)]
openvpn: add new list option tls_ciphersuites
To configure the list of allowable TLS 1.3 ciphersuites, the option
tls_ciphersuites is used instead of tls_ciphers.
Signed-off-by: Martin Schiller <ms@dev.tdt.de>
Zachary Cook [Thu, 11 Jul 2019 20:09:15 +0000 (16:09 -0400)]
brcm47xx: fix 831-old_gpio_wdt.patch for linux 4.19
Fix the following compilation error when using linux 4.19 on brcm47xx:
drivers/watchdog/old_gpio_wdt.c:236:2: error: implicit declaration of function 'setup_timer'
setup_timer was removed and replaced by timer_setup in linux >=4.15:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=
513ae785
Update the patch to use the timer_setup interface
Signed-off-by: Zachary Cook <zachcook1991@gmail.com>
Petr Štetiar [Wed, 17 Jul 2019 13:19:54 +0000 (15:19 +0200)]
ath79: ar9330: add missing watchdog node
It was reported in FS#2385, that Carambola2 doesn't currently have
working watchdog so fix it by adding watchdog node.
Ref: FS#2385
Signed-off-by: Petr Štetiar <ynezz@true.cz>
INAGAKI Hiroshi [Thu, 27 Jun 2019 03:27:27 +0000 (12:27 +0900)]
ramips: add MT7615 wireless support for ELECOM WRC-1167GHBK2-S
ELECOM WRC-1167GHBK2-S has a MediaTek MT7615D chip for 2.4/5 GHz
wireless.
A driver package for MT7615 chip is added to OpenWrt in
a0e5ca4f3523b9eef96bff32e45f6fa8275b982f,
so add preliminary MT7615 chip support for WRC-1167GHBK2-S.
Note: Currently, DBDC mode for MT7615 is not supported in mt76 driver.
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
Petr Štetiar [Tue, 16 Jul 2019 19:43:08 +0000 (21:43 +0200)]
perf: simplify the build process
Redirect the build output to PKG_BUILD_DIR instead of copying over
complete source code.
Build tested on following targets:
x86/64 ar7/generic ipq40xx/generic imx6/generic ar71xx/generic
ramips/mt7621 ramips/mt7620 sunxi/cortexa7
Run tested on imx6/apalis.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Tue, 16 Jul 2019 19:46:49 +0000 (21:46 +0200)]
kernel: generic: fix perf build breakage on 4.19
Drop 211-host_tools_portability.patch which is breaking perf build on
4.19 kernels by removing the include directory from the host's CFLAGS
leading to the following build breakage:
pmu-events/jevents.c:48:10: fatal error: linux/list.h: No such file or directory
#include <linux/list.h>
^~~~~~~~~~~~~~
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Tue, 16 Jul 2019 20:06:40 +0000 (22:06 +0200)]
imx6: apalis: add missing jffs2reset to ramfs during sysupgrade
jffs2reset is used to cleanup the rootfs_data overlay, but it's
currently missing in the ramfs during sysupgrade leading to the
following error:
Switching to ramdisk...
Performing system upgrade...
/lib/upgrade/do_stage2: line 27: jffs2reset: not found
Fixes: 2f1a11d0089c ("imx6: apalis: fix config survival after sysupgrade -n")
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Petr Štetiar [Tue, 16 Jul 2019 08:23:18 +0000 (10:23 +0200)]
imx6: apalis: fix sysupgrade paths
We can't use $board_name in sysupgrade paths for kernel and rootfs as we
currently generate one image which could be used on two different base
boards.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Alberto Bursi [Sun, 14 Jul 2019 01:11:00 +0000 (03:11 +0200)]
x86: add modern network modules to Generic target
Many Atom-based embedded/industrial x86 boards can't run 64bit operating
systems due to either processor or board firmware limitations, but they
have modern interfaces (PCIe) or have modern Intel gigabit controllers
onboard. With the current default package selection for x86 Generic
target their network won't work.
Add the modern gigabit network modules needed or most likely going to be
used as add-in cards, similar to what is the list on x86_64 target.
Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
[fixed whitespace issue]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Felix Fietkau [Wed, 17 Jul 2019 07:36:33 +0000 (09:36 +0200)]
mt76: update to the latest version
3d7f738 mt76: mt7615: add missing register initialization
Signed-off-by: Felix Fietkau <nbd@nbd.name>
Felix Fietkau [Wed, 19 Jun 2019 10:32:20 +0000 (12:32 +0200)]
mac80211: add config tweak for tx bursting when using VHT
By default, set BE tx queue TXOP limit to 1.0 in the hostapd config
Many vendor drivers are doing similar things to boost throughput.
On MT7612 under ideal conditions, it improves tx throughput from 470 Mbit/s
to about 570 Mbit/s.
Signed-off-by: Felix Fietkau <nbd@nbd.name>
Rafał Miłecki [Sun, 14 Jul 2019 17:00:00 +0000 (19:00 +0200)]
base-files: don't set ARGV and ARGC
Those are not used by any image check function anymore.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Rafał Miłecki [Sun, 14 Jul 2019 16:59:59 +0000 (18:59 +0200)]
mvebu: sysupgrade: don't use $ARGV in platform_check_image()
sysupgrade passes image path to platform_check_image() as an argument so
it can be simply accessed using $1
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Rafał Miłecki [Sun, 14 Jul 2019 17:03:19 +0000 (19:03 +0200)]
treewide: sysupgrade: don't use $ARGV in platform_do_upgrade()
stage2 passes image path to platform_do_upgrade() as an argument so it
can be simply accessed using $1
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Rafał Miłecki [Fri, 12 Jul 2019 12:05:49 +0000 (14:05 +0200)]
ramips: get rid of platform_pre_upgrade()
The only step between platform_pre_upgrade() and platform_do_upgrade()
is switching to ramdisk. It should be fine to "mtd erase firmware" from
the later callback and get rid of the first one.
This change wasn't tested on affected target but identical code logic
was verified to work as expected on brcm47xx with initramfs firmware.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Rafał Miłecki [Fri, 12 Jul 2019 12:05:47 +0000 (14:05 +0200)]
ar71xx: get rid of platform_pre_upgrade()
The only step between platform_pre_upgrade() and platform_do_upgrade()
is switching to ramdisk. It should be fine to "mtd erase firmware" from
the later callback and get rid of the first one.
This change wasn't tested on affected target but identical code logic
was verified to work as expected on brcm47xx with initramfs firmware.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Etienne Champetier [Sun, 14 Jul 2019 02:43:28 +0000 (19:43 -0700)]
ar71xx: enable SGMII fixup on Mikrotik wAP AC
fixes intermittent loss of connectivity on 1Gbit port, with log message:
> 803x_aneg_done: SGMII link is not ok
Thanks to David Bauer for pointing me in the right direction.
I just had to figure out the right bus_id, which you find in this log:
> ag71xx ag71xx.1: connected to PHY at gpio-1:00 [uid=
004dd074,
driver=Atheros 8031 ethernet]
Fixes FS#2236
Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com>
[Wrapped commit message - Fixed whitespace erors]
Signed-off-by: David Bauer <mail@david-bauer.net>
Chuanhong Guo [Tue, 16 Jul 2019 11:38:27 +0000 (19:38 +0800)]
ath79: add seama header fixup for Qihoo C301
This script is copied from ar71xx. Without a header fixup, u-boot
checksum for kernel will fail after the first boot.
Fixes: a9360452f0 ("ath79: add support for Qihoo C301")
Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
Chuanhong Guo [Tue, 16 Jul 2019 11:35:12 +0000 (19:35 +0800)]
package: mtd: add fixseama command for ath79
This is needed by Qihoo C301.
Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
Rafał Miłecki [Sun, 14 Jul 2019 20:11:40 +0000 (22:11 +0200)]
orion: sysupgrade: change platform_check_image() args validation
sysupgrade passes image to check as argument so use $# instead of $ARGC.
It also fits this function better as it checks $1 and not $ARGV.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
projects / openwrt / staging / hauke.git / log