[OpenWrt-Devel] [PATCH] ipq806x: add ramdisk feature

2018-12-29 Thread INAGAKI Hiroshi
r installing OpenWrt. Therefore, on this device, when installing OpenWrt by the user, change bootcmd as follows so that WG2600HP downloads and executes initramfs image from TFTP server if necessary. ex.: bootcmd="ping ${serverip} && tftpboot 0x4400 wg2600hp-initramfs.bin;

Re: [OpenWrt-Devel] [PATCH] ramips: specify "firmware" partition format for remaining devices

2018-12-13 Thread INAGAKI Hiroshi
On 2018/12/14 1:16, Rafał Miłecki wrote: From: Rafał Miłecki It results in calling the right MTD parser directly instead of trying them one by one. Signed-off-by: Rafał Miłecki --- I'm not sure about the AR670W.dts. It seems to be using WRG according to the image generating code:

Re: [OpenWrt-Devel] [PATCH 8/8] ipq806x: specify "firmware" partition format for NEC Aterm WG2600HP

2018-12-10 Thread INAGAKI Hiroshi
On 2018/12/10 1:44, Christian Lamparter wrote: | For backwards compatibility partitions as direct subnodes of the flash device are | supported. This use is discouraged. | NOTE: also for backwards compatibility, direct subnodes that have a compatible | string are not considered partitions, as

Re: [OpenWrt-Devel] [PATCH 1/2] ramips: Update ZBT WE1026 DTS-files

2019-07-05 Thread INAGAKI Hiroshi
checking the history of the files that I relicense, there are three more people that should be added to the CC-list (INAGAKI Hiroshi, Mathias Kresin and Petr Štetiar). I have done so now, thanks for spotting this and the mistake was of course not intentional. BR, Kristian . Sorry for late response, OK

Re: [OpenWrt-Devel] [PATCH RFT] ramips: mt7621: use lzma-loader for all devices

2020-04-14 Thread INAGAKI Hiroshi
Hello, I tried this change in several routers. In the following routers, kernel 5.4 without/with your patch works fine: - Buffalo WSR-1166DHP   U-Boot 1.1.3 (Dec 16 2014 - 14:38:30) 0.09, Ralink UBoot Version: 4.2.1.0 - ELECOM WRC-1167GHBK2-S   U-Boot 1.1.3 (Jan 23 2017 - 20:06:24), Ralink

[PATCH 0/2] ramips: add support for ELECOM 2x2 11ac devices with MT7621

2020-11-28 Thread INAGAKI Hiroshi
+0x244/0x498 [ 12.694919] [<80045e2c>] worker_thread+0x168/0x5ec [ 12.704459] [<8004b630>] kthread+0x140/0x148 [ 12.712952] [<800068d8>] ret_from_kernel_thread+0x14/0x1c [ 12.724271] ---[ end trace 3c804470b09f795e ]--- [1]: https://github.com/openwrt/mt76/blob/066cc441eb8fcec

Re: [PATCH 1/2] ramips: add support for ELECOM WRC-1167GS2-B

