Re: [PATCH] octeontx: kernel: add USB storage boot support
On Thu, Feb 23, 2023 at 3:23 PM Tim Harvey wrote: > > Enable BLK_DEV_SD and USB_STORAGE so that rootfs can be on a USB Mass > Storage device. > > This increases the kernel Image by 66KiB > > Signed-off-by: Tim Harvey > --- > target/linux/octeontx/config-5.15 | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/target/linux/octeontx/config-5.15 > b/target/linux/octeontx/config-5.15 > index 40cab28f60a0..c2ad7e7ab9d7 100644 > --- a/target/linux/octeontx/config-5.15 > +++ b/target/linux/octeontx/config-5.15 > @@ -59,6 +59,7 @@ CONFIG_BLK_DEV_BSG=y > CONFIG_BLK_DEV_BSGLIB=y > CONFIG_BLK_DEV_BSG_COMMON=y > CONFIG_BLK_DEV_LOOP=y > +CONFIG_BLK_DEV_SD=y > CONFIG_BLK_MQ_PCI=y > CONFIG_BLK_MQ_VIRTIO=y > CONFIG_BLK_PM=y > @@ -401,6 +402,7 @@ CONFIG_UNMAP_KERNEL_AT_EL0=y > CONFIG_USB=y > CONFIG_USB_COMMON=y > CONFIG_USB_PCI=y > +CONFIG_USB_STORAGE=y > CONFIG_USB_SUPPORT=y > # CONFIG_USB_UHCI_HCD is not set > CONFIG_USB_XHCI_HCD=y > -- > 2.25.1 > Any additional comments or discussion on this? CONFIG_BLK_DEV_SD=y is required to allow OpenWrt's rootfs on a SCSI block device such as mSATA. CONFIG_USB_STORAGE=y is required additionally to allow OpenWrt's rootfs on a USB mass storage device. Both cases are useful if for example the bootloader is on different boot device than OpenWrt's rootfs. This differs from enabling USB mass storage via kmod-usb-storage as that gets loaded as a module after OpenWrt's rootfs is mounted. This seems like a relatively small increase in kernel size for the functionality. Best Regards, Tim ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
OpenWrt @ Battlemesh
Hi, Wireless Battlemesh v15 is coming up in May 8-14. https://battlemesh.org/BattleMeshV15 Battlemesh will take place this year in Calafou, Vallbona d'Anoia, Barcelona. We were thinking to do a OpenWrt meeting in parallel or before/after Battlemesh. I would like to know if it makes sense to organize an OpenWrt meeting at Battelmesh or before/after Battlemesh. I think we have 3 options. OpenWrt meetup at 7 and 8 of May. OpenWrt meetup at 14 and 15 of May. OpenWrt meetup sometime between 8 and 14 of May. If someone wants to do presentations or workshops we can do this also as part of the Battlemesh and offer it to everyone joining Battlemesh too. The main purpose of such a meetup would be to to align on some strategies on what to do next in OpenWrt and how to do it from my point of view. The advantage of doing it around Battlemesh is that we have to organize less ourselves. What do you think about this plan? Who would join such a meetup? Sorry for delaying this so much. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] kernel: modules: package Microchip LAN743x PCIe gigE driver
Package the Microchip LAN743x PCIe gigE driver Signed-off-by: Tim Harvey --- package/kernel/linux/modules/netdevices.mk | 16 1 file changed, 16 insertions(+) diff --git a/package/kernel/linux/modules/netdevices.mk b/package/kernel/linux/modules/netdevices.mk index 248aaf06f7e8..acab054b0b88 100644 --- a/package/kernel/linux/modules/netdevices.mk +++ b/package/kernel/linux/modules/netdevices.mk @@ -1523,3 +1523,19 @@ endef $(eval $(call KernelPackage,atlantic)) + +define KernelPackage/lan743x + SUBMENU:=$(NETWORK_DEVICES_MENU) + TITLE:=Microchip LAN743x PCI Express Gigabit Ethernet NIC + DEPENDS:=@PCI_SUPPORT + KCONFIG:=CONFIG_LAN743X + FILES:=$(LINUX_DIR)/drivers/net/ethernet/microchip/lan743x.ko + AUTOLOAD:=$(call AutoProbe,lan743x) +endef + +define KernelPackage/lan743x/description + Kernel module for Microchip LAN743x PCI Express Gigabit Ethernet NIC +endef + +$(eval $(call KernelPackage,lan743x)) + -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
