[PATCH v2] mvebu: add support for Fortinet FortiGate 50E
Hauke Mehrtens
hauke at hauke-m.de
Sun Mar 5 08:42:53 PST 2023
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(Green) of
> WAN1/2 are connected to GPIO expander. There is no way to indicate
> link speed of networking device, so those LEDs cannot be used like
> stock firmware.
I think you can use the ledtrig-netdev to activate the LEDs on link up
if they are connected to the nxp,pca9555 GPIO extender.
> - Both colors of Bi-color LEDs on the front panel cannot be turned on at
> the same time.
>
> - "PWR" and "Logo" LEDs are connected to power source directory.
>
> - The following partitions are added for OpenWrt.
> These partitions are contained in "uboot" partition (0x0-0x1fffff) on
> stock firmware.
>
> - "firmware-info"
> - "dtb"
> - "u-boot-env"
> - "board-info"
>
.....
>
> +define Device/fortinet_fg-50e
> + DEVICE_VENDOR := Fortinet
> + DEVICE_MODEL := FortiGate 50E
> + SOC := armada-385
> + KERNEL := kernel-bin | append-dtb
> + KERNEL_INITRAMFS := kernel-bin | append-dtb | fortigate-header | \
> + gzip-filename FGT50E
> + KERNEL_SIZE := 6144k
> + DEVICE_DTS := armada-385-fortinet-fg-50e
> + IMAGE/sysupgrade.bin := append-rootfs | pad-rootfs | \
> + sysupgrade-tar rootfs=$$$$@ | append-metadata
> + DEVICE_PACKAGES := kmod-hwmon-nct7802
Why don't you add the driver for the GPIO extender kmod-gpio-pca953x here?
> +endef
> +TARGET_DEVICES += fortinet_fg-50e
> +
> define Device/globalscale_mirabox
> $(Device/NAND-512K)
> DEVICE_VENDOR := Globalscale
More information about the openwrt-devel
mailing list