Re: [OpenWrt-Devel] [PATCH 2/2] mvebu: remove default profile
17/01/2019 05:38, Rosen Penev: On Sun, Jan 13, 2019 at 12:28 PM Tomasz Maciej Nowak wrote: When using Image Builder and building image for Cortex A53 or A72 subtargets, it'll fail with following message: Collected errors: * opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8864. * opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8964. make[2]: *** [Makefile:153: package_install] Error 255 make[1]: *** [Makefile:114: _call_image] Error 2 This is beacuse both packages are available only for Cortex A9 subtarget and are included in PACKAGES array in default profile. Instead patching this, let's remove profiles completely, since all necessary packages are specified in DEVICE_PACKAGES array for each device. NACK. This breaks Turris Omnia compilation. Something about a clearfog bootloader. Would you please try to add the "PROFILES := Default" again to the "define Device/Default" section and check if it fixes your build error? On gemini, I noticed that due to the missing PROFILES all images are build, regardless of the selected (or currently processed in case of a multi profile build). It causes race conditions on gemini and is most likely the reason why the buildbot fails to create the images for the last weeks. I'm not yet sure where the real bug is. Mathias Signed-off-by: Tomasz Maciej Nowak --- target/linux/mvebu/image/Makefile | 1 - target/linux/mvebu/profiles/000-Default.mk | 18 -- 2 files changed, 19 deletions(-) delete mode 100644 target/linux/mvebu/profiles/000-Default.mk diff --git a/target/linux/mvebu/image/Makefile b/target/linux/mvebu/image/Makefile index be01623e86..22519bd9d0 100644 --- a/target/linux/mvebu/image/Makefile +++ b/target/linux/mvebu/image/Makefile @@ -81,7 +81,6 @@ define Build/omnia-medkit-initramfs endef define Device/Default - PROFILES := Default DEVICE_DTS := $(1) BOARD_NAME = $$(DEVICE_DTS) KERNEL_NAME := zImage diff --git a/target/linux/mvebu/profiles/000-Default.mk b/target/linux/mvebu/profiles/000-Default.mk deleted file mode 100644 index 8690dd8da5..00 --- a/target/linux/mvebu/profiles/000-Default.mk +++ /dev/null @@ -1,18 +0,0 @@ -# -# Copyright (C) 2015 OpenWrt.org -# -# This is free software, licensed under the GNU General Public License v2. -# See /LICENSE for more information. -# - -define Profile/Default - NAME:=Default Profile (all drivers) - PACKAGES:= kmod-mwlwifi wpad-basic swconfig mkf2fs e2fsprogs \ - mwlwifi-firmware-88w8864 mwlwifi-firmware-88w8964 -endef - -define Profile/Default/Description - Default package set compatible with most boards. -endef - -$(eval $(call Profile,Default)) -- 2.20.1 ___ 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 mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ath79: Add GL.iNet AR-300M-Lite: Setup with eth0 as LAN
From f6c780752d5812b24a923286700a58f174d792ae Mon Sep 17 00:00:00 2001
From: Jeff Kletsky
Date: Wed, 16 Jan 2019 12:32:15 -0800
Subject: [PATCH] ath79: Add GL.iNet AR-300M-Lite: Setup with eth0 as LAN
AR300M-Lite is single-Ethernet variant of the AR300M series
Its eth0 would otherwise be assigned to the WAN interface
making it unreachable firstboot or failsafe.
Removes the assignment of GPIO 2 as an "LED" as the feature
to switch the power to the USB port is not present this version
Installation instructions from OEM (OpenWrt variant):
* Upload the sysupgrade image to the device
* Flash with "sysupgrade -n -F "
Tested on GL.iNet AR300M-Lite
Signed-off-by: Jeff Kletsky
---
target/linux/ath79/base-files/etc/board.d/02_network | 1 +
target/linux/ath79/dts/qca9531_glinet_gl-ar300m-lite.dts | 11 +++
target/linux/ath79/image/generic.mk | 9 +
3 files changed, 21 insertions(+)
create mode 100644 target/linux/ath79/dts/qca9531_glinet_gl-ar300m-lite.dts
diff --git a/target/linux/ath79/base-files/etc/board.d/02_network
b/target/linux/ath79/base-files/etc/board.d/02_network
index 3eb0e413f3..fa947203f8 100755
--- a/target/linux/ath79/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/base-files/etc/board.d/02_network
@@ -13,6 +13,7 @@ ath79_setup_interfaces()
devolo,dvl1200i|\
devolo,dvl1750c|\
devolo,dvl1750i|\
+ glinet,ar300m-lite|\
ocedo,koala|\
ocedo,raccoon|\
pcs,cap324|\
diff --git a/target/linux/ath79/dts/qca9531_glinet_gl-ar300m-lite.dts
b/target/linux/ath79/dts/qca9531_glinet_gl-ar300m-lite.dts
new file mode 100644
index 00..c38fcf735d
--- /dev/null
+++ b/target/linux/ath79/dts/qca9531_glinet_gl-ar300m-lite.dts
@@ -0,0 +1,11 @@
+/dts-v1/;
+
+#include "qca9531_glinet_gl-ar300m-nor.dts"
+
+/ {
+ compatible = "glinet,gl-ar300m-lite", "qca,qca9531";
+ model = "GL.iNet GL-AR300M-Lite";
+};
+
+/delete-node/ &{/leds/usb};
+
diff --git a/target/linux/ath79/image/generic.mk
b/target/linux/ath79/image/generic.mk
index 22ba5305b1..38cdd5d109 100644
--- a/target/linux/ath79/image/generic.mk
+++ b/target/linux/ath79/image/generic.mk
@@ -296,6 +296,15 @@ define Device/glinet_gl-ar150
endef
TARGET_DEVICES += glinet_gl-ar150
+define Device/glinet_gl-ar300m-lite
+ ATH_SOC := qca9531
+ DEVICE_TITLE := GL.iNet GL-AR300M-Lite
+ DEVICE_PACKAGES := kmod-usb-core kmod-usb2
+ IMAGE_SIZE := 16000k
+ SUPPORTED_DEVICES += gl-ar300m-lite
+endef
+TARGET_DEVICES += glinet_gl-ar300m-lite
+
define Device/glinet_gl-ar300m-nor
ATH_SOC := qca9531
DEVICE_TITLE := GL.iNet GL-AR300M
--
2.11.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC 6/6] grub2: add preinit hook for bootloader upgrade
I'm somewhat apprehensive about this applying to all targets that consume GRUB2. On x86 and x86_64 images, I believe sysupgrade lays down every partition in the image over its equivalent already on the device. Since the bootloader (MBR, presumably, for most x86 targets) lives in the early part of the disk and chain-loads the later phase, does it not suffice to update the grub2 core module on the boot patition? A few questions, though: * Should the grub2 install changes be part of a variant, or a target-specific flag? * Is reinstalling the bootloader after sysupgrade dangerous? * If there is a target that doesn't support BIOS boot, could using grub-bios-setup cause problems for it? Sorry if this message comes up out-of-order. I wasn't previously subscribed to the list, and I have tried to craft the reply properly . . . Thanks, -d ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] mvebu: remove default profile
On Sun, Jan 13, 2019 at 12:28 PM Tomasz Maciej Nowak wrote: > > When using Image Builder and building image for Cortex A53 or > A72 subtargets, it'll fail with following message: > > Collected errors: > * opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8864. > * opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8964. > make[2]: *** [Makefile:153: package_install] Error 255 > make[1]: *** [Makefile:114: _call_image] Error 2 > > This is beacuse both packages are available only for Cortex A9 subtarget > and are included in PACKAGES array in default profile. Instead patching > this, let's remove profiles completely, since all necessary packages are > specified in DEVICE_PACKAGES array for each device. NACK. This breaks Turris Omnia compilation. Something about a clearfog bootloader. > > Signed-off-by: Tomasz Maciej Nowak > --- > target/linux/mvebu/image/Makefile | 1 - > target/linux/mvebu/profiles/000-Default.mk | 18 -- > 2 files changed, 19 deletions(-) > delete mode 100644 target/linux/mvebu/profiles/000-Default.mk > > diff --git a/target/linux/mvebu/image/Makefile > b/target/linux/mvebu/image/Makefile > index be01623e86..22519bd9d0 100644 > --- a/target/linux/mvebu/image/Makefile > +++ b/target/linux/mvebu/image/Makefile > @@ -81,7 +81,6 @@ define Build/omnia-medkit-initramfs > endef > > define Device/Default > - PROFILES := Default >DEVICE_DTS := $(1) >BOARD_NAME = $$(DEVICE_DTS) >KERNEL_NAME := zImage > diff --git a/target/linux/mvebu/profiles/000-Default.mk > b/target/linux/mvebu/profiles/000-Default.mk > deleted file mode 100644 > index 8690dd8da5..00 > --- a/target/linux/mvebu/profiles/000-Default.mk > +++ /dev/null > @@ -1,18 +0,0 @@ > -# > -# Copyright (C) 2015 OpenWrt.org > -# > -# This is free software, licensed under the GNU General Public License v2. > -# See /LICENSE for more information. > -# > - > -define Profile/Default > - NAME:=Default Profile (all drivers) > - PACKAGES:= kmod-mwlwifi wpad-basic swconfig mkf2fs e2fsprogs \ > - mwlwifi-firmware-88w8864 mwlwifi-firmware-88w8964 > -endef > - > -define Profile/Default/Description > - Default package set compatible with most boards. > -endef > - > -$(eval $(call Profile,Default)) > -- > 2.20.1 > > > ___ > 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 2/2] mpc85xx: add support for OCEDO Panda
CPU: FSL P1020 (2x 800MHz E500 PPC)
RAM: 1GB DDR3
FLASH: 256MiB NAND
WiFi: 2x Atheros AR9382 2x2:2 abgn
ETH: 2x BCM54616S - 1x BCM53128 8-port switch
LED: 5x LEDs (Power, WiFi1, WiFi2, N/D, SYS)
BTN: 1x RESET
Installation
1. Download initrams kernel image, dtb binary and sysupgrade image.
2. Place initramfs kernel into tftp root directory. Rename to
"panda-uimage-factory".
3. Place dtb binary into tftp root directory. Rename to "panda.fdt".
4. Start tftp server on 192.168.100.8/24.
5. Power up the device with the reset button pressed. It will download
the initrams and dtb via tftp and boot into OpenWRT in RAM.
6. SSH into the device and remove the factory partitions.
> ubirmvol /dev/ubi0 --name=kernel1
> ubirmvol /dev/ubi0 --name=rootfs1
> ubirmvol /dev/ubi0 --name=devicetree1
You will have around 60 MiB of free space with that.
You can also delete "kernel2", "devicetree2", "rootfs2" and "storage"
respectively in case you do not want to go back to the vendor firmware.
7. Modify the U-Boot bootcmd to allow for booting OpenWRT
> fw_setenv bootcmd_owrt "ubi part ubi && ubi read 0x100 kernel
&& bootm 0x100"
> fw_setenv bootargs_owrt "setenv bootargs console=ttyS0,115200
ubi.mtd=3,2048"
> fw_setenv bootcmd "run bootargs_owrt; run bootcmd_owrt"
8. Transfer the sysupgrade image via scp into the /tmp directory.
9. Upgrade the device
> sysupgrade -n /tmp/
Signed-off-by: David Bauer
---
package/boot/uboot-envtools/files/mpc85xx | 22 ++
.../mpc85xx/base-files/etc/board.d/02_network | 5 +
.../etc/hotplug.d/ieee80211/10-fix-wifi-mac | 5 +
.../base-files/lib/upgrade/platform.sh| 1 +
target/linux/mpc85xx/config-4.14 | 1 +
.../files/arch/powerpc/boot/dts/panda.dts | 264 ++
.../files/arch/powerpc/platforms/85xx/panda.c | 91 ++
target/linux/mpc85xx/image/Makefile | 14 +
target/linux/mpc85xx/p1020/config-default | 22 ++
target/linux/mpc85xx/p1020/target.mk | 1 +
.../106-powerpc-85xx-panda-support.patch | 34 +++
.../105-powerpc-85xx-panda-support.patch | 34 +++
12 files changed, 494 insertions(+)
create mode 100644 package/boot/uboot-envtools/files/mpc85xx
create mode 100644 target/linux/mpc85xx/files/arch/powerpc/boot/dts/panda.dts
create mode 100644
target/linux/mpc85xx/files/arch/powerpc/platforms/85xx/panda.c
create mode 100644
target/linux/mpc85xx/patches-4.14/106-powerpc-85xx-panda-support.patch
create mode 100644
target/linux/mpc85xx/patches-4.19/105-powerpc-85xx-panda-support.patch
diff --git a/package/boot/uboot-envtools/files/mpc85xx
b/package/boot/uboot-envtools/files/mpc85xx
new file mode 100644
index 00..d219b57cb1
--- /dev/null
+++ b/package/boot/uboot-envtools/files/mpc85xx
@@ -0,0 +1,22 @@
+#!/bin/sh
+
+[ -e /etc/config/ubootenv ] && exit 0
+
+touch /etc/config/ubootenv
+
+. /lib/uboot-envtools.sh
+. /lib/functions.sh
+
+board=$(board_name)
+
+case "$board" in
+ocedo,panda)
+ ubootenv_add_uci_config "/dev/mtd1" "0x0" "0x2" "0x2"
+ ubootenv_add_uci_config "/dev/mtd2" "0x0" "0x2" "0x2"
+ ;;
+esac
+
+config_load ubootenv
+config_foreach ubootenv_add_app_config ubootenv
+
+exit 0
diff --git a/target/linux/mpc85xx/base-files/etc/board.d/02_network
b/target/linux/mpc85xx/base-files/etc/board.d/02_network
index 19f01a6589..d6b4eebf14 100755
--- a/target/linux/mpc85xx/base-files/etc/board.d/02_network
+++ b/target/linux/mpc85xx/base-files/etc/board.d/02_network
@@ -13,6 +13,11 @@ case "$board" in
aerohive,hiveap-330)
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
+ocedo,panda)
+ ucidef_set_interface_wan "eth1"
+ ucidef_add_switch "switch0" \
+ "0:lan" "1:lan" "2:lan" "3:lan" "4:lan" "5:lan" "6:lan" "7:lan"
"8u@eth0"
+ ;;
tplink,tl-wdr4900-v1)
ucidef_add_switch "switch0" \
"0@eth0" "2:lan:1" "3:lan:2" "4:lan:3" "5:lan:4" "1:wan"
diff --git
a/target/linux/mpc85xx/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
b/target/linux/mpc85xx/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
index 3092cebfc9..f153b53c8e 100644
--- a/target/linux/mpc85xx/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
+++ b/target/linux/mpc85xx/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
@@ -12,6 +12,11 @@ PHYNBR=${DEVPATH##*/phy}
board=$(board_name)
case "$board" in
+ocedo,panda)
+ WMAC=wmac$(($PHYNBR + 1))
+ MAC=$(mtd_get_mac_ascii uboot-env0 ${WMAC})
+ echo ${MAC} > /sys${DEVPATH}/macaddress
+ ;;
sophos,red-15w-rev1)
echo $(mtd_get_mac_ascii u-boot-env ethaddr) > /sys${DEVPATH}/macaddress
;;
diff --git a/target/linux/mpc85xx/base-files/lib/upgrade/platform.sh
b/target/linux/mpc85xx/base-files/lib/upgrade/platform.sh
index 9f49d0ddce..0e9a68ebdf 100755
--- a/target/linux/mpc85xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/mpc85xx/base-files/lib/upgrade/platform.sh
@@ -13,6
[OpenWrt-Devel] [PATCH 1/2] mpc85xx: use generic diag.sh
This commit removes the target-specific diag.sh script. This way, the
generic one is used for the target, which uses DT-aliases to specify the
LEDs used.
This way, we are also able to use different LEDs to indicate different
states. We use green status LEDs for indicating boot and a running
system. Where possible, the red status LED is used to indicate failsafe
mode and a running upgrade.
Signed-off-by: David Bauer
---
target/linux/mpc85xx/base-files/etc/diag.sh | 41 ---
.../arch/powerpc/boot/dts/hiveap-330.dts | 11 -
.../arch/powerpc/boot/dts/red-15w-rev1.dts| 11 -
.../arch/powerpc/boot/dts/tl-wdr4900-v1.dts | 6 ++-
4 files changed, 23 insertions(+), 46 deletions(-)
delete mode 100644 target/linux/mpc85xx/base-files/etc/diag.sh
diff --git a/target/linux/mpc85xx/base-files/etc/diag.sh
b/target/linux/mpc85xx/base-files/etc/diag.sh
deleted file mode 100644
index e344d4b756..00
--- a/target/linux/mpc85xx/base-files/etc/diag.sh
+++ /dev/null
@@ -1,41 +0,0 @@
-#!/bin/sh
-# Copyright (C) 2013 OpenWrt.org
-
-. /lib/functions.sh
-. /lib/functions/leds.sh
-
-get_status_led() {
- case $(board_name) in
- aerohive,hiveap-330)
- status_led="hiveap-330:green:tricolor0"
- ;;
- sophos,red-15w-rev1)
- status_led="red-15w-rev1:green:system"
- ;;
- tplink,tl-wdr4900-v1)
- status_led="tp-link:blue:system"
- ;;
- esac
-}
-
-set_state() {
- get_status_led
-
- case "$1" in
- preinit)
- status_led_blink_preinit
- ;;
-
- failsafe)
- status_led_blink_failsafe
- ;;
-
- preinit_regular)
- status_led_blink_preinit_regular
- ;;
-
- done)
- status_led_on
- ;;
- esac
-}
diff --git a/target/linux/mpc85xx/files/arch/powerpc/boot/dts/hiveap-330.dts
b/target/linux/mpc85xx/files/arch/powerpc/boot/dts/hiveap-330.dts
index 5e732664aa..c4abc905e9 100644
--- a/target/linux/mpc85xx/files/arch/powerpc/boot/dts/hiveap-330.dts
+++ b/target/linux/mpc85xx/files/arch/powerpc/boot/dts/hiveap-330.dts
@@ -14,6 +14,13 @@
model = "Aerohive HiveAP-330";
compatible = "aerohive,hiveap-330";
+ aliases {
+ led-boot = _green;
+ led-failsafe = _red;
+ led-running = _green;
+ led-upgrade = _red;
+ };
+
chosen {
bootargs-override = "console=ttyS0,9600";
};
@@ -109,12 +116,12 @@
compatible = "national,lp5521";
reg = <0x32>;
clock-mode = /bits/ 8 <2>;
- chan0 {
+ tricolor_red: chan0 {
chan-name = "hiveap-330:red:tricolor0";
led-cur = /bits/ 8 <0x2f>;
max-cur = /bits/ 8 <0x5f>;
};
- chan1 {
+ tricolor_green:chan1 {
chan-name =
"hiveap-330:green:tricolor0";
led-cur = /bits/ 8 <0x2f>;
max-cur = /bits/ 8 <0x5f>;
diff --git a/target/linux/mpc85xx/files/arch/powerpc/boot/dts/red-15w-rev1.dts
b/target/linux/mpc85xx/files/arch/powerpc/boot/dts/red-15w-rev1.dts
index 600426bb6e..40b8014a53 100644
--- a/target/linux/mpc85xx/files/arch/powerpc/boot/dts/red-15w-rev1.dts
+++ b/target/linux/mpc85xx/files/arch/powerpc/boot/dts/red-15w-rev1.dts
@@ -6,6 +6,13 @@
model = "Sophos RED 15w Rev.1";
compatible = "sophos,red-15w-rev1";
+ aliases {
+ led-boot = _green;
+ led-failsafe = _red;
+ led-running = _green;
+ led-upgrade = _red;
+ };
+
memory {
device_type = "memory";
};
@@ -13,12 +20,12 @@
leds {
compatible = "gpio-leds";
- system_green {
+ system_green: system_green {
gpios = < 7 0>;
label = "red-15w-rev1:green:system";
};
- system_red {
+ system_red: system_red {
gpios = < 3 0>;
label = "red-15w-rev1:red:system";
};
diff --git a/target/linux/mpc85xx/files/arch/powerpc/boot/dts/tl-wdr4900-v1.dts
b/target/linux/mpc85xx/files/arch/powerpc/boot/dts/tl-wdr4900-v1.dts
index 0969b272a8..ab4952aad5 100644
--- a/target/linux/mpc85xx/files/arch/powerpc/boot/dts/tl-wdr4900-v1.dts
+++ b/target/linux/mpc85xx/files/arch/powerpc/boot/dts/tl-wdr4900-v1.dts
@@ -24,6 +24,10 @@
aliases {
spi0 =
+ led-boot = _green;
+
[OpenWrt-Devel] [PATCH] uboot-mxs: bump to v2019.01
Also update the U-Boot BSP patch for I2SE Duckbill devices.
Signed-off-by: Michael Heimpold
---
package/boot/uboot-mxs/Makefile | 4 +-
.../patches/001-add-i2se-duckbill.patch | 40 +++
2 files changed, 35 insertions(+), 9 deletions(-)
diff --git a/package/boot/uboot-mxs/Makefile b/package/boot/uboot-mxs/Makefile
index cd26704cb6..c4485f5b3d 100644
--- a/package/boot/uboot-mxs/Makefile
+++ b/package/boot/uboot-mxs/Makefile
@@ -8,10 +8,10 @@
include $(TOPDIR)/rules.mk
include $(INCLUDE_DIR)/kernel.mk
-PKG_VERSION:=2018.09
+PKG_VERSION:=2019.01
PKG_RELEASE:=1
-PKG_HASH:=839bf23cfe8ce613a77e583a60375179d0ad324e92c82fbdd07bebf0fd142268
+PKG_HASH:=50bd7e5a466ab828914d080d5f6a432345b500e8fba1ad3b7b61e95e60d51c22
include $(INCLUDE_DIR)/u-boot.mk
include $(INCLUDE_DIR)/package.mk
diff --git a/package/boot/uboot-mxs/patches/001-add-i2se-duckbill.patch
b/package/boot/uboot-mxs/patches/001-add-i2se-duckbill.patch
index e5d3484d8e..9acb6a508d 100644
--- a/package/boot/uboot-mxs/patches/001-add-i2se-duckbill.patch
+++ b/package/boot/uboot-mxs/patches/001-add-i2se-duckbill.patch
@@ -1,4 +1,4 @@
-From 7b919a74c562ca33ae28c9214f225a79b57209e4 Mon Sep 17 00:00:00 2001
+From 6af0148a38b23ba761905f98a7211fab986033ce Mon Sep 17 00:00:00 2001
From: Michael Heimpold
Date: Thu, 13 Sep 2018 21:40:19 +0200
Subject: [PATCH] arm: mxs: add support for I2SE's Duckbill boards
@@ -43,6 +43,8 @@ Signed-off-by: Stefan Wahren
create mode 100644 configs/duckbill_defconfig
create mode 100644 include/configs/duckbill.h
+diff --git a/arch/arm/mach-imx/mxs/Kconfig b/arch/arm/mach-imx/mxs/Kconfig
+index 68072d5a1f..82aaa3ef76 100644
--- a/arch/arm/mach-imx/mxs/Kconfig
+++ b/arch/arm/mach-imx/mxs/Kconfig
@@ -50,6 +50,10 @@ config TARGET_APX4DEVKIT
@@ -64,6 +66,9 @@ Signed-off-by: Stefan Wahren
source "board/ppcag/bg0900/Kconfig"
source "board/schulercontrol/sc_sps_1/Kconfig"
source "board/technologic/ts4600/Kconfig"
+diff --git a/board/i2se/duckbill/Kconfig b/board/i2se/duckbill/Kconfig
+new file mode 100644
+index 00..98c1e4689f
--- /dev/null
+++ b/board/i2se/duckbill/Kconfig
@@ -0,0 +1,15 @@
@@ -82,6 +87,9 @@ Signed-off-by: Stefan Wahren
+ default "duckbill"
+
+endif
+diff --git a/board/i2se/duckbill/MAINTAINERS b/board/i2se/duckbill/MAINTAINERS
+new file mode 100644
+index 00..5496baa330
--- /dev/null
+++ b/board/i2se/duckbill/MAINTAINERS
@@ -0,0 +1,6 @@
@@ -91,12 +99,15 @@ Signed-off-by: Stefan Wahren
+F:board/i2se/duckbill/
+F:include/configs/duckbill.h
+F:configs/duckbill_defconfig
+diff --git a/board/i2se/duckbill/Makefile b/board/i2se/duckbill/Makefile
+new file mode 100644
+index 00..0079eb413c
--- /dev/null
+++ b/board/i2se/duckbill/Makefile
@@ -0,0 +1,10 @@
+# SPDX-License-Identifier: GPL-2.0+
+#
-+# (C) Copyright 2014-2018
++# (C) Copyright 2014-2019
+# Michael Heimpold, m...@heimpold.de.
+
+ifndefCONFIG_SPL_BUILD
@@ -104,6 +115,9 @@ Signed-off-by: Stefan Wahren
+else
+obj-y := iomux.o
+endif
+diff --git a/board/i2se/duckbill/duckbill.c b/board/i2se/duckbill/duckbill.c
+new file mode 100644
+index 00..f93c372611
--- /dev/null
+++ b/board/i2se/duckbill/duckbill.c
@@ -0,0 +1,186 @@
@@ -111,7 +125,7 @@ Signed-off-by: Stefan Wahren
+/*
+ * I2SE Duckbill board
+ *
-+ * (C) Copyright 2014-2018 Michael Heimpold
++ * (C) Copyright 2014-2019 Michael Heimpold
+ */
+
+#include
@@ -293,6 +307,9 @@ Signed-off-by: Stefan Wahren
+
+ return 0;
+}
+diff --git a/board/i2se/duckbill/iomux.c b/board/i2se/duckbill/iomux.c
+new file mode 100644
+index 00..1db3c52c34
--- /dev/null
+++ b/board/i2se/duckbill/iomux.c
@@ -0,0 +1,156 @@
@@ -300,7 +317,7 @@ Signed-off-by: Stefan Wahren
+/*
+ * I2SE Duckbill IOMUX setup
+ *
-+ * Copyright (C) 2013-2018 Michael Heimpold
++ * Copyright (C) 2013-2019 Michael Heimpold
+ */
+
+#include
@@ -452,6 +469,9 @@ Signed-off-by: Stefan Wahren
+ else
+ mxs_iomux_setup_multiple_pads(iomux_setup_v1,
ARRAY_SIZE(iomux_setup_v1));
+}
+diff --git a/configs/duckbill_defconfig b/configs/duckbill_defconfig
+new file mode 100644
+index 00..f92a67d53d
--- /dev/null
+++ b/configs/duckbill_defconfig
@@ -0,0 +1,38 @@
@@ -493,12 +513,15 @@ Signed-off-by: Stefan Wahren
+CONFIG_CONS_INDEX=0
+CONFIG_OF_LIBFDT=y
+# CONFIG_EFI_LOADER is not set
+diff --git a/include/configs/duckbill.h b/include/configs/duckbill.h
+new file mode 100644
+index 00..e7fce8843e
--- /dev/null
+++ b/include/configs/duckbill.h
@@ -0,0 +1,179 @@
+/* SPDX-License-Identifier: GPL-2.0+ */
+/*
-+ * Copyright (C) 2014-2018 Michael Heimpold
++ * Copyright (C) 2014-2019 Michael Heimpold
+ *
+ */
+#ifndef __CONFIGS_DUCKBILL_H__
@@ -613,7 +636,7 @@ Signed-off-by: Stefan Wahren
+ "mmcroot=/dev/mmcblk0p2\0" \
+ "mmcargs=setenv bootargs console=${console},${baudrate} " \
+ "root=${mmcroot} " \
-+
Re: [OpenWrt-Devel] [RFC 4/6] x86: geode: shrink amount of default packages
W dniu 16.01.2019 o 02:25, Philip Prindeville pisze: > Inline > >> On Jan 15, 2019, at 12:40 AM, Tomasz Maciej Nowak wrote: >> >> Hi Philip >> >> W dniu 14.01.2019 o 21:10, Philip Prindeville pisze: >> >>> Why is the hwclock being dropped everywhere? >> >> It's provided by busybox and installed by default, also greping for its >> usage in target/linux/x86/base-files returned nothing. Am I missing >> something, is the full fledged one used somewhere or by something? > > > It’s used at least two places. > > When you first get the board and bring it up and set the clock, since it’s > not usually set correctly by the factory, and it’s used by the ntpd script to > save the synchronized time when the system is taken down. But it uses options available in busybox hwclock so I still don't see a reason to add it. > >> >>> And who says the geos2, net5501, or alix2 are obsolete? >> >> They are not obsolete by any means, only the way to assign packages for >> specific device changes. Please take a look at patch nr 2 in this RFC and >> section adding target/linux/x86/image/geode.mk. There You have almost all >> packages replicated with additional geos device profile. Now You'll get two >> images, one generic, and one for geos. This distinction is here because with >> old way of adding packages, the generic image would end up with lot of >> useless, geos/dsl specific packages. > > > So why is there a Device/geos but none of the other SBC’s? None other SBC is so specific (I followed what packages were specified in profiles), and for other most drivers are enabled in kernel config. > And why doesn’t the geos DEVICE_PACKAGES include -kmod-via-rhine, since it > uses the kmod-8139cp instead? I can remove the call for generic profile and add all relevant packages if that is preferred. Anyway both of these drivers are enabled in kernel config as built-in and those kmod packages are empty. In next version of this series I'll remove kmod packages which are enabled in kernel. > > -Philip Please give this series a test. Regards, Tomasz. > > > >> >>> I have some running right here… >> >> I have WRAP which runs perfectly fine with these changes. >> -- TMN ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
