aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/x86/64
Commit message (Collapse)AuthorAgeFilesLines
* treewide: remove files for building 5.10 kernelNick Hainke2023-05-121-510/+0
| | | | | | | | | | | All targets are bumped to 5.15. Remove the old 5.10 patches, configs and files using: find target/linux -iname '*-5.10' -exec rm -r {} \; Further, remove the 5.10 include. Signed-off-by: Nick Hainke <vincent@systemli.org>
* kernel: Move CONFIG_DRM_XEN_FRONTEND to generic configurationHauke Mehrtens2022-12-231-1/+0
| | | | | | | The CONFIG_DRM_XEN_FRONTEND configuration symbol is also used by the layerscape target, move it to the generic kernel configuration. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: enable PINCTRL for all Intel platformXiaopo Zhang2022-11-202-13/+13
| | | | | | Enable Intel PINCTRL for all platform on both 32 bit and 64 bit target. Signed-off-by: Xiaopo Zhang <xiaopoz@proton.me>
* x86/64: enable Intel PINCTRL in 64bit targetXiaopo Zhang2022-11-202-14/+16
| | | | | | | | | | | | Intel PINCTRL is not enable in the 64bit build, while it is enabled in the x86/general target, which disables the ability of controlling GPIO in the 64 bit build. This commit copies the corresponding part of x86/general config, since it is already there, so it should be fine to enable the same settings here. Signed-off-by: Xiaopo Zhang <xiaopoz@proton.me>
* kernel: Move some IOMMU options to genericHauke Mehrtens2022-09-242-4/+1
| | | | | | | | | | | | This adds some missing IOMMU related options for x86/64 and moves some of them to generic for all targets. On x86 IOMMU_DEFAULT_DMA_LAZY is used by default, on all other platforms IOMMU_DEFAULT_DMA_STRICT is the default. we just follow the default kernel configuration here. Fixes: 8fea4a102ccd ("x86/64: enable IOMMU support") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86/64: enable IOMMU supportNicola Corna2022-09-212-0/+38
| | | | | | | | | | | Enable IOMMU support for Intel and AMD x86 platforms. With this, when the vfio module is present, physical PCI devices can be passed to VMs, for example with `qemu-system-x86_64 -device vfio-pci,host=05:00.0 ...`. IOMMU support increases the kernel size by a small amount (~370KB, from 5239840 B to 5611200 B, a ~7% increase in size). Signed-off-by: Nicola Corna <nicola@corna.info>
* kernel: Activate CONFIG_GPIOLIB in generic configurationHauke Mehrtens2022-08-102-2/+0
| | | | | | | | All targets expect the malta target already activate the CONFIG_GPIOLIB option. Move it to generic kernel configuration and also activate it for malta. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: 5.15: x86-64: enable CONFIG_SLSRui Salvaterra2022-06-271-0/+1
| | | | | | | | Starting with GCC 12, we have the possibility of mitigating straight-line speculation vulnerabilities in x86-64 targets. Make it so. Reported-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* generic: enable CRYPTO_LIB_BLAKE2S[_X86|_ARM]Tomasz Maciej Nowak2022-06-242-0/+4
| | | | | | | | | | | | This is now built-in, enable so it won't propagate on target configs. Link: https://lkml.org/lkml/2022/1/3/168 Fixes: 79e7a2552e89 ("kernel: bump 5.15 to 5.15.44") Fixes: 0ca93670693b ("kernel: bump 5.10 to 5.10.119") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (Link to Kernel's commit taht made it built-in, CRYPTO_LIB_BLAKE2S[_ARM|_X86] as it's selectable, 5.10 backport) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: update config for 5.15Petr Štetiar2022-03-291-9/+33
| | | | | | Refresh kernel config with `make kernel_oldconfig` make target. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: copy config and patches from 5.10 to 5.15Petr Štetiar2022-03-291-0/+491
| | | | | | | | | | | | | | So the upcoming changes needed for 5.15 can be reviewed easily. Removing following patches backported from 5.15: * 101-v5.15-mfd-lpc_ich-Enable-GPIO-driver-for-DH89xxCC.patch * 102-v5.15-platform-x86-add-meraki-mx100-platform-driver.patch Removed upstreamed patch `300-pcengines_apu1_led.patch` in commit 1b40faf7e4ab ("leds: apu: extend support for PC Engines APU1 with newer firmware") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: 5.10: consolidate mac80211 crypto optionsSergey Ryazanov2021-12-171-6/+0
| | | | | | | | | | | | | | | | | | | | | | Each of - CRYPTO_AEAD2 - CRYPTO_AEAD - CRYPTO_GF128MUL - CRYPTO_GHASH - CRYPTO_HASH2 - CRYPTO_HASH - CRYPTO_MANAGER2 - CRYPTO_MANAGER - CRYPTO_NULL2 either directly required for mac80211 crypto support, or directly selected by such options. Support for the mac80211 crypto was enabled in the generic config since c7182123b9 ("kernel: make cryptoapi support needed by mac80211 built-in"). So move the above options from the target configs to the generic config to make it clear why do we need them. CC: Felix Fietkau <nbd@nbd.name> Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* x86/64: enable MMIO_CMDLINE_DEVICES for firecracker supportPaul Spooren2021-10-121-0/+1
| | | | | | | | | | | | | This Kernel option allows to run OpenWrt witin a `firecracker` micro VM. Firecracker is a KVM-based tool for superfast booting VMs on x86_64 and aarch64. It makes rootfs available to the guest as a virtio-mmio device and passes its address via the kernel cmdline. A kernel without CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES will not recognize the rootfs virtio-mmio device. Suggested-by: Packet Please <pktpls@systemli.org> Signed-off-by: Paul Spooren <mail@aparcar.org>
* x86: remove obsolete Kernel 5.4Paul Spooren2021-10-021-501/+0
| | | | | | | With the upgrade to Kernel 5.10 per default the old version is no longer required to be in tree. Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: move two symbols to the generic kconfigsRui Salvaterra2021-08-292-4/+0
| | | | | | | CONFIG_RCU_{NEED_SEGCBLIST,STALL_COMMON} are set basically everywhere. Move them to the generic kconfigs. And resort the generic kconfigs while at it. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* treewide: add various missing config symbolsDavid Bauer2021-08-101-1/+0
| | | | | | Fixes commit 91a52f22a13d ("treewide: backport support for nvmem on non platform devices") Signed-off-by: David Bauer <mail@david-bauer.net>
* x86: kernel: set NR_CPUS to 512Edgar Su2021-07-182-4/+4
| | | | | | | | | | NR_CPUS limits the number of CPUs supported to 8. This makes total sense on hardware-restircted platforms, but not on x86_64, where CPUs with more than 8 cores can be easily acquired and with less physical limitaions. see also: https://forum.openwrt.org/t/x86-64-8-cpu-limitation-on-vanilla-release/100946 Signed-off-by: Edgar Su <sjs333@outlook.com>
* x86: kernel: enable Fusion-MPT SAS driverMark Carroll2021-06-062-0/+2
| | | | | | | Compile in MPT SAS driver required to mount rootfs on some VMWare systems (e.g. required for 1&1 IONOS). Signed-off-by: Mark Carroll <git@markcarroll.net>
* kernel: add missing config symbols, fix typosTony Ambardar2021-03-191-2/+0
| | | | | | | | | | Update 5.10 generic config to add missing options prompting during builds, when setting CONFIG_ALL_KMODS. Refresh the x86 subtargets to drop symbols added to the generic config. Also fix a typo in 5.4/5.10 generic configs: "CONFIG_CONFIG_KVM_AMD_SEV". Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* kernel: move some disabled symbols to genericAleksander Jan Bajkowski2021-03-192-4/+0
| | | | | | Move some disabled symbols found in armvirt target to generic. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* x86: support kernel 5.10Tony Ambardar2021-03-141-0/+501
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add linux 5.10 as testing kernel, copy generic/subtarget configs and target patches from 5.4. Signed-off-by: Tony Ambardar <itugrok@yahoo.com> x86: update target patches for kernel 5.10 Refresh all patches while also dropping: 800-hwmon-w83627ehf-dont-claim-nct677x.patch which is now upstreamed as: 3207408ab4cb ("hwmon: (w83627ehf) remove nct6775 and nct6776 support") Signed-off-by: Tony Ambardar <itugrok@yahoo.com> x86: refresh 5.10 target config Refresh config using "make kernel_oldconfig". Signed-off-by: Tony Ambardar <itugrok@yahoo.com> x86: refresh and test all subtarget configs Refresh configs using "make kernel_oldconfig CONFIG_TARGET=subtarget". Build and run-tested using QEMU: x86/64, x86/legacy, x86/generic. Build-tested only: x86/geode. Signed-off-by: Tony Ambardar <itugrok@yahoo.com> [squashed commits] Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* x86: add support for AWS T3 instancesAlberto Bursi2021-03-011-0/+1
| | | | | | | | | | | | | | | | | 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>
* x86: enable CONFIG_MMC_SDHCI_ACPI for x86_64Mengyang Li2020-12-031-0/+2
| | | | | | | | | | | | | | | | | | | | | Some x86_64 single board computer (including Atomic Pi) has onboard emmc, but requires CONFIG_MMC_SDHCI_ACPI driver to use or boot from it. Here is boot message for the mmc device [ 2.838008] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 2.857536] mmc1: SDHCI controller on ACPI [80860F14:01] using ADMA [ 2.950019] mmc0: new HS200 MMC card at address 0001 [ 3.158271] mmcblk0: mmc0:0001 M52516 14.6 GiB [ 3.170290] mmcblk0boot0: mmc0:0001 M52516 partition 1 4.00 MiB [ 3.177191] mmcblk0boot1: mmc0:0001 M52516 partition 2 4.00 MiB [ 3.183963] mmcblk0rpmb: mmc0:0001 M52516 partition 3 4.00 MiB, \ chardev (248:0) Other lines changed in this config file are introduced by menuconfig. Signed-off-by: Mengyang Li <mayli.he@gmail.com>
* kernel: remove support for kernel 4.19Adrian Schmutzler2020-10-301-516/+0
| | | | | | | We use 5.4 on all targets by default, and 4.19 has never been released in a stable version. There is no reason to keep it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: Move CONFIG_IONIC to generic kernel configHauke Mehrtens2020-08-101-1/+0
| | | | | | | It is deactivated everywhere, just set this in the generic config. Acked-by: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: unify CONFIG_GPIO_SYSFS in kernel configsFelix Fietkau2020-08-062-2/+0
| | | | | | Enable it for all platforms Signed-off-by: Felix Fietkau <nbd@nbd.name>
* treewide: drop shebang from non-executable target filesAdrian Schmutzler2020-06-161-1/+0
| | | | | | | | | | | | | | This drops the shebang from all target files for /lib and /etc/uci-defaults folders, as these are sourced and the shebang is useless. While at it, fix the executable flag on a few of these files. This does not touch ar71xx, as this target is just used for backporting now and applying cosmetic changes would just complicate things. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: add gpio-it87Florian Eckert2020-06-032-2/+2
| | | | | | | | | | | | | | | Since commit 910df3f06cc902ca2cb0ca8e963e9354c930df1a we have build in on all X86/64 platforms the gpio-it87 driver. Since this change I am getting the following error message on boot. > kern.err kernel: [ 1.009416] gpio_it87: no device I do not have this device on my system. To prevent the nonsensical message and the loading of the module I have added this as a package, so that it can be installed later or during image building. Signed-off-by: Florian Eckert <fe@dev.tdt.de> Reviewed-by: Philip Prindeville <philipp@redfish-solutions.com>
* x86: fix generic kernel 5.4 configAlberto Bursi2020-05-201-12/+0
| | | | | | | | | | | | | | The last kernel update done with commit 500a02bc29b9 ("x86: Update configuration") placed most of the updated config only in the x86_64 target. Move the options needed by the other targets too in the x86 base config, and add an additional option needed by those targets. Fixes: 500a02bc29b9 ("x86: Update configuration") Signed-off-by: Alberto Bursi <bobafetthotmail@gmail.com> [commit subject/description tweaks] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: move packages selection to profilesTomasz Maciej Nowak2020-04-201-2/+0
| | | | | | | | | | This can be rather confusing for contributors, since there are three layers in which they can be added. As for now there are none profiles other than generic (exception: geos) let's move them to these profiles. Being here this commit also removes packages in geode profiles already enabled in kernel config. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: select kmod-button-hotplug by defaultTomasz Maciej Nowak2020-04-201-2/+2
| | | | | | | This package is useful by all subtargets, therefore move it to default packages selection. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: fix kmod-forcedeth package selectionTomasz Maciej Nowak2020-04-201-1/+1
| | | | | | | | There's no such package as forcedeth, threfore the driver is never selected. Fix it by properly specifying package name. Fixes: 35f208d ("x86: add nforce eth to default packages") Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: add nforce eth to default packagesAlberto Bursi2020-04-131-1/+2
| | | | | | | | | | | | | forcedeth is necessary to use the integrated ethernet controller of Nvidia nForce chipset. There are PC motherboards with this chipset from 2001 that run 32bit Athlon XP CPUs and more modern ones up to 2009 that can run Intel and AMD 64bit processors, so add this to all non-geode x86 targets. Signed-off-by: Alberto Bursi <bobafetthotmail@gmail.com>
* x86/64: add cdrom and iso9660 drivers李国2020-03-312-0/+8
| | | | | | | The iso image need cdrom and iso9660 drivers to boot, otherwise it will hang when mounting the root file system Signed-off-by: 李国 <uxgood.org@gmail.com>
* x86: remove obsolete legacy profilesPaul Spooren2020-03-211-15/+0
| | | | | | | | Rely on device profiles instead for packages selection. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [rebase, adjusted commit title] Signed-off-by: Paul Spooren <mail@aparcar.org>
* x86: Remove kernel 4.14 supportHauke Mehrtens2020-03-121-487/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: x86_64: drop CALGARY IOMMU on 5.4Kevin Darbyshire-Bryant2020-03-021-2/+2
| | | | | | It's snuck back in on kernel 5.4 configs, so drop it there too. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* treewide: move commonly disabled symbols to generic configDavid Bauer2020-03-011-1/+0
| | | | | | | Move new commonly disabled kernel 5.4 symbols to the generic kernel configuration. Signed-off-by: David Bauer <mail@david-bauer.net>
* x86: Update configurationHauke Mehrtens2020-02-281-43/+43
| | | | | | | The configuration was refreshed and KERNEL_TESTING_PATCHVER was set to make it easy to compile for kernel 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: copy kernel patches from 4.19 to 5.4Hauke Mehrtens2020-02-281-0/+513
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: x86_64: drop CALGARY properlyKevin Darbyshire-Bryant2020-02-251-2/+2
| | | | | | | Use correct config syntax of 'is not set' instead of just commenting the line Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: x86_64: drop CALGARY IOMMUKevin Darbyshire-Bryant2020-02-251-2/+2
| | | | | | | | | | | | The calgary IOMMU was only used on high-end IBM systems in the early x86_64 age. This is an unlikely OpenWrt target and in fact upstream are looking to drop the driver entirely with the bonus that we no longer see: [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing! Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* x86: delete empty Makefile introduced by accidentAdrian Schmutzler2019-11-041-0/+0
| | | | | | | | | When changing profile titles for this target, an empty Makefile has been added by accident. Fixes: 14d17306bc73 ("x86: make profile titles more verbose") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* x86: make profile titles more verbosePaul Spooren2019-11-032-3/+3
| | | | | | | | | | | | | | | | So far (nearly) all x86 profiles are called "Generic" which makes it hard to distinguish them in special cases, like searching for a specific profile (without pre-selecting target/subtarget). To make this change locally working, remove the tmp/ folder to force reload of menuconfig. As these files are infrequently touched, the Copyright was updated as well. Signed-off-by: Paul Spooren <mail@aparcar.org> [changed commit title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 4.19 to 4.19.67Koen Vandeputte2019-08-271-0/+1
| | | | | | | | | | | | Refreshed all patches. Also add a missing symbol for x86 which got used now in this bump. - ISCSI_IBFT Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.139Koen Vandeputte2019-08-271-0/+1
| | | | | | | | | | | | Refreshed all patches. Also add a missing symbol for x86 which got used now in this bump. - ISCSI_IBFT Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: x86: enable NVME support for 64 bit targetLucian Cristian2019-07-092-0/+3
| | | | | | | | Newer motherboards support NVMe U.2 connectors but also NVMe storage can be used on add-on pcie adapters. Enable kernel driver on x86 for now so the NVMe flash storage can be used Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* x86: video: disable buildtin amdgpu DRM driverLucian Cristian2019-02-172-2/+2
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* x86: DRM: add x64 subtarget supportLucian Cristian2019-02-172-4/+117
| | | | | | copy settings from generic subtarget Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* x86: Add support for kernel 4.19Hauke Mehrtens2019-01-121-0/+449
| | | | | | | | | | | | This adds initial support for kernel 4.19 to the x86 target. The patches and the kernel configurations were copied from kernel 4.14 and then refreshed. The legacy and the genode target will not support PAE any more because they use a CPU type which does not support PAE, the generic sub target still supports PAE. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>