[OpenWrt-Devel] [PATCH 2/2] uboot-imx6: Bump to 2019.01
Build tested: apalis, mx6sabresd, nitrogen6dl, nitrogen6dl2g, nitrogen6q,
nitrogen6q2g, nitrogen6s, nitrogen6s1g, wandboard
Run tested: apalis (pending PR #1595)
Cc: Felix Fietkau
Cc: Vladimir Vid
Cc: Koen Vandeputte
Signed-off-by: Petr Štetiar
---
package/boot/uboot-imx6/Makefile | 4 ++--
package/boot/uboot-imx6/patches/100-wandboard-enable-fit.patch | 6 +++---
.../boot/uboot-imx6/patches/110-mx6cuboxi-mmc-fallback.patch | 10 +-
3 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/package/boot/uboot-imx6/Makefile b/package/boot/uboot-imx6/Makefile
index 3eba249..25d68bf 100644
--- a/package/boot/uboot-imx6/Makefile
+++ b/package/boot/uboot-imx6/Makefile
@@ -7,10 +7,10 @@
include $(TOPDIR)/rules.mk
-PKG_VERSION:=2018.03
+PKG_VERSION:=2019.01
PKG_RELEASE:=1
-PKG_HASH:=7e7477534409d5368eb1371ffde6820f0f79780a1a1f676161c48442cb303dfd
+PKG_HASH:=50bd7e5a466ab828914d080d5f6a432345b500e8fba1ad3b7b61e95e60d51c22
include $(INCLUDE_DIR)/u-boot.mk
include $(INCLUDE_DIR)/package.mk
diff --git a/package/boot/uboot-imx6/patches/100-wandboard-enable-fit.patch
b/package/boot/uboot-imx6/patches/100-wandboard-enable-fit.patch
index 6bfcc1f..3ab6152 100644
--- a/package/boot/uboot-imx6/patches/100-wandboard-enable-fit.patch
+++ b/package/boot/uboot-imx6/patches/100-wandboard-enable-fit.patch
@@ -1,6 +1,6 @@
--- a/configs/wandboard_defconfig
+++ b/configs/wandboard_defconfig
-@@ -27,7 +27,7 @@ CONFIG_CMD_I2C=y
+@@ -29,7 +29,7 @@ CONFIG_CMD_I2C=y
CONFIG_CMD_MMC=y
CONFIG_CMD_SATA=y
CONFIG_CMD_USB=y
@@ -8,8 +8,8 @@
+# CONFIG_CMD_CACHE is not set
CONFIG_CMD_EXT4_WRITE=y
CONFIG_ENV_IS_IN_MMC=y
- CONFIG_DM=y
-@@ -39,3 +39,5 @@ CONFIG_USB_STORAGE=y
+ CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG=y
+@@ -43,3 +43,5 @@ CONFIG_USB=y
CONFIG_VIDEO=y
# CONFIG_VIDEO_SW_CURSOR is not set
CONFIG_OF_LIBFDT=y
diff --git a/package/boot/uboot-imx6/patches/110-mx6cuboxi-mmc-fallback.patch
b/package/boot/uboot-imx6/patches/110-mx6cuboxi-mmc-fallback.patch
index 0883eb7..4b34a83 100644
--- a/package/boot/uboot-imx6/patches/110-mx6cuboxi-mmc-fallback.patch
+++ b/package/boot/uboot-imx6/patches/110-mx6cuboxi-mmc-fallback.patch
@@ -1,7 +1,7 @@
--- a/board/solidrun/mx6cuboxi/mx6cuboxi.c
+++ b/board/solidrun/mx6cuboxi/mx6cuboxi.c
-@@ -334,6 +334,12 @@ int board_init(void)
- return ret;
+@@ -290,6 +290,12 @@ static void setup_iomux_enet(void)
+ udelay(100);
}
+void board_boot_order(u32 *spl_boot_list)
@@ -10,12 +10,12 @@
+ spl_boot_list[1] = BOOT_DEVICE_MMC1;
+}
+
- static bool is_hummingboard(void)
+ int board_phy_config(struct phy_device *phydev)
{
- int val1, val2;
+ if (phydev->drv->config)
--- a/arch/arm/mach-imx/spl.c
+++ b/arch/arm/mach-imx/spl.c
-@@ -136,7 +136,7 @@ int g_dnl_bind_fixup(struct usb_device_d
+@@ -167,7 +167,7 @@ int g_dnl_bind_fixup(struct usb_device_d
/* called from spl_mmc to see type of boot mode for storage (RAW or FAT) */
u32 spl_boot_mode(const u32 boot_device)
{
--
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] u-boot.mk: Fix building of recent U-Boot sources
This patch fixes following error with U-Boot 2019.01 on imx6: In file included from tools/lib/crc16.c:1:0: ./tools/../lib/crc16.c: In function 'crc16_ccitt': ./tools/../lib/crc16.c:70:2: error: 'for' loop initial declarations are only allowed in C99 mode for (int i = 0; i < len; i++) ^ ./tools/../lib/crc16.c:70:2: note: use option -std=c99 or -std=gnu99 to compile your code Code was introduced in the upstream v2019.01-rc1-154-g51c2345: commit 51c2345bd24837f9f67f16268da6dc71573f1325 Author: Philipp Tomsich Date: Sun Nov 25 19:22:19 2018 +0100 Roll CRC16-CCITT into the hash infrastructure Upstream has added -std=gnu11 host flag in v2018.07-rc2-1-gfa89399: commit fa893990e9b53425af5f5059e04a2bffde91ccf9 Author: Tom Rini Date: Tue Jun 19 23:53:54 2018 -0400 Makefile: Ensure we build with -std=gnu11 Build tested on imx6: apalis, mx6sabresd, nitrogen6dl, nitrogen6dl2g, nitrogen6q, nitrogen6q2g, nitrogen6s, nitrogen6s1g, wandboard Run tested: apalis (pending PR #1595) Signed-off-by: Petr Štetiar --- include/u-boot.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/u-boot.mk b/include/u-boot.mk index babb764..26e1685 100644 --- a/include/u-boot.mk +++ b/include/u-boot.mk @@ -42,7 +42,7 @@ TARGET_DEP = TARGET_$(BUILD_TARGET)$(if $(BUILD_SUBTARGET),_$(BUILD_SUBTARGET)) UBOOT_MAKE_FLAGS = \ HOSTCC="$(HOSTCC)" \ - HOSTCFLAGS="$(HOST_CFLAGS) $(HOST_CPPFLAGS)" \ + HOSTCFLAGS="$(HOST_CFLAGS) $(HOST_CPPFLAGS) -std=gnu11" \ HOSTLDFLAGS="$(HOST_LDFLAGS)" define Build/U-Boot/Target -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] lantiq: Add support for 2nd USB port on Fritz!Box 7320 and 7330
From: Robert Resch
This patch enables support for 2nd USB port, which is available on
Fritz!Box 7320 and 7330. It was run-tested on 7320 and 7330 as well.
It's just rework of previous Robert's patch email attempt[1], this time
in proper format.
1. http://lists.infradead.org/pipermail/openwrt-devel/2019-January/015461.html
Signed-off-by: Robert Resch
Signed-off-by: Petr Štetiar
---
target/linux/lantiq/files-4.14/arch/mips/boot/dts/FRITZ7320.dts | 8
1 file changed, 8 insertions(+)
diff --git a/target/linux/lantiq/files-4.14/arch/mips/boot/dts/FRITZ7320.dts
b/target/linux/lantiq/files-4.14/arch/mips/boot/dts/FRITZ7320.dts
index 45a59c0..e999b59 100644
--- a/target/linux/lantiq/files-4.14/arch/mips/boot/dts/FRITZ7320.dts
+++ b/target/linux/lantiq/files-4.14/arch/mips/boot/dts/FRITZ7320.dts
@@ -159,6 +159,14 @@
status = "okay";
};
+&usb_phy1 {
+ status = "okay";
+};
+
&usb0 {
status = "okay";
};
+
+&usb1 {
+ status = "okay";
+};
--
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/4 v2] gemini: Add v4.19 kernel patches
This is the remainder of kernel patches for the v4.19
kernel. A whole slew of the previous patch stack is now
upstream, so this mainly contains the stuff that was
added upstream between v4.19 and v5.0-rc1, and then
the USB FOTG201 patches from Hans.
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Resend.
---
...pinctrl-gemini-Mask-and-set-properly.patch | 36 +++
...inctrl-gemini-Fix-up-TVC-clock-group.patch | 146
...nctrl-gemini-Drop-noisy-debug-prints.patch | 87
.../0004-boot-sq201-from-sda1.patch | 25 +++
...hysmap_of-Move-custom-initialization.patch | 52 +
...physmap_of_gemini-Handle-pin-control.patch | 194
...he-D-Link-DIR-685-MTD-partition-info.patch | 71 ++
...8-ARM-dts-Enable-Gemini-flash-access.patch | 169 ++
...rtitions-Add-RedBoot-FIS-DT-bindings.patch | 51 +
...ns-Add-second-compatible-for-redboot.patch | 77 +++
...11-ARM-dts-Fix-up-SQ201-flash-access.patch | 73 ++
...ARM-dts-Blank-D-Link-DIR-685-console.patch | 30 +++
...ost-fotg2-add-silicon-clock-handling.patch | 123 ++
...st-add-DT-bindings-for-faraday-fotg2.patch | 69 ++
...b-host-fotg2-add-device-tree-probing.patch | 48
...t-fotg2-add-Gemini-specific-handling.patch | 138
...t-fotg2-restart-hcd-after-port-reset.patch | 32 +++
...he-FOTG210-USB-host-to-Gemini-boards.patch | 210 ++
18 files changed, 1631 insertions(+)
create mode 100644
target/linux/gemini/patches-4.19/0001-pinctrl-gemini-Mask-and-set-properly.patch
create mode 100644
target/linux/gemini/patches-4.19/0002-pinctrl-gemini-Fix-up-TVC-clock-group.patch
create mode 100644
target/linux/gemini/patches-4.19/0003-pinctrl-gemini-Drop-noisy-debug-prints.patch
create mode 100644
target/linux/gemini/patches-4.19/0004-boot-sq201-from-sda1.patch
create mode 100644
target/linux/gemini/patches-4.19/0005-mtd-physmap_of-Move-custom-initialization.patch
create mode 100644
target/linux/gemini/patches-4.19/0006-mtd-physmap_of_gemini-Handle-pin-control.patch
create mode 100644
target/linux/gemini/patches-4.19/0007-ARM-dts-Fix-up-the-D-Link-DIR-685-MTD-partition-info.patch
create mode 100644
target/linux/gemini/patches-4.19/0008-ARM-dts-Enable-Gemini-flash-access.patch
create mode 100644
target/linux/gemini/patches-4.19/0009-mtd-partitions-Add-RedBoot-FIS-DT-bindings.patch
create mode 100644
target/linux/gemini/patches-4.19/0010-mtd-partitions-Add-second-compatible-for-redboot.patch
create mode 100644
target/linux/gemini/patches-4.19/0011-ARM-dts-Fix-up-SQ201-flash-access.patch
create mode 100644
target/linux/gemini/patches-4.19/0012-ARM-dts-Blank-D-Link-DIR-685-console.patch
create mode 100644
target/linux/gemini/patches-4.19/0013-usb-host-fotg2-add-silicon-clock-handling.patch
create mode 100644
target/linux/gemini/patches-4.19/0014-usb-host-add-DT-bindings-for-faraday-fotg2.patch
create mode 100644
target/linux/gemini/patches-4.19/0015-usb-host-fotg2-add-device-tree-probing.patch
create mode 100644
target/linux/gemini/patches-4.19/0016-usb-host-fotg2-add-Gemini-specific-handling.patch
create mode 100644
target/linux/gemini/patches-4.19/0017-usb-host-fotg2-restart-hcd-after-port-reset.patch
create mode 100644
target/linux/gemini/patches-4.19/0018-ARM-dts-Add-the-FOTG210-USB-host-to-Gemini-boards.patch
diff --git
a/target/linux/gemini/patches-4.19/0001-pinctrl-gemini-Mask-and-set-properly.patch
b/target/linux/gemini/patches-4.19/0001-pinctrl-gemini-Mask-and-set-properly.patch
new file mode 100644
index ..3cc7bad8b84c
--- /dev/null
+++
b/target/linux/gemini/patches-4.19/0001-pinctrl-gemini-Mask-and-set-properly.patch
@@ -0,0 +1,36 @@
+From f8ac3d3472a8dc99c8647a637611d146d88be8cb Mon Sep 17 00:00:00 2001
+From: Linus Walleij
+Date: Tue, 9 Oct 2018 10:09:14 +0200
+Subject: [PATCH 01/18] pinctrl: gemini: Mask and set properly
+
+The code was written under the assumption that the
+regmap_update_bits() would mask the bits in the mask and
+set the bits in the value.
+
+It missed the points that it will not set bits in the value
+unless these are also masked in the mask. Set value bits
+that are not in the mask will simply be ignored.
+
+Fixes: 06351d133dea ("pinctrl: add a Gemini SoC pin controller")
+Signed-off-by: Linus Walleij
+---
+ drivers/pinctrl/pinctrl-gemini.c | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/drivers/pinctrl/pinctrl-gemini.c
b/drivers/pinctrl/pinctrl-gemini.c
+index fa7d998e1d5a..1e484a36ff07 100644
+--- a/drivers/pinctrl/pinctrl-gemini.c
b/drivers/pinctrl/pinctrl-gemini.c
+@@ -2184,7 +2184,8 @@ static int gemini_pmx_set_mux(struct pinctrl_dev
*pctldev,
+func->name, grp->name);
+
+ regmap_read(pmx->map, GLOBAL_MISC_CTRL, &before);
+- regmap_update_bits(pmx->map, GLOBAL_MISC_CTRL, grp->mask,
++ regmap_update_bits(pmx->map, GLOBAL_MISC_CTRL,
++ grp->mask | grp->value,
+
[OpenWrt-Devel] [PATCH 4/4 v2] gemini: Add SL93512R Support
This generates images for the StorLink SL93512R reference design which is supported in kernel v4.19. Signed-off-by: Linus Walleij --- ChangeLog v1->v2: - Resend. --- target/linux/gemini/image/Makefile | 21 + 1 file changed, 21 insertions(+) diff --git a/target/linux/gemini/image/Makefile b/target/linux/gemini/image/Makefile index 59041a72a785..722df1c82b00 100644 --- a/target/linux/gemini/image/Makefile +++ b/target/linux/gemini/image/Makefile @@ -39,6 +39,19 @@ define Build/dns313-images if [ -d $(BIN_DIR)/.boot ] ; then rm -rf $(BIN_DIR)/.boot ; fi endef +# Create the special SL93512R image format with the squashfs +# split across two "partitions" named rd.gz and hddapp.tgz but +# essentially just being used by OpenWRT as one big squashfs +# partition +define Build/sl93512r-images + dd if=$(IMAGE_ROOTFS) of=$(BIN_DIR)/rd.gz bs=6144k conv=sync + dd if=$(IMAGE_ROOTFS) of=$(BIN_DIR)/hddapp.bz2 bs=6144k count=1 seek=1 + cp $(IMAGE_KERNEL) $(BIN_DIR)/zImage + mv $(BIN_DIR)/rd.gz $(BIN_DIR)/$(IMG_PREFIX)-sl93512r-rd.gz + mv $(BIN_DIR)/hddapp.bz2 $(BIN_DIR)/$(IMG_PREFIX)-sl93512r-hddapp.bz2 + mv $(BIN_DIR)/zImage $(BIN_DIR)/$(IMG_PREFIX)-sl93512r-zImage +endef + # Create the special NAS4220B image format with the squashfs # and overlay inside the "rd.gz" file. We pad it out to 6144K # which is the size of the initramfs partition. @@ -122,6 +135,14 @@ define Device/dlink-dns-313 endef TARGET_DEVICES += dlink-dns-313 +define Device/sl93512r + DEVICE_TITLE := StorLink SL93512R Reference Design + IMAGES += sl93512r-image + IMAGE/sl93512r-image := sl93512r-images + DEVICE_PACKAGES := $(GEMINI_NAS_PACKAGES) +endef +TARGET_DEVICES += sl93512r + define Device/nas4220b DEVICE_TITLE := Raidsonic NAS IB-4220-B IMAGES += nas4220b-image -- 2.19.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/4 v2] gemini: Switch to kernel v4.19
This adds a config and augments the gemini makefile to use kernel v4.19. These devices work so much better with v4.19 so let's immediately make it the default. Signed-off-by: Linus Walleij --- ChangeLog v1->v2: - Run the config through OpenWrt make kernel_oldconfig and inspect the result. Looks good now. --- target/linux/gemini/Makefile| 2 +- target/linux/gemini/config-4.19 | 494 2 files changed, 495 insertions(+), 1 deletion(-) create mode 100644 target/linux/gemini/config-4.19 diff --git a/target/linux/gemini/Makefile b/target/linux/gemini/Makefile index 3204b3f5d81e..03f0fdbb1d6c 100644 --- a/target/linux/gemini/Makefile +++ b/target/linux/gemini/Makefile @@ -13,7 +13,7 @@ FEATURES:=squashfs pci rtc usb dt gpio display CPU_TYPE:=fa526 MAINTAINER:=Roman Yeryomin -KERNEL_PATCHVER:=4.14 +KERNEL_PATCHVER:=4.19 define Target/Description Build firmware images for the StorLink/Cortina Gemini CS351x ARM FA526 CPU diff --git a/target/linux/gemini/config-4.19 b/target/linux/gemini/config-4.19 new file mode 100644 index ..2bca204a91c8 --- /dev/null +++ b/target/linux/gemini/config-4.19 @@ -0,0 +1,494 @@ +CONFIG_ALIGNMENT_TRAP=y +CONFIG_AMBA_PL08X=y +CONFIG_ARCH_CLOCKSOURCE_DATA=y +CONFIG_ARCH_GEMINI=y +CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y +CONFIG_ARCH_HAS_ELF_RANDOMIZE=y +CONFIG_ARCH_HAS_FORTIFY_SOURCE=y +CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y +CONFIG_ARCH_HAS_KCOV=y +CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y +CONFIG_ARCH_HAS_PHYS_TO_DMA=y +CONFIG_ARCH_HAS_RESET_CONTROLLER=y +CONFIG_ARCH_HAS_SET_MEMORY=y +CONFIG_ARCH_HAS_SG_CHAIN=y +CONFIG_ARCH_HAS_STRICT_KERNEL_RWX=y +CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y +CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y +CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y +# CONFIG_ARCH_MOXART is not set +CONFIG_ARCH_MULTIPLATFORM=y +CONFIG_ARCH_MULTI_V4=y +# CONFIG_ARCH_MULTI_V4T is not set +CONFIG_ARCH_MULTI_V4_V5=y +# CONFIG_ARCH_MULTI_V5 is not set +CONFIG_ARCH_NR_GPIO=0 +CONFIG_ARCH_OPTIONAL_KERNEL_RWX=y +CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y +CONFIG_ARCH_SUPPORTS_UPROBES=y +CONFIG_ARCH_USE_BUILTIN_BSWAP=y +CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y +CONFIG_ARCH_WANT_GENERAL_HUGETLB=y +CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y +CONFIG_ARM=y +CONFIG_ARM_AMBA=y +CONFIG_ARM_APPENDED_DTB=y +# CONFIG_ARM_ATAG_DTB_COMPAT is not set +CONFIG_ARM_HAS_SG_CHAIN=y +CONFIG_ARM_L1_CACHE_SHIFT=5 +CONFIG_ARM_PATCH_PHYS_VIRT=y +# CONFIG_ARM_SMMU is not set +# CONFIG_ARM_SP805_WATCHDOG is not set +CONFIG_ARM_UNWIND=y +CONFIG_ATA=y +CONFIG_ATAGS=y +CONFIG_ATA_VERBOSE_ERROR=y +CONFIG_AUTO_ZRELADDR=y +CONFIG_BINFMT_MISC=y +CONFIG_BLK_DEV_SD=y +CONFIG_BLK_MQ_PCI=y +CONFIG_BLK_SCSI_REQUEST=y +CONFIG_BOUNCE=y +# CONFIG_BPF_SYSCALL is not set +CONFIG_CLKDEV_LOOKUP=y +CONFIG_CLKSRC_MMIO=y +CONFIG_CLONE_BACKWARDS=y +CONFIG_CMA=y +CONFIG_CMA_ALIGNMENT=8 +CONFIG_CMA_AREAS=7 +# CONFIG_CMA_DEBUG is not set +# CONFIG_CMA_DEBUGFS is not set +CONFIG_CMA_SIZE_MBYTES=16 +# CONFIG_CMA_SIZE_SEL_MAX is not set +CONFIG_CMA_SIZE_SEL_MBYTES=y +# CONFIG_CMA_SIZE_SEL_MIN is not set +# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set +CONFIG_CMDLINE="console=ttyS0,19200n8" +CONFIG_CMDLINE_FROM_BOOTLOADER=y +CONFIG_COMMON_CLK=y +CONFIG_COMMON_CLK_GEMINI=y +CONFIG_CONSOLE_TRANSLATIONS=y +CONFIG_COREDUMP=y +CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y +CONFIG_CPU_32v4=y +CONFIG_CPU_ABRT_EV4=y +# CONFIG_CPU_BPREDICT_DISABLE is not set +CONFIG_CPU_CACHE_FA=y +CONFIG_CPU_CACHE_VIVT=y +CONFIG_CPU_COPY_FA=y +CONFIG_CPU_CP15=y +CONFIG_CPU_CP15_MMU=y +# CONFIG_CPU_DCACHE_WRITETHROUGH is not set +CONFIG_CPU_FA526=y +# CONFIG_CPU_ICACHE_DISABLE is not set +CONFIG_CPU_NO_EFFICIENT_FFS=y +CONFIG_CPU_PABRT_LEGACY=y +CONFIG_CPU_TLB_FA=y +CONFIG_CPU_USE_DOMAINS=y +CONFIG_CRASH_CORE=y +CONFIG_CRC16=y +# CONFIG_CRC32_SARWATE is not set +CONFIG_CRC32_SLICEBY8=y +CONFIG_CRC_CCITT=y +CONFIG_CRC_ITU_T=y +CONFIG_CROSS_MEMORY_ATTACH=y +CONFIG_CRYPTO_AEAD=y +CONFIG_CRYPTO_AEAD2=y +CONFIG_CRYPTO_CCM=y +CONFIG_CRYPTO_CMAC=y +CONFIG_CRYPTO_CRC32C=y +CONFIG_CRYPTO_CTR=y +CONFIG_CRYPTO_DES=y +CONFIG_CRYPTO_DRBG=y +CONFIG_CRYPTO_DRBG_HMAC=y +CONFIG_CRYPTO_DRBG_MENU=y +CONFIG_CRYPTO_ECB=y +CONFIG_CRYPTO_ECHAINIV=y +CONFIG_CRYPTO_GCM=y +CONFIG_CRYPTO_GF128MUL=y +CONFIG_CRYPTO_GHASH=y +CONFIG_CRYPTO_HASH=y +CONFIG_CRYPTO_HASH2=y +CONFIG_CRYPTO_HMAC=y +CONFIG_CRYPTO_HW=y +CONFIG_CRYPTO_JITTERENTROPY=y +CONFIG_CRYPTO_MANAGER=y +CONFIG_CRYPTO_MANAGER2=y +CONFIG_CRYPTO_MD4=y +CONFIG_CRYPTO_MD5=y +CONFIG_CRYPTO_NULL=y +CONFIG_CRYPTO_NULL2=y +CONFIG_CRYPTO_RNG=y +CONFIG_CRYPTO_RNG2=y +CONFIG_CRYPTO_RNG_DEFAULT=y +CONFIG_CRYPTO_SEQIV=y +CONFIG_CRYPTO_SHA256=y +CONFIG_CRYPTO_WORKQUEUE=y +CONFIG_DEBUG_BUGVERBOSE=y +CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S" +CONFIG_DEBUG_MEMORY_INIT=y +# CONFIG_DEBUG_USER is not set +CONFIG_DECOMPRESS_BZIP2=y +CONFIG_DECOMPRESS_GZIP=y +CONFIG_DECOMPRESS_LZ4=y +CONFIG_DECOMPRESS_LZMA=y +CONFIG_DECOMPRESS_LZO=y +CONFIG_DECOMPRESS_XZ=y +CONFIG_DEFAULT_CFQ=y +# CONFIG_DEFAULT_DEADLINE is not set +CONFIG_DEFAULT_IOSCHED="cfq" +CO
[OpenWrt-Devel] [PATCH 3/4 v2] gemini: Drop switch kmod and swconfig
The DIR-685 needs this module compiled in for safety (it is facing the LAN ports) and it is now using the DSA switch architecture so swconfig is not needed. Signed-off-by: Linus Walleij --- ChangeLog v1->v2: - Resend. --- target/linux/gemini/image/Makefile | 1 - 1 file changed, 1 deletion(-) diff --git a/target/linux/gemini/image/Makefile b/target/linux/gemini/image/Makefile index c1d7792bf8ff..59041a72a785 100644 --- a/target/linux/gemini/image/Makefile +++ b/target/linux/gemini/image/Makefile @@ -108,7 +108,6 @@ GEMINI_NAS_PACKAGES:=kmod-md-mod kmod-md-linear kmod-md-multipath \ define Device/dlink-dir-685 DEVICE_TITLE := D-Link DIR-685 Xtreme N Storage Router DEVICE_PACKAGES := $(GEMINI_NAS_PACKAGES) \ - kmod-switch-rtl8366rb swconfig \ rt2800-pci IMAGES += dir685-image IMAGE/dir685-image := dir685-images -- 2.19.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 0/4 v2] Update Gemini to kernel v4.19
This updates the Gemini platform to use kernel v4.19. Since many of the in-flight patches are upstream in v4.19 we cut down a bit on the patch burden with this, and we also invented and patched some new stuff. As the Gemini platforms use DSA switches as of v4.19 we don't need the switch kmod or swconfig anymore. A new reference design named SL93512R is available so support it. If the first patch is too big, the patches are also available here: https://dflund.se/~triad/krad/gemini/openwrt/ On popular request also pushed to github: https://github.com/linusw/openwrt Branch "gemini-v4.19" Linus Walleij (4): gemini: Add v4.19 kernel patches gemini: Switch to kernel v4.19 gemini: Drop switch kmod and swconfig gemini: Add SL93512R Support target/linux/gemini/Makefile | 2 +- target/linux/gemini/config-4.19 | 494 ++ target/linux/gemini/image/Makefile| 22 +- ...pinctrl-gemini-Mask-and-set-properly.patch | 36 ++ ...inctrl-gemini-Fix-up-TVC-clock-group.patch | 146 ++ ...nctrl-gemini-Drop-noisy-debug-prints.patch | 87 +++ .../0004-boot-sq201-from-sda1.patch | 25 + ...hysmap_of-Move-custom-initialization.patch | 52 ++ ...physmap_of_gemini-Handle-pin-control.patch | 194 +++ ...he-D-Link-DIR-685-MTD-partition-info.patch | 71 +++ ...8-ARM-dts-Enable-Gemini-flash-access.patch | 169 ++ ...rtitions-Add-RedBoot-FIS-DT-bindings.patch | 51 ++ ...ns-Add-second-compatible-for-redboot.patch | 77 +++ ...11-ARM-dts-Fix-up-SQ201-flash-access.patch | 73 +++ ...ARM-dts-Blank-D-Link-DIR-685-console.patch | 30 ++ ...ost-fotg2-add-silicon-clock-handling.patch | 123 + ...st-add-DT-bindings-for-faraday-fotg2.patch | 69 +++ ...b-host-fotg2-add-device-tree-probing.patch | 48 ++ ...t-fotg2-add-Gemini-specific-handling.patch | 138 + ...t-fotg2-restart-hcd-after-port-reset.patch | 32 ++ ...he-FOTG210-USB-host-to-Gemini-boards.patch | 210 21 files changed, 2147 insertions(+), 2 deletions(-) create mode 100644 target/linux/gemini/config-4.19 create mode 100644 target/linux/gemini/patches-4.19/0001-pinctrl-gemini-Mask-and-set-properly.patch create mode 100644 target/linux/gemini/patches-4.19/0002-pinctrl-gemini-Fix-up-TVC-clock-group.patch create mode 100644 target/linux/gemini/patches-4.19/0003-pinctrl-gemini-Drop-noisy-debug-prints.patch create mode 100644 target/linux/gemini/patches-4.19/0004-boot-sq201-from-sda1.patch create mode 100644 target/linux/gemini/patches-4.19/0005-mtd-physmap_of-Move-custom-initialization.patch create mode 100644 target/linux/gemini/patches-4.19/0006-mtd-physmap_of_gemini-Handle-pin-control.patch create mode 100644 target/linux/gemini/patches-4.19/0007-ARM-dts-Fix-up-the-D-Link-DIR-685-MTD-partition-info.patch create mode 100644 target/linux/gemini/patches-4.19/0008-ARM-dts-Enable-Gemini-flash-access.patch create mode 100644 target/linux/gemini/patches-4.19/0009-mtd-partitions-Add-RedBoot-FIS-DT-bindings.patch create mode 100644 target/linux/gemini/patches-4.19/0010-mtd-partitions-Add-second-compatible-for-redboot.patch create mode 100644 target/linux/gemini/patches-4.19/0011-ARM-dts-Fix-up-SQ201-flash-access.patch create mode 100644 target/linux/gemini/patches-4.19/0012-ARM-dts-Blank-D-Link-DIR-685-console.patch create mode 100644 target/linux/gemini/patches-4.19/0013-usb-host-fotg2-add-silicon-clock-handling.patch create mode 100644 target/linux/gemini/patches-4.19/0014-usb-host-add-DT-bindings-for-faraday-fotg2.patch create mode 100644 target/linux/gemini/patches-4.19/0015-usb-host-fotg2-add-device-tree-probing.patch create mode 100644 target/linux/gemini/patches-4.19/0016-usb-host-fotg2-add-Gemini-specific-handling.patch create mode 100644 target/linux/gemini/patches-4.19/0017-usb-host-fotg2-restart-hcd-after-port-reset.patch create mode 100644 target/linux/gemini/patches-4.19/0018-ARM-dts-Add-the-FOTG210-USB-host-to-Gemini-boards.patch -- 2.19.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFT] toolchain/musl: update to version 1.1.21
On Wednesday, January 23, 2019 2:26:20 PM CET Koen Vandeputte wrote: > Hi Christian, > > fwiw, I've been using every musl git bump up to this release on my > devices offshore. It has been running on ~65 devices covering multiple > arches. (armv6k-mpcore, armv7, mips24, mips74, x86_64) > > Looks really ok to me, and I statistically do see a drop in weird > one-time issues compared to 1.1.20 > > Concerning the patch itself: > > You probably will need to rebase and refresh the musl patches based on > the latest master state. I also created the bump in my staging tree when > 1.1.21 it was released, and I have an additional patch refreshed, which > is a delta to yours. You are right, I had a version bump in my tree that updated the offsets of 110-read_timezone_from_fs.patch. With it the patches are identical (apart from the commit message). > Other than that: > > Tested-by: Koen Vandeputte I'm a bit worried about: "This release makes improvements with respect to default thread stack size, including increasing the default from 80k to 128k, increasing the default guard size from 4k to 8k, and allowing the default to be increased via ELF headers so that programs that need larger stacks can be build without source-level changes, using just LDFLAGS." and it's impact on LOWMEM devices. Currently, I'm looking into making some "before and after" comparisions before moving on. Regards, Christian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] wireguard: bump to 0.0.20190123
On Wed, Jan 23, 2019 at 2:50 PM Jason A. Donenfeld wrote: > > * tools: curve25519: handle unaligned loads/stores safely > > This should fix sporadic crashes with `wg pubkey` on certain architectures. > > * netlink: auth socket changes against namespace of socket > > In WireGuard, the underlying UDP socket lives in the namespace where the > interface was created and doesn't move if the interface is moved. This > allows one to create the interface in some privileged place that has > Internet access, and then move it into a container namespace that only > has the WireGuard interface for egress. Consider the following > situation: > > 1. Interface created in namespace A. Socket therefore lives in namespace A. > 2. Interface moved to namespace B. Socket remains in namespace A. > 3. Namespace B now has access to the interface and changes the listen > port and/or fwmark of socket. Change is reflected in namespace A. > > This behavior is arguably _fine_ and perhaps even expected or > acceptable. But there's also an argument to be made that B should have > A's cred to do so. So, this patch adds a simple ns_capable check. > > * ratelimiter: build tests with !IPV6 > > Should reenable building in debug mode for systems without IPv6. > > * noise: replace getnstimeofday64 with ktime_get_real_ts64 > * ratelimiter: totalram_pages is now a function > * qemu: enable FP on MIPS > > Linux 5.0 support. > > * keygen-html: bring back pure javascript implementation > > Benoît Viguier has proofs that values will stay well within 2^53. We > also have an improved carry function that's much simpler. Probably more > constant time than emscripten's 64-bit integers. > > * contrib: introduce simple highlighter library > > This is the highlighter library being used in: > - https://twitter.com/EdgeSecurity/status/1085294681003454465 > - https://twitter.com/EdgeSecurity/status/1081953278248796165 > > It's included here as a contrib example, so that others can paste it into > their own GUI clients for having the same strictly validating highlighting. > > * netlink: use __kernel_timespec for handshake time > > This readies us for Y2038. See https://lwn.net/Articles/776435/ for more info. > > Signed-off-by: Jason A. Donenfeld > --- > package/network/services/wireguard/Makefile | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/package/network/services/wireguard/Makefile > b/package/network/services/wireguard/Makefile > index f752d3b..2e9f17e 100644 > --- a/package/network/services/wireguard/Makefile > +++ b/package/network/services/wireguard/Makefile > @@ -11,12 +11,12 @@ include $(INCLUDE_DIR)/kernel.mk > > PKG_NAME:=wireguard > > -PKG_VERSION:=0.0.20181218 > +PKG_VERSION:=0.0.20190123 > PKG_RELEASE:=1 > > PKG_SOURCE:=WireGuard-$(PKG_VERSION).tar.xz > PKG_SOURCE_URL:=https://git.zx2c4.com/WireGuard/snapshot/ > -PKG_HASH:=2e9f86acefa49dbfb7fa6f5e10d543f1885a2d5460cd5e102696901107675735 > +PKG_HASH:=edd13c7631af169e3838621b1a1bff3ef73cf7bc778eec2bd55f7c1089ffdf9b > > PKG_LICENSE:=GPL-2.0 Apache-2.0 > PKG_LICENSE_FILES:=COPYING > -- > 2.20.1 Patch pushed to master (https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=bbcd0634f8c9769a336386f8df471231d24a27cc); thx Hans > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] wireguard: bump to 0.0.20190123
* tools: curve25519: handle unaligned loads/stores safely This should fix sporadic crashes with `wg pubkey` on certain architectures. * netlink: auth socket changes against namespace of socket In WireGuard, the underlying UDP socket lives in the namespace where the interface was created and doesn't move if the interface is moved. This allows one to create the interface in some privileged place that has Internet access, and then move it into a container namespace that only has the WireGuard interface for egress. Consider the following situation: 1. Interface created in namespace A. Socket therefore lives in namespace A. 2. Interface moved to namespace B. Socket remains in namespace A. 3. Namespace B now has access to the interface and changes the listen port and/or fwmark of socket. Change is reflected in namespace A. This behavior is arguably _fine_ and perhaps even expected or acceptable. But there's also an argument to be made that B should have A's cred to do so. So, this patch adds a simple ns_capable check. * ratelimiter: build tests with !IPV6 Should reenable building in debug mode for systems without IPv6. * noise: replace getnstimeofday64 with ktime_get_real_ts64 * ratelimiter: totalram_pages is now a function * qemu: enable FP on MIPS Linux 5.0 support. * keygen-html: bring back pure javascript implementation Benoît Viguier has proofs that values will stay well within 2^53. We also have an improved carry function that's much simpler. Probably more constant time than emscripten's 64-bit integers. * contrib: introduce simple highlighter library This is the highlighter library being used in: - https://twitter.com/EdgeSecurity/status/1085294681003454465 - https://twitter.com/EdgeSecurity/status/1081953278248796165 It's included here as a contrib example, so that others can paste it into their own GUI clients for having the same strictly validating highlighting. * netlink: use __kernel_timespec for handshake time This readies us for Y2038. See https://lwn.net/Articles/776435/ for more info. Signed-off-by: Jason A. Donenfeld --- package/network/services/wireguard/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package/network/services/wireguard/Makefile b/package/network/services/wireguard/Makefile index f752d3b..2e9f17e 100644 --- a/package/network/services/wireguard/Makefile +++ b/package/network/services/wireguard/Makefile @@ -11,12 +11,12 @@ include $(INCLUDE_DIR)/kernel.mk PKG_NAME:=wireguard -PKG_VERSION:=0.0.20181218 +PKG_VERSION:=0.0.20190123 PKG_RELEASE:=1 PKG_SOURCE:=WireGuard-$(PKG_VERSION).tar.xz PKG_SOURCE_URL:=https://git.zx2c4.com/WireGuard/snapshot/ -PKG_HASH:=2e9f86acefa49dbfb7fa6f5e10d543f1885a2d5460cd5e102696901107675735 +PKG_HASH:=edd13c7631af169e3838621b1a1bff3ef73cf7bc778eec2bd55f7c1089ffdf9b PKG_LICENSE:=GPL-2.0 Apache-2.0 PKG_LICENSE_FILES:=COPYING -- 2.20.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFT] toolchain/musl: update to version 1.1.21
Hi Christian, fwiw, I've been using every musl git bump up to this release on my devices offshore. It has been running on ~65 devices covering multiple arches. (armv6k-mpcore, armv7, mips24, mips74, x86_64) Looks really ok to me, and I statistically do see a drop in weird one-time issues compared to 1.1.20 Concerning the patch itself: You probably will need to rebase and refresh the musl patches based on the latest master state. I also created the bump in my staging tree when 1.1.21 it was released, and I have an additional patch refreshed, which is a delta to yours. Other than that: Tested-by: Koen Vandeputte ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Current "OpenWrt Style Guide for DTS"?
On Tue, 22 Jan 2019 at 23:06, Jeff Kletsky wrote: > Use of CPP #include vs. Device Tree /include/ > = > > * It appears that the CPP #include is preferred. Is this correct? Yes. That one is commonly used by DTS in Linux's sources and we try to match it when possible. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Current "OpenWrt Style Guide for DTS"?
Thank you Chuanhong for handling this so well!
Few minor comments below.
On Wed, 23 Jan 2019 at 04:09, Chuanhong Guo wrote:
> On Wed, Jan 23, 2019 at 6:07 AM Jeff Kletsky wrote:
> ...
> >
> > Choice of Node Naming for Partitions
> >
> >
> > In some DTS files, the partitions are named using sequential integers.
> > In others, the offset of the partition is used.
> >
> > * Which of the two is preferred?
> >
> > uboot: u-boot@0 {
> > firmware@2 {
> > art: art@ff {
> >
> > vs.
> >
> > partition@0 {
> > partition@1 {
> > partition@2 {
> > art: partition@3 {
> Neither. It's partition@:
> https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=6dd94c2781b79ffd20f1a57a48fa2314d67ee190
It's mean to be properly documented in the:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/mtd/partition.txt
but it seems to need fixing.
> > TAB vs. SPACE Indentation
> > =
> >
> > * It appears that TAB indentation is being used. Is this correct?
> Yes.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst
> > read-only Partitions
> >
> >
> > * Is it appropriate to mark the boot-loader partition as read-only?
> >
> > * What about the art partition?
> >
> > Doing so would seem to be able help prevent users following outdated
> > or ill-advised suggestions to write to their file systems using
> > low-level access.
> Correct. Both of those partitions aren't supposed to be written normally.
> >
> > Advanced users that, for some reason, want to overwrite these critical
> > partitions could always compile their own kernel with the restriction
> > removed.
> Yes. They are always able to make their custom firmware for this purpose.
> >
> >
> >
> > ---
> > Context for the following questions is discussed below the "8<" marker
> > TL;DR Stable references to partitions for DT modification when "inheriting"
> > ---
> >
> > Partition "label" Properties
> >
> >
> > Some of the "label" properties seem obviously named, like "firmware"
> > and "art" and I assume that the kernel and drivers key off of these.
> >
> > * Is there a list of "reserved" and/or "preferred" values for the
> >label property of the partitions?
> OpenWrt kernel will try to automatically split "firmware“ into
> kernel/rootfs, and it'll auto-attach "ubi" partition as a ubi device.
> Besides these two the other names doesn't have any strict
> requirements. People usually follow what the manufacturer defined in
> their stock firmware.
Auto-splitting "firmware" partition (by its name) is enabled by:
CONFIG_MTD_SPLIT_FIRMWARE
If you use a proper compatible string it doesn't has to be named
"firmware" and you don't need CONFIG_MTD_SPLIT_FIRMWARE
--
Rafał
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
