mirror
/
openwrt
mirror of https://git.openwrt.org/openwrt/openwrt.git
1
0
Fork 0
Code Releases Activity
openwrt/target/linux/x86/modules.mk

105 lines
3.1 KiB
Makefile
Raw Normal View History

target: use SPDX license identifiers on Makefiles Use SPDX license tags to allow machines to check licenses. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2021-02-10 14:52:34 +01:00
# SPDX-License-Identifier: GPL-2.0-only
x86: add kernel module for AMD CS5535/CS5536 audio chipset Add support for the integrated AC97 sound device on motherboards with AMD CS5535/CS5536 chipsets. Tested on Wyse Winterm S30. Signed-off-by: Cezary Jackiewicz <cezary@eko.one.pl>
2017-01-04 18:51:35 +01:00
#
# Copyright (C) 2017 Cezary Jackiewicz <cezary@eko.one.pll>
x86: add support for AWS T3 instances Amazon AWS T3 cloud instances require kernel support for the Elastic Fabric Adapter to access storage and for Elastic Network Adapter to use network interfaces. Since the Fabric Adapter is needed to access root filesystem, enable in x86_64 kernel. Elastic Network Adapter goes in a module, and add this module to default list in x86_64. The module is set to AutoLoad because AutoProbe does not seem to load it. Signed-off-by: Alberto Bursi <bobafetthotmail@gmail.com>
2021-02-06 20:25:32 +01:00
define KernelPackage/amazon-ena
SUBMENU:=$(NETWORK_DEVICES_MENU)
TITLE:=Elastic Network Adapter (for Amazon AWS T3)
DEPENDS:=@TARGET_x86_64
KCONFIG:=CONFIG_ENA_ETHERNET
FILES:=$(LINUX_DIR)/drivers/net/ethernet/amazon/ena/ena.ko
AUTOLOAD:=$(call AutoLoad,12,ena)
endef
define KernelPackage/amazon-ena/description
This driver supports Elastic Network Adapter (ENA)
used by Amazon AWS T3 instances.
endef
$(eval $(call KernelPackage,amazon-ena))
x86/64: Add support for AMD SOC Ethernet controller This feature is already supported in kernel. Add definition and configuration in Makefile of OpenWRT. It is tested on board Dibbler with processor V1605B. Dmesg is as below. -------------------------------------------- [ 0.317122] smpboot: CPU0: AMD Ryzen Embedded V1605B with Radeon Vega Gfx (family: 0x17, model: 0x11, stepping: 0x0) [ 8.227270] libphy: amd-xgbe-mii: probed [ 8.228189] amd-xgbe 0000:02:00.1 eth0: net device enabled [ 8.228999] libphy: amd-xgbe-mii: probed [ 8.229921] amd-xgbe 0000:02:00.2 eth1: net device enabled ..... [ 11.760869] br-lan: port 1(eth0) entered blocking state [ 11.761365] br-lan: port 1(eth0) entered disabled state [ 11.762019] device eth0 entered promiscuous mode [ 11.785285] 8021q: adding VLAN 0 to HW filter on device eth1 [ 16.881431] amd-xgbe 0000:02:00.1 eth0: Link is Up - 1Gbps/Full - flow control off [ 16.882108] br-lan: port 1(eth0) entered blocking state [ 16.882583] br-lan: port 1(eth0) entered forwarding state [ 16.883249] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready ----------------------------------------------- Signed-off-by: Zheng Bao <fishbaozi@gmail.com>
2021-04-13 06:46:17 +02:00
define KernelPackage/amd-xgbe
SUBMENU:=$(NETWORK_DEVICES_MENU)
TITLE:=AMD Ethernet on SoC support
x86: amd-xgbe: add missing dependencies on 5.10 fix the following build error when building with test kernel: Package kmod-amd-xgbe is missing dependencies for the following libraries: mdio_devres.ko Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
2021-04-18 12:05:08 +02:00
DEPENDS:=@PCI_SUPPORT @TARGET_x86_64 +kmod-lib-crc32c +kmod-ptp +kmod-libphy +LINUX_5_10:kmod-mdio-devres
x86/64: Add support for AMD SOC Ethernet controller This feature is already supported in kernel. Add definition and configuration in Makefile of OpenWRT. It is tested on board Dibbler with processor V1605B. Dmesg is as below. -------------------------------------------- [ 0.317122] smpboot: CPU0: AMD Ryzen Embedded V1605B with Radeon Vega Gfx (family: 0x17, model: 0x11, stepping: 0x0) [ 8.227270] libphy: amd-xgbe-mii: probed [ 8.228189] amd-xgbe 0000:02:00.1 eth0: net device enabled [ 8.228999] libphy: amd-xgbe-mii: probed [ 8.229921] amd-xgbe 0000:02:00.2 eth1: net device enabled ..... [ 11.760869] br-lan: port 1(eth0) entered blocking state [ 11.761365] br-lan: port 1(eth0) entered disabled state [ 11.762019] device eth0 entered promiscuous mode [ 11.785285] 8021q: adding VLAN 0 to HW filter on device eth1 [ 16.881431] amd-xgbe 0000:02:00.1 eth0: Link is Up - 1Gbps/Full - flow control off [ 16.882108] br-lan: port 1(eth0) entered blocking state [ 16.882583] br-lan: port 1(eth0) entered forwarding state [ 16.883249] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready ----------------------------------------------- Signed-off-by: Zheng Bao <fishbaozi@gmail.com>
2021-04-13 06:46:17 +02:00
KCONFIG:=CONFIG_AMD_XGBE
FILES:=$(LINUX_DIR)/drivers/net/ethernet/amd/xgbe/amd-xgbe.ko
AUTOLOAD:=$(call AutoLoad,35,amd-xgbe)
endef
define KernelPackage/amd-xgbe/description
Kernel modules for AMD 10GbE Ethernet device on an AMD SoC.
endef
$(eval $(call KernelPackage,amd-xgbe))
x86: add kernel module for AMD CS5535/CS5536 audio chipset Add support for the integrated AC97 sound device on motherboards with AMD CS5535/CS5536 chipsets. Tested on Wyse Winterm S30. Signed-off-by: Cezary Jackiewicz <cezary@eko.one.pl>
2017-01-04 18:51:35 +01:00
define KernelPackage/sound-cs5535audio
TITLE:=CS5535/CS5536 Audio Controller
DEPENDS:=@TARGET_x86_geode +kmod-ac97
KCONFIG:=CONFIG_SND_CS5535AUDIO
FILES:=$(LINUX_DIR)/sound/pci/cs5535audio/snd-cs5535audio.ko
AUTOLOAD:=$(call AutoLoad,36,snd-cs5535audio)
$(call AddDepends/sound)
endef
define KernelPackage/sound-cs5535audio/description
Support for the integrated AC97 sound device on motherboards
with AMD CS5535/CS5536 chipsets.
endef
$(eval $(call KernelPackage,sound-cs5535audio))
x86: add kernel module for sp5100_tco watchdog This change adds the sp5100_tco driver as a kernel module for the x86 target. Specifically, this can be used by the PCEngines APU2/APU3. The reason for having this as a kernel module is to allow users to load/unload it on demand, as the I2C interface on the APU2/APU3 will not work while this module is loaded. More info can be found on GitHub at https://github.com/riptidewave93/LEDE-APU2/pull/5#issuecomment-255667736 Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2017-01-14 17:20:25 +01:00
x86: avoid underscore in package name As 07e1d88d7beb ("kernel: avoid underscore in *6lowpan package names") shows, underscores might cause build failures. Replace underscore with dash. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
2020-02-23 05:05:35 +01:00
define KernelPackage/sp5100-tco
x86: add kernel module for sp5100_tco watchdog This change adds the sp5100_tco driver as a kernel module for the x86 target. Specifically, this can be used by the PCEngines APU2/APU3. The reason for having this as a kernel module is to allow users to load/unload it on demand, as the I2C interface on the APU2/APU3 will not work while this module is loaded. More info can be found on GitHub at https://github.com/riptidewave93/LEDE-APU2/pull/5#issuecomment-255667736 Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2017-01-14 17:20:25 +01:00
SUBMENU:=$(OTHER_MENU)
TITLE:=SP5100 Watchdog Support
DEPENDS:=@TARGET_x86
KCONFIG:=CONFIG_SP5100_TCO
FILES:=$(LINUX_DIR)/drivers/watchdog/sp5100_tco.ko
AUTOLOAD:=$(call AutoLoad,50,sp5100_tco,1)
endef
x86: avoid underscore in package name As 07e1d88d7beb ("kernel: avoid underscore in *6lowpan package names") shows, underscores might cause build failures. Replace underscore with dash. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
2020-02-23 05:05:35 +01:00
define KernelPackage/sp5100-tco/description
x86: add kernel module for sp5100_tco watchdog This change adds the sp5100_tco driver as a kernel module for the x86 target. Specifically, this can be used by the PCEngines APU2/APU3. The reason for having this as a kernel module is to allow users to load/unload it on demand, as the I2C interface on the APU2/APU3 will not work while this module is loaded. More info can be found on GitHub at https://github.com/riptidewave93/LEDE-APU2/pull/5#issuecomment-255667736 Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2017-01-14 17:20:25 +01:00
Kernel module for the SP5100_TCO hardware watchdog.
endef
x86: avoid underscore in package name As 07e1d88d7beb ("kernel: avoid underscore in *6lowpan package names") shows, underscores might cause build failures. Replace underscore with dash. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
2020-02-23 05:05:35 +01:00
$(eval $(call KernelPackage,sp5100-tco))
kernel: add pcengines-apu2 module description Add a module description for the new pcengnies-apu2 device driver. This driver supports the front button and LEDs on the PC Engines APUv2/APUv3 boards. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
2019-07-02 12:04:58 +02:00
define KernelPackage/pcengines-apuv2
SUBMENU:=$(OTHER_MENU)
TITLE:=PC Engines APUv2/3 front button and LEDs driver
DEPENDS:=@TARGET_x86 +kmod-gpio-amd-fch +kmod-leds-gpio
KCONFIG:=CONFIG_PCENGINES_APU2
FILES:=$(LINUX_DIR)/drivers/platform/x86/pcengines-apuv2.ko
AUTOLOAD:=$(call AutoLoad,60,pcengines-apuv2)
endef
define KernelPackage/pcengines-apuv2/description
This driver provides support for the front button and LEDs on
PC Engines APUv2/APUv3 board.
endef
$(eval $(call KernelPackage,pcengines-apuv2))
x86: add support for Meraki MX100 This commit will add support for the Meraki MX100 in OpenWRT. Specs: * CPU: Intel Xeon E3-1200 Series 1.5GHz 2C/4T * Memory: 4GB DDR3 1600 ECC * Storage: 1GB USB NAND, 1TB SATA HDD * Wireless: None * Wired: 10x 1Gb RJ45, 2x 1Gb SFP UART: The UART header is named CONN11 and is found in the center of the mainboard. The pinout from Pin 1 (marked with a black triangle) to pin 4 is below: Pin 1: VCC Pin 2: TX Pin 3: RX Pin 4: GND Note that VCC is not required for UART on this device. Booting: 1. Flash/burn one of the images from this repo to a flash drive. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Hook up UART to the MX100, plug in the USB drive, and then power up the device. 4. At the BIOS prompt, quickly press F7 and then scroll to the Save & Exit tab. 5. Scroll down to Boot Override, and select the UEFI entry for your jumpdrive. Note: UEFI booting will fail if the SATA cable for the HDD is plugged in. The issue is explained under the Flashing instructions. Flashing: 1. Ensure the MX100 is powered down, and not plugged into power. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Using the Mini USB female port found by the SATA port on the motherboard, flash one of the images to the system. Example: `dd if=image of=/dev/sdb conv=fdatasync` where sdb is the USB device for the MX100's NAND. 4. Unplug the Mini USB, hook up UART to the MX100, and then power up the device. 5. At the BIOS prompt, quickly press F7 and then scroll to the Boot tab. 6. Change the boot order and set UEFI: USB DISK 2.0 as first, and USB DISK 2.0 as second. Disable the other boot options. 7. Go to Save & Exit, and then select Save Changes and Reset Note that OpenWRT will fail to boot in UEFI mode when the SATA hard drive is plugged in. To fix this, boot with the SATA disk unplugged and then run the following command: `sed -i "s|hd0,gpt1|hd1,gpt1|g" boot/grub/grub.cfg` Once the above is ran, OpenWRT will boot when the HDD is plugged into SATA. The reason this happens is the UEFI implementation for the MX100 will always set anything on SATA to HD0 instead of the onboard USB storage, so we have to accomidate it since OpenWRT's GRUB does not support detecting a boot disk via UUID. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2021-10-01 16:38:56 +02:00
define KernelPackage/meraki-mx100
SUBMENU:=$(OTHER_MENU)
TITLE:=Cisco Meraki MX100 Platform Driver
DEPENDS:=@TARGET_x86 @!LINUX_5_4 +kmod-tg3 +kmod-gpio-button-hotplug +kmod-leds-gpio \
Revert "gpio-cdev: add nu801 userspace driver" This reverts commit f536f5ebddd9c532a08ac4a9be3ef0c02f7bfeb8. As Hauke commented, this causes builder failures on 5.4 kernels. This revert includes changes to the mx100 kernel modules dependency as well as the uci led definitions. Tested-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
2021-10-10 22:06:51 +02:00
+kmod-usb-ledtrig-usbport +kmod-itco-wdt
x86: add support for Meraki MX100 This commit will add support for the Meraki MX100 in OpenWRT. Specs: * CPU: Intel Xeon E3-1200 Series 1.5GHz 2C/4T * Memory: 4GB DDR3 1600 ECC * Storage: 1GB USB NAND, 1TB SATA HDD * Wireless: None * Wired: 10x 1Gb RJ45, 2x 1Gb SFP UART: The UART header is named CONN11 and is found in the center of the mainboard. The pinout from Pin 1 (marked with a black triangle) to pin 4 is below: Pin 1: VCC Pin 2: TX Pin 3: RX Pin 4: GND Note that VCC is not required for UART on this device. Booting: 1. Flash/burn one of the images from this repo to a flash drive. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Hook up UART to the MX100, plug in the USB drive, and then power up the device. 4. At the BIOS prompt, quickly press F7 and then scroll to the Save & Exit tab. 5. Scroll down to Boot Override, and select the UEFI entry for your jumpdrive. Note: UEFI booting will fail if the SATA cable for the HDD is plugged in. The issue is explained under the Flashing instructions. Flashing: 1. Ensure the MX100 is powered down, and not plugged into power. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Using the Mini USB female port found by the SATA port on the motherboard, flash one of the images to the system. Example: `dd if=image of=/dev/sdb conv=fdatasync` where sdb is the USB device for the MX100's NAND. 4. Unplug the Mini USB, hook up UART to the MX100, and then power up the device. 5. At the BIOS prompt, quickly press F7 and then scroll to the Boot tab. 6. Change the boot order and set UEFI: USB DISK 2.0 as first, and USB DISK 2.0 as second. Disable the other boot options. 7. Go to Save & Exit, and then select Save Changes and Reset Note that OpenWRT will fail to boot in UEFI mode when the SATA hard drive is plugged in. To fix this, boot with the SATA disk unplugged and then run the following command: `sed -i "s|hd0,gpt1|hd1,gpt1|g" boot/grub/grub.cfg` Once the above is ran, OpenWRT will boot when the HDD is plugged into SATA. The reason this happens is the UEFI implementation for the MX100 will always set anything on SATA to HD0 instead of the onboard USB storage, so we have to accomidate it since OpenWRT's GRUB does not support detecting a boot disk via UUID. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2021-10-01 16:38:56 +02:00
KCONFIG:=CONFIG_MERAKI_MX100
FILES:=$(LINUX_DIR)/drivers/platform/x86/meraki-mx100.ko
AUTOLOAD:=$(call AutoLoad,60,meraki-mx100,1)
endef
define KernelPackage/meraki-mx100/description
This driver provides support for the front button and LEDs on
the Cisco Meraki MX100 (Tinkerbell) 1U appliance. Note this also
selects the gpio-cdev nu801 userspace driver to support the Status
LED, as well as other required platform drivers.
endef
$(eval $(call KernelPackage,meraki-mx100))