gluon/targets/x86.inc

config('CONFIG_VDI_IMAGES', true)
config('CONFIG_VMDK_IMAGES', true)

packages {
	'kmod-3c59x',
	'kmod-8139cp',
	'kmod-8139too',
	'kmod-e100',
	'kmod-e1000',
	'kmod-e1000e',
	'kmod-forcedeth',
	'kmod-igb',
	'kmod-natsemi',
	'kmod-ne2k-pci',
	'kmod-pcnet32',
	'kmod-r8169',
	'kmod-sis900',
	'kmod-sky2',
	'kmod-tg3',
	'kmod-tulip',
	'kmod-via-rhine',
	'kmod-via-velocity',
	'kmod-ath9k',
	'kmod-gpio-button-hotplug',
	'kmod-gpio-nct5104d',
	'kmod-hwmon-core',
	'kmod-leds-gpio',
	'kmod-leds-apu2',
	'kmod-sp5100_tco',
	'kmod-usb-core',
	'kmod-usb-ohci',
	'kmod-usb2',
	'kmod-usb3',
	'kmod-usb-serial',
	'kmod-ath10k',
	'ath10k-firmware-qca9887',
	'ath10k-firmware-qca9888',
	'ath10k-firmware-qca988x',
	'ath10k-firmware-qca9984',
	'kmod-mt76x0e',
	'kmod-mt76x2',
	'kmod-mt7603',
	'kmod-mt7615e',
}
build: rework config generation So far, we were using a sort operation on the generated .config to implement precedence of =y packages over =m, and =m over unset. Unfortunately, this sort not only used for packages, but for all config lines. This made it impossible to override settings from targets/generic in a target config when the new setting was sorted before the generic setting. To fix this, track configurations by their keys, so we can properly override config keys that were set before. Value-based precedence is only preserved for package configuration. The config() and try_config() calls always take key and value as separate arguments now. Strings are quoted automatically; the values true, nil and false map to y, m and unset for tristate options. config() can take an optional third argument to override the error message to display when the setting fails to apply. All existing target configs generate the same .config with the old and the new code. The new code is also a bit faster on targets with many devices. 2020-05-26 20:40:12 +00:00			`config('CONFIG_VDI_IMAGES', true)`
			`config('CONFIG_VMDK_IMAGES', true)`
x86: move common parts of x86-generic and x86-64 to include file 2018-04-26 20:59:36 +00:00
Switch to Lua for target definitions The old bash-based parsing code was way too complex. Replace it with Lua. 2019-06-14 17:20:15 +00:00			`packages {`
			`'kmod-3c59x',`
			`'kmod-8139cp',`
			`'kmod-8139too',`
			`'kmod-e100',`
			`'kmod-e1000',`
			`'kmod-e1000e',`
			`'kmod-forcedeth',`
			`'kmod-igb',`
			`'kmod-natsemi',`
			`'kmod-ne2k-pci',`
			`'kmod-pcnet32',`
			`'kmod-r8169',`
			`'kmod-sis900',`
			`'kmod-sky2',`
			`'kmod-tg3',`
			`'kmod-tulip',`
			`'kmod-via-rhine',`
			`'kmod-via-velocity',`
			`'kmod-ath9k',`
			`'kmod-gpio-button-hotplug',`
			`'kmod-gpio-nct5104d',`
			`'kmod-hwmon-core',`
			`'kmod-leds-gpio',`
			`'kmod-leds-apu2',`
			`'kmod-sp5100_tco',`
			`'kmod-usb-core',`
			`'kmod-usb-ohci',`
			`'kmod-usb2',`
			`'kmod-usb3',`
			`'kmod-usb-serial',`
x86: switch to non-CT ath10k module It seems the CT variant was used for 11s meshing on x86 by accient. Switch to non-CT to match the other targets. 2019-11-07 18:45:56 +00:00			`'kmod-ath10k',`
build: drop GLUON_WLAN_MESH variable 2019-11-05 19:49:55 +00:00			`'ath10k-firmware-qca9887',`
x86: add common wireless packages (#1947) 2020-03-23 18:00:28 +00:00			`'ath10k-firmware-qca9888',`
build: drop GLUON_WLAN_MESH variable 2019-11-05 19:49:55 +00:00			`'ath10k-firmware-qca988x',`
x86: add common wireless packages (#1947) 2020-03-23 18:00:28 +00:00			`'ath10k-firmware-qca9984',`
			`'kmod-mt76x0e',`
			`'kmod-mt76x2',`
			`'kmod-mt7603',`
			`'kmod-mt7615e',`
Switch to Lua for target definitions The old bash-based parsing code was way too complex. Replace it with Lua. 2019-06-14 17:20:15 +00:00			`}`