2020-12-19 Thread INAGAKI Hiroshi
ess 86:ab:18:58:2f:15 ``` - Wi-Fi band on primary phy (2.4GHz) cannot be limitted by specifying ieee80211-freq-limit (fail to register secondary phy due to error) - mtd-mac-address in the wifi node is required for using mtd-mac-address-increment Signed-off-by: INAGAKI Hiroshi ---

Re: [PATCH 1/2] ramips: add support for ELECOM WRC-1167GS2-B

2020-12-19 Thread INAGAKI Hiroshi
Hello, On 2020/12/20 4:38, Adrian Schmutzler wrote: Hi, -Original Message- From: INAGAKI Hiroshi [mailto:musashino.o...@gmail.com] Sent: Samstag, 19. Dezember 2020 14:54 To: Adrian Schmutzler ; openwrt- de...@lists.openwrt.org Subject: Re: [PATCH 1/2] ramips: add support for ELECOM

Re: [PATCH] base-files: fix configuration generation of network if "bridge" exists

2021-05-24 Thread INAGAKI Hiroshi
Hi Rafał, thank you for your reply. On 2021/05/24 6:06, Rafał Miłecki wrote: On 23.05.2021 13:30, INAGAKI Hiroshi wrote: After the commit 43fc720657c6e3b30c6ed89d7227ee6e646c158b ("base-files: generate "device UCI type section for bridge"), the wrong network configurati

[PATCH] base-files: fix configuration generation of network if "bridge" exists

2021-05-23 Thread INAGAKI Hiroshi
RX bytes:34944 (34.1 KiB) TX bytes:34944 (34.1 KiB) root@OpenWrt:/# This patch fixes this issue. Fixes: 43fc720657 ("base-files: generate "device" UCI type section for bridge") Signed-off-by: INAGAKI Hiroshi --- package/base-files/files/bin/config_generate | 3 ++- 1 f

Re: [PATCH 0/5] mediatek: Add support for Buffalo WSR-2533DHP2

2021-03-10 Thread INAGAKI Hiroshi
Hi Hauke, On 2021/03/10 8:52, Hauke Mehrtens wrote: These patches are adding support for different TRX magics and later support for the Buffalo WSR-2533DHP2. This was developed mostly by INAGAKI Hiroshi and I did some fixes and cleaned the patches up in the last days. I added the two patches

[PATCH 0/3] realtek: add support for Panasonic Switch-M8eG PN28080K

2021-10-03 Thread INAGAKI Hiroshi
N28xx0) is a Broadcom SoC based hardware. - This series uses the VxWorks-based kernel in stock firmware. [1]: https://github.com/openwrt/openwrt/pull/4209 INAGAKI Hiroshi (3): realtek: enable pca953x driver for target realtek: enable gpio-restart driver in target realtek: add support for Panas

[PATCH 3/3] realtek: add support for Panasonic Switch-M8eG PN28080K

2021-10-03 Thread INAGAKI Hiroshi
setenv bootcmd 'bootm 0x8100' on OpenWrt: fw_setenv loadaddr fw_setenv bootcmd 'bootm 0x8100' 2. Perform reset or reboot on U-Boot: reset on OpenWrt: reboot Signed-off-by: INAGAKI Hiroshi --- .../rtl8380_panasonic_m8eg-pn28080k.dts | 103

[PATCH 1/3] realtek: enable pca953x driver for target

2021-10-03 Thread INAGAKI Hiroshi
The system status LED on Panasonic Switch-M8eG PN28080K is connected to a PCA9539PW. To use the LED as a status LED of OpenWrt while booting, enable the pca953x driver and built-in to the kernel. Signed-off-by: INAGAKI Hiroshi --- target/linux/realtek/config-5.10 | 3 +++ target/linux/realtek

[PATCH 2/3] realtek: enable gpio-restart driver in target

2021-10-03 Thread INAGAKI Hiroshi
On Panasonic Switch-M8eG PN28080K, a GPIO pin on PCA9539 chip is used for for hard-reset of the system. To use this, enable gpio-restart driver and built-in to the kernel. Signed-off-by: INAGAKI Hiroshi --- target/linux/realtek/config-5.10 | 1 + target/linux/realtek/config-5.4 | 1 + 2 files

Re: [PATCH v2 2/2] realtek: add support for Panasonic Switch-M8eG PN28080K

2021-12-04 Thread INAGAKI Hiroshi
Hi Sander, Thank you for the review. On 2021/12/05 1:02, Sander Vanheule wrote: Hi Hiroshi, Thanks for the update. Some inline comments below. On Tue, 2021-11-30 at 19:43 +0900, INAGAKI Hiroshi wrote: Panasonic Switch-M8eG PN28080K is a 8 + 1 port gigabit switch, based on RTL8380M

Re: [PATCH 2/3] realtek: enable gpio-restart driver in target

2021-11-13 Thread INAGAKI Hiroshi
Hi, On 2021/11/13 6:15, Sander Vanheule wrote: As made clear by Paul Fertser, gpio-restart isn't actually used unless _machine_restart() is also removed. Although I don't mind adding the correct nodes to the DTS already (maybe others disagree). Adding the driver already would only have the

Re: [PATCH 3/3] realtek: add support for Panasonic Switch-M8eG PN28080K

2021-11-13 Thread INAGAKI Hiroshi
Hi Sander, Thank you for your review. On 2021/11/13 7:46, Sander Vanheule wrote: Hi Hiroshi, On Sun, 2021-10-03 at 15:53 +0900, INAGAKI Hiroshi wrote: Panasonic M8eG PN28080K is a 8 + 1 port gigabit switch, based on RTL8380M. Specification: - SoC   : Realtek RTL8380M - RAM

Re: [PATCH 3/3] realtek: add support for Panasonic Switch-M8eG PN28080K

2021-11-20 Thread INAGAKI Hiroshi
Hi Sander, On 2021/11/14 17:52, Sander Vanheule wrote: Hi Hiroshi, On Sun, 2021-11-14 at 14:32 +0900, INAGAKI Hiroshi wrote: Hi Sander, Thank you for your review. On 2021/11/13 7:46, Sander Vanheule wrote: Hi Hiroshi, On Sun, 2021-10-03 at 15:53 +0900, INAGAKI Hiroshi wrote: Panasonic

Re: [PATCH 0/3] realtek: add support for Panasonic Switch-M8eG PN28080K

2021-11-29 Thread INAGAKI Hiroshi
Hi Hauke, Thank you for the guidance. On 2021/11/30 6:37, Hauke Mehrtens wrote: On 11/12/21 10:00 PM, Sander Vanheule wrote: Hi, On Sun, 2021-10-03 at 15:53 +0900, INAGAKI Hiroshi wrote: [...] INAGAKI Hiroshi (3):    realtek: enable pca953x driver for target    realtek: enable gpio

[PATCH v2 0/2] realtek: add support for Panasonic Switch-M8eG PN28080K

2021-11-30 Thread INAGAKI Hiroshi
s" instead of "gpio-keys-polled" - update/remove comments in mtd partitions - use "led-*" scheme and add color/function properties for each node of LEDs - drop unnecessary default values from gpio-restart node INAGAKI Hiroshi (2): realtek: enable pca953x driver for target

[PATCH v2 1/2] realtek: enable pca953x driver for target

2021-11-30 Thread INAGAKI Hiroshi
The system status LED on Panasonic Switch-M8eG PN28080K is connected to a PCA9539PW. To use the LED as a status LED of OpenWrt while booting, enable the pca953x driver and built-in to the kernel. Also enable CONFIG_GPIO_PCA953X_IRQ to use interrupt via RTL83xx GPIO. Signed-off-by: INAGAKI Hiroshi

[PATCH v2 2/2] realtek: add support for Panasonic Switch-M8eG PN28080K

2021-11-30 Thread INAGAKI Hiroshi
ware: 1. Delete "loadaddr" variable and set "bootcmd" to the original value on U-Boot: setenv loadaddr setenv bootcmd 'bootm 0x8100' on OpenWrt: fw_setenv loadaddr fw_setenv bootcmd 'bootm 0x8100' 2. Perform reset or reboot on U-Boot:

Re: [PATCH v4 2/2] realtek: add support for Panasonic Switch-M8eG PN28080K

2022-03-13 Thread INAGAKI Hiroshi
Hi Sander, Thank you for your review. On 2022/03/13 19:41, Sander Vanheule wrote: Hi Hiroshi, On Wed, 2022-03-09 at 23:31 +0900, INAGAKI Hiroshi wrote: Panasonic Switch-M8eG PN28080K is a 8 + 1 port gigabit switch, based on RTL8380M. Specification: - SoC   : Realtek RTL8380M - RAM

[PATCH fstools] partname: add "fstools_use_partlabel" option to find part from label

2022-03-11 Thread INAGAKI Hiroshi
equired for I-O DATA HDL-A/HDL2-A. On they, kernel and rootfs are stored in the storage device connected to SATA, port1 or port2 and the path to the partition will be assigned dynamically. So "root=PARTLABEL=" syntax is required instead of "/dev/sdXN". Signed-off-by: INAGAKI

[PATCH v3 0/2] realtek: add support for Panasonic Switch-M8eG PN28080K

2022-03-09 Thread INAGAKI Hiroshi
o device dts - move child i2c bus definitions in PCA9545 to device dts - use actual SoC name "rtl8380" in second compatible of root INAGAKI Hiroshi (2): realtek: enable pca953x driver for target realtek: add support for Panasonic Switch-M8eG PN28080K .../rtl8380_panasonic_m8eg-pn28

[PATCH v3 2/2] realtek: add support for Panasonic Switch-M8eG PN28080K

2022-03-09 Thread INAGAKI Hiroshi
ware: 1. Delete "loadaddr" variable and set "bootcmd" to the original value on U-Boot: setenv loadaddr setenv bootcmd 'bootm 0x8100' on OpenWrt: fw_setenv loadaddr fw_setenv bootcmd 'bootm 0x8100' 2. Perform reset or reboot on U-Boot:

[PATCH v3 1/2] realtek: enable pca953x driver for target

2022-03-09 Thread INAGAKI Hiroshi
The system status LED on Panasonic Switch-M8eG PN28080K is connected to a PCA9539PW. To use the LED as a status LED of OpenWrt while booting, enable the pca953x driver and built-in to the kernel. Also enable CONFIG_GPIO_PCA953X_IRQ to use interrupt via RTL83xx GPIO. Signed-off-by: INAGAKI Hiroshi

Re: [PATCH v3 1/2] realtek: enable pca953x driver for target

2022-03-09 Thread INAGAKI Hiroshi
Oops, I forgot to update the title of this commit... I'll fix and re-send, please ignore this series. Sorry for noise... Regards, Hiroshi On 2022/03/09 21:52, INAGAKI Hiroshi wrote: The system status LED on Panasonic Switch-M8eG PN28080K is connected to a PCA9539PW. To use the LED as a status

[PATCH v4 2/2] realtek: add support for Panasonic Switch-M8eG PN28080K

2022-03-09 Thread INAGAKI Hiroshi
ware: 1. Delete "loadaddr" variable and set "bootcmd" to the original value on U-Boot: setenv loadaddr setenv bootcmd 'bootm 0x8100' on OpenWrt: fw_setenv loadaddr fw_setenv bootcmd 'bootm 0x8100' 2. Perform reset or reboot on U-Boot:

[PATCH v4 1/2] realtek: enable pca953x driver for rtl838x subtarget

2022-03-09 Thread INAGAKI Hiroshi
The system status LED on Panasonic Switch-M8eG PN28080K is connected to a PCA9539PW. To use the LED as a status LED of OpenWrt while booting, enable the pca953x driver and built-in to the kernel. Also enable CONFIG_GPIO_PCA953X_IRQ to use interrupt via RTL83xx GPIO. Signed-off-by: INAGAKI Hiroshi

[PATCH v4 0/2] realtek: add support for Panasonic Switch-M8eG PN28080K

2022-03-09 Thread INAGAKI Hiroshi
o device dts - move child i2c bus definitions in PCA9545 to device dts - use actual SoC name "rtl8380" in second compatible of root v3 -> v4: - update the title of the first commit - drop unnecessary "/delete-node/" of rtl8231 from dtsi INAGAKI Hiroshi (2): realtek: en

[PATCH fstools v2] partname: check "PARTLABEL" in root= parameter

2022-03-12 Thread INAGAKI Hiroshi
nstead of "/dev/sdXN". Signed-off-by: INAGAKI Hiroshi --- libfstools/partname.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/libfstools/partname.c b/libfstools/partname.c index f59c52e..fd499c7 100644 --- a/libfstools/partname.c +++ b/libfstools/partna

Re: [PATCH fstools] partname: add "fstools_use_partlabel" option to find part from label

2022-03-12 Thread INAGAKI Hiroshi
Hi Daniel, Thank you for your review. On 2022/03/12 19:57, Daniel Golle wrote: On Sat, Mar 12, 2022 at 01:05:17PM +0900, INAGAKI Hiroshi wrote: This patch adds "fstools_use_partlabel" option to partname driver. The Linux Kernel supports "root=PARTLABEL=" syntax, but fsto

Re: [PATCH] ipq40xx: add support for Sony NCP-HG100/Cellular

2022-03-28 Thread INAGAKI Hiroshi
Hi Christian, Thank you for your review. On 2022/03/28 4:48, Christian Lamparter wrote: Hi, On Sun, Mar 27, 2022 at 10:22 AM INAGAKI Hiroshi wrote: Sony NCP-HG100/Cellular is a IoT Gateway with 2.4/5 GHz band 11ac (WiFi-5) wireless function, based on IPQ4019. Specification: - SoC

[PATCH] ipq40xx: add support for Sony NCP-HG100/Cellular

2022-03-27 Thread INAGAKI Hiroshi
306721 128M rootfs 16 306722 568865 128M rootfs_1 17 568866 3958065 1654M rootfs_data [initial work] Signed-off-by: Iwao Yuki Co-developed-by: Iwao Yuki [adjustments, cleanups, commit message, sending patch] Signed-off-by: INAGAKI Hiroshi --- T

[fstools v2 PATCH 2/2] partname: check "PARTLABEL" in root= parameter

2022-07-02 Thread INAGAKI Hiroshi
. So "root=PARTLABEL=" syntax is required instead of "/dev/sdXN". Signed-off-by: INAGAKI Hiroshi --- v1 -> v2: - use "PARTLABEL=" string in root= parametr instead of the new fstools parameter to block searching root device v2 -> v3: - rebased on the firs

[fstools v2 PATCH 1/2] partname: check all parameters for overriding if needed

2022-07-02 Thread INAGAKI Hiroshi
passed by dtb, for OpenWrt So, this patch adds checking support for all parameters in the specified file and check all for root device ("root=" parameter). Signed-off-by: INAGAKI Hiroshi --- v1 -> v2: (no patch) v2 -> v3: - added patch to fix wrong detection of overridde

Re: [fstools v2 PATCH 1/2] partname: check all parameters for overriding if needed

2022-07-02 Thread INAGAKI Hiroshi
A, this series is not v2, it's v3... I mistook in the subject... On 2022/07/02 15:48, INAGAKI Hiroshi wrote: In bootargs, the specific parameter is overridden if needed for booting OpenWrt, such as "root=". In this case, the last specific parameter in bootargs should be re

[PATCH v2] ipq40xx: add support for Sony NCP-HG100/Cellular

2022-09-04 Thread INAGAKI Hiroshi
28193 8192K 0:HLOS 14 28194 44577 8192K 0:HLOS_1 15 44578 306721 128M rootfs 16 306722 568865 128M rootfs_1 17 568866 3958065 1654M rootfs_data [initial work] Signed-off-by: Iwao Yuki Co-developed-by: Iwao Yu

Re: [PATCH] realtek: mark clock source as continuous

2022-10-31 Thread INAGAKI Hiroshi
source as continuous, the kernel enables it to be used for high resolution timers. This allows readx_poll_timeout() to sleep for less than one system timer interval, reducing system dead time. Link: https://github.com/openwrt/openwrt/issues/7 Reported-by: INAGAKI Hiroshi Cc: Markus Sto

Re: [PATCH] ramips: use ARTIFACTS for initramfs-factory of I-O DATA WN-AX1167GR

2022-11-29 Thread INAGAKI Hiroshi
On 2022/11/29 22:04, Daniel Golle wrote: On Tue, Nov 29, 2022 at 09:30:25PM +0900, INAGAKI Hiroshi wrote: Hi Daniel, thank you for your review. On 2022/11/29 11:07, Daniel Golle wrote: On Wed, Nov 23, 2022 at 12:24:09PM +0900, INAGAKI Hiroshi wrote: ... @@ -972,10 +955,13 @@ define Device

Re: [PATCH] ramips: use ARTIFACTS for initramfs-factory of I-O DATA WN-AX1167GR

2022-11-29 Thread INAGAKI Hiroshi
Hi Daniel, thank you for your review. On 2022/11/29 11:07, Daniel Golle wrote: On Wed, Nov 23, 2022 at 12:24:09PM +0900, INAGAKI Hiroshi wrote: ... @@ -972,10 +955,13 @@ define Device/iodata_wn-ax1167gr $(Device/dsa-migration) $(Device/uimage-lzma-loader) IMAGE_SIZE := 15552k

Re: [PATCH] ramips: use ARTIFACTS for initramfs-factory of I-O DATA WN-AX1167GR

2022-11-29 Thread INAGAKI Hiroshi
On 2022/11/30 0:30, Daniel Golle wrote: On Tue, Nov 29, 2022 at 11:10:22PM +0900, INAGAKI Hiroshi wrote: [...] This seems to be caused by "image" directory in staging_dir/target-mipsel_24kc_musl/ not existing, and when I created that folder manually the build succeeded. --

[PATCH v2] ramips: use ARTIFACTS for initramfs-factory of I-O DATA WN-AX1167GR

2022-11-30 Thread INAGAKI Hiroshi
OS image partition is 0x78 (7680 KiB = 7.5 MiB), so check-size for initramfs-factory image needs to be called with the size. Signed-off-by: INAGAKI Hiroshi --- v1 -> v2 - update for IB - use append-image-stage instead of append-image - drop ifneq-endif switch of CONFIG_TARGET_ROOTFS_INITRAMFS

[PATCH] ramips: use ARTIFACTS for initramfs-factory of I-O DATA WN-AX1167GR

2022-11-22 Thread INAGAKI Hiroshi
OS image partition is 0x78 (7680 KiB = 7.5 MiB), so check-size for initramfs-factory image needs to be called with the size. Signed-off-by: INAGAKI Hiroshi --- target/linux/ramips/image/mt7621.mk | 24 +--- 1 file changed, 5 insertions(+), 19 deletions(-) diff --git a/target/li

[PATCH v3] mvebu: add support for Fortinet FortiGate 50E

2023-03-08 Thread INAGAKI Hiroshi
9b: Data Offset (jffs2) 0x19c - 0x19f: Data Length (jffs2) 0x1a0 - 0x1ff: ? *: required for initramfs image MAC addresses: (eth0): 70:4C:A5:xx:xx:7C (board-info, 0xd880 (hex)) WAN 1 : 70:4C:A5:xx:xx:7D WAN 2 : 70:4C:A5:xx:xx:7E LAN 1 : 70:4C:A5:xx:xx:7F LAN 2 : 70:4C:A5:xx:xx:80 LAN 3 : 70:4C:A5:

[PATCH 1/2] mvebu: cortexa9: enable Ethernet PHY LED trigger

2023-03-23 Thread INAGAKI Hiroshi
To use :: trigger for LEDs, enable PHY LED trigger (CONFIG_LED_TRIGGER_PHY). Signed-off-by: INAGAKI Hiroshi --- target/linux/mvebu/cortexa9/config-5.15 | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/mvebu/cortexa9/config-5.15 b/target/linux/mvebu/cortexa9/config-5.15 index

[PATCH 0/2] mvebu: use PHY LED trigger "SPEED" LEDs on FortiGate 50E

2023-03-23 Thread INAGAKI Hiroshi
ed PHY LED trigger which can be used to indicate link speed (100M/1000M), so replace the default trigger to it. INAGAKI Hiroshi (2): mvebu: cortexa9: enable Ethernet PHY LED trigger mvebu: use PHY LED trigger for speed LEDs on FortiGate 50E .../mvebu/cortexa9/base-files/etc/board.d/01_le

[PATCH 2/2] mvebu: use PHY LED trigger for speed LEDs on FortiGate 50E

2023-03-23 Thread INAGAKI Hiroshi
Use :: trigger instead of netdev(link) trigger for Fortinet FortiGate 50E, to indicate link speed on the each phys. 1000 Mbps: Green 100 Mbps : Amber 10 Mbps : (turn off) Fixes: 102dc5a62506 ("mvebu: add support for Fortinet FortiGate 50E") Signed-off-by: INAGAKI Hiroshi ---

Re: [PATCH v2] mvebu: add support for Fortinet FortiGate 50E

2023-03-05 Thread INAGAKI Hiroshi
Hi Hauke, thank you for your review. On 2023/03/06 1:42, Hauke Mehrtens wrote: On 3/1/23 17:01, INAGAKI Hiroshi wrote: Fortinet FortiGate 50E (FG-50E) is a UTM, based on Armada 385 (88F6820). Notes: - All "SPEED" LEDs(Green/Amber) of LAN and 1000M "SPEED" LEDs

Re: [PATCH] mvebu: add support for Fortinet FortiGate 50E

2023-03-01 Thread INAGAKI Hiroshi
On 2023/03/02 0:29, INAGAKI Hiroshi wrote: Fortinet FortiGate 50E (FG-50E) is a UTM, based on Armada 385 (88F6820). Specification: - SoC : Marvell Armada 385 88F6820 - RAM : DDR3 2 GiB (Micron MT41K512M8DA-107, "D9SGQ") - Flash: SPI-NOR 128 MiB

[PATCH v2] mvebu: add support for Fortinet FortiGate 50E

2023-03-01 Thread INAGAKI Hiroshi
: ? *: required for initramfs image MAC addresses: (eth0): 70:4C:A5:xx:xx:7C (board-info, 0xd880 (hex)) WAN 1 : 70:4C:A5:xx:xx:7D WAN 2 : 70:4C:A5:xx:xx:7E LAN 1 : 70:4C:A5:xx:xx:7F LAN 2 : 70:4C:A5:xx:xx:80 LAN 3 : 70:4C:A5:xx:xx:81 LAN 4 : 70:4C:A5:xx:xx:82 LAN 5 : 70:4C:A5:xx:xx:83 Signed-off

[PATCH] mvebu: add support for Fortinet FortiGate 50E

2023-03-01 Thread INAGAKI Hiroshi
0): 70:4C:A5:xx:xx:7C (board-info, 0xd880 (hex)) WAN 1 : 70:4C:A5:xx:xx:7D WAN 2 : 70:4C:A5:xx:xx:7E LAN 1 : 70:4C:A5:xx:xx:7F LAN 2 : 70:4C:A5:xx:xx:80 LAN 3 : 70:4C:A5:xx:xx:81 LAN 4 : 70:4C:A5:xx:xx:82 LAN 5 : 70:4C:A5:xx:xx:83 Signed-off-by: INAGAKI Hiroshi --- .../bas

Re: [PATCH v2] mvebu: add support for Fortinet FortiGate 50E

2023-03-01 Thread INAGAKI Hiroshi
Hi Mark, On 2023/03/02 4:47, Mark Thurston wrote: On Wed, 01 Mar 2023 16:01:50 + INAGAKI Hiroshi wrote --- > Fortinet FortiGate 50E (FG-50E) is a UTM, based on Armada 385 (88F6820). > > Specification: > > - SoC : Marvell Armada 385 88

Re: [PATCH] mtdsplit_uimage: Split also after offsetted uImage

2024-01-26 Thread INAGAKI Hiroshi
Hello Linus, This is just a question: doesn't it work with "openwrt,offset" property of mtdsplit_uimage parser instead of modifying that parser? I'm thinking like the following: - dts: partition@1 {     compatible = "openwrt,uimage", "denx,uimage";     reg = <0x01 0xfe>;    

Re: Status of snapshot builds for omap target

2024-04-02 Thread INAGAKI Hiroshi
Hi Raylynn, omap target was disabled due to the VLAN issue on using cpsw-switch driver. see details: https://github.com/openwrt/openwrt/issues/11953 On 2024/04/02 13:52, Raylynn Knight via openwrt-devel wrote: The sender domain has a DMARC Reject/Quarantine policy which disallows sending

Re: Status of snapshot builds for omap target

2024-04-08 Thread INAGAKI Hiroshi
Hi Raylynn, sorry for late reply. From my understanding... On 2024/04/05 4:42, Raylynn Knight via openwrt-devel wrote: If I understand the issue correctly then it does not affect two of the four currently supported devices (i.e. it only affects Beaglebone Black and AM335x EVM and not

Re: [PATCH] realtek/rtl839x: Edgecore ECS4100-12PH support

2024-04-04 Thread INAGAKI Hiroshi
Hi stijn, I have some comments below. On 2024/04/04 23:28, st...@linux-ipv6.be wrote: Add support for the Edgecore ECS4100-12PH, an 8-port PoE Gigabit Ethernet switch with 2 combo RJ45/SFP and 2 SFP ports. Hardware: * SoC: RTL8392M * RAM: 256MiB * Flash: 32MiB SPI-NOR * Ethernet: * 8x GbE

Re: Status of snapshot builds for omap target

2024-04-16 Thread INAGAKI Hiroshi
Hi Raylynn, On 2024/04/11 15:57, Raylynn Knight wrote: Hiroshi, I’m late responding also so no problem. On Apr 8, 2024, at 9:48 PM, INAGAKI Hiroshi wrote: Hi Raylynn, sorry for late reply. From my understanding... On 2024/04/05 4:42, Raylynn Knight via openwrt-devel wrote: If I