aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/x86/64
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* x86: Refresh kernel 4.14 configurationHauke Mehrtens2019-01-121-8/+5
| | | | | | | | | | | | This refreshes the kernel configuration for kernel 4.14. First this was run for the legacy target: make kernel_oldconfig Then for all targets including the legacy target this was run: make kernel_oldconfig CONFIG_TARGET=subtarget The option CONFIG_104_QUAD_8 was added to the generic configuration because it would have been automatically removed. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: Use kernel specific subtarget configurationsHauke Mehrtens2019-01-121-0/+0
| | | | | | | | | | This makes it possible to use different sub target configurations for kernel 4.19 for example. To support kernel 4.9 and kernel 4.14 with the same configuration file already needed some extra work this will not be needed for kernel 4.19 any more. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: enable kmod-bnx2 on 64-bit by defaultAlberto Bursi2019-01-021-1/+1
| | | | | | | Gigabit ethernet adapters using BCM5706/5708/5709/5716 chipset are common on servers and as easy/cheap to get as Intel based ones. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* kernel: enable memory compactionFelix Fietkau2018-10-091-0/+1
| | | | | | | | | | | Compaction is the only memory management component to form high order (larger physically contiguous) memory blocks reliably. The page allocator relies on compaction heavily and the lack of the feature can lead to unexpected OOM killer invocations for high order memory requests. You shouldn't disable this option unless there really is a strong reason for it. Signed-off-by: Felix Fietkau <nbd@nbd.name> Signed-off-by: Michal Hrusecky <michal.hrusecky@nic.cz>
* x86/64: enable X86_INTEL_LPSS to select PINCTRLMartin Schiller2018-08-251-1/+10
| | | | | | | This makes it possible to use the MCP23S08 i/o expander on x86_64 platforms with linux 4.14. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* x86: disable CONFIG_EFI_VARSAlif M. Ahmad2018-05-181-1/+1
| | | | | | | | | | Disable CONFIG_EFI_VARS, since it suffers from sysfs limitation (no support for variable longer than 1024 bytes). kmod-fs-efivarfs is the replacement of this, which enables mounting efivarfs file system and doesn't suffer from 1024 bytes limitation. Signed-off-by: Alif M. Ahmad <alive4ever@live.com>
* kernel: bump 4.14 to 4.14.11Stijn Tintel2018-01-031-1/+2
| | | | | | | | | | | | | | | Rename unwinder config symbols to match upstream changes. Refresh patches. Update patch that no longer applies: 202-reduce_module_size.patch Also enable CONFIG_PAGE_TABLE_ISOLATION. This feature was backported from 4.15 to the 4.14 stable series. It is enabled by default, so enable it in OpenWrt as well. Compile-tested on x86/64. Runtime-tested on x86/64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* x86: Add support for kernel 4.14Hauke Mehrtens2017-12-161-4/+32
| | | | | | | | This adds basic support for kernel 4.14, this was tested in qemu only. The subtarget configuration was refresh with kernel 4.14 and the options needed to make it compile on kernel 4.9 were added manually. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: refresh configurationHauke Mehrtens2017-12-161-3/+3
| | | | | | | Just refresh the kernel configuration, some options are removed because they are now in the generic kernel configuration. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: add on-chip thermal sensors and cpuid supportPhilip Prindeville2017-12-161-1/+18
| | | | | | | | | | | Cover temperature sensors for all mainstream 64-bit processors, including AMD 10h and 15h families, Intel iCore, Xeon, Atom, and Via Nano. Also add CPUID support for user-space applications to detect CPU type. Include the on-chip sensors for 64-bit CPU's in the generic profile in case someone builds a 32-bit kernel to run on a Xeon SoC, etc. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* x86: refresh settings for 4.9.59Philip Prindeville2017-12-161-7/+1
| | | | Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* kernel: Hyper-V PCI pass throughLucian Cristian2017-11-221-1/+1
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* kernel: add packaging for Xeon iTCO watchdog timerPhilip Prindeville2017-09-171-1/+1
| | | | Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* x86: Fix xen serial console by removing conflicting PATA driverBaptiste Jonglez2017-07-161-1/+0
| | | | | | | | | | | | | | | | | | | | | The Xen serial console has been broken since the xen_domu subtarget was merged in the generic x86 subtarget (commits 1d6879ee and 371b382a). The reason for the broken serial console seems to be an IRQ conflict between the serial console driver and the PATA_LEGACY driver: [ 1.330125] genirq: Flags mismatch irq 8. 00000000 (hvc_console) vs. 00000000 (platform[pata_legacy.4]) [ 1.330134] hvc_open: request_irq failed with rc -16. [ 1.330148] Warning: unable to open an initial console. Just drop the PATA_LEGACY driver from the x86/generic and x86_64 subtargets, since this driver is marked experimental and only supports very old ISA devices anyway. It is still included in the x86/legacy subtarget where it rightfully belongs. Fixes: FS#787 Signed-off-by: Baptiste Jonglez <git@bitsofnetworks.org>
* x86/64: add xen DomU supportBaptiste Jonglez2017-07-162-1/+68
| | | | | | | | | | Xen support for x86/generic was added in 1d6879ee. This commit also enables it for x86/64. This was successfully tested with Xen 4.5, although the serial console is broken in the same way as x86/generic (see FS#787) Signed-off-by: Baptiste Jonglez <git@bitsofnetworks.org>
* x86: Move USB support from subtargets to target configBaptiste Jonglez2017-07-161-9/+0
| | | | | | | | | All x86 subtargets enable USB support, so it makes sense to enable it in the target config instead, to avoid duplication. Also refresh subtarget configs accordingly. Signed-off-by: Baptiste Jonglez <git@bitsofnetworks.org>
* x86: Refresh subtargets kernel configBaptiste Jonglez2017-07-161-14/+2
| | | | | | | | | | | | | | | | | This was done by simply running `make kernel_menuconfig CONFIG_TARGET=subtarget` and then saving without changing any option. Most of the removed options can be explained because they are already present in the target config or in the generic 4.9 config: - PAE-related options, enabled by default on x86 by 961c0eac - LZO-related options, enabled by default since 4.9 As far as I understand the build system, this shouldn't have any user-visible impact, because the build system already merges the various kernel configs during build. Signed-off-by: Baptiste Jonglez <git@bitsofnetworks.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 06:20:38 +0000