aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/x86
Commit message (Collapse)AuthorAgeFilesLines
* x86/config-5.10: geode: add missing CONFIG_WATCHDOG_CORE optionFlorian Eckert2022-09-241-0/+1
| | | | | | | | | | | | | If this module is not set to y, then I get the following compilation error during geode build. Package kmod-w83627hf-wdt is missing dependencies for the following libraries: watchdog.ko Setting the linux CONFIG_WATCHDOG_CORE to y as in all other targets fixes this issue. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* x86/config-5.15: geode: add missing CONFIG_WATCHDOG_CORE optionFlorian Eckert2022-09-241-0/+1
| | | | | | | | | | | | | | If this module is not set to y, then I get the following compilation error during geode build. Package kmod-w83627hf-wdt is missing dependencies for the following libraries: watchdog.ko Setting the linux CONFIG_WATCHDOG_CORE to y as in all other targets fixes this issue. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* linux/x86: add missing CONFIG_WATCHDOG_CORE to *-wdtFlorian Eckert2022-09-241-4/+10
| | | | | | | | | The packages also need a dependency to watchdog core. This commit adds the needed WATCHDOG_CORE dependency. https://github.com/torvalds/linux/blob/master/drivers/watchdog/Kconfig Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* 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>
* target/x86: add grub2-bios-setup to DEFAULT_PACKAGESFlorian Eckert2022-09-191-1/+4
| | | | | | | | | | | | | | | | | | With the commit 5876d6a62fc0ae5799e7d9c896356f75c99a6f0a the command under `/usr/sbin/grub-bios-setup` has been moved to its own package named `grub-bios-setup`. The script `81_upgrade_bootloader` under `/lib/preinit` is used by all x86 targets to update the bootloader. The script is using the command `grub-bios-setup` for this. I get the following output at the first boot after the upgrade. `/etc/preinit: line 9: /usr/sbin/grub-bios-setup: not found`. To fix this, the DEFAULT_PACKAGES dependency is extended by the entry `grub2-bios-setup` so that the missing command is installed again. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* x86: setup netdev paths for MX100Martin Kennedy2022-09-101-1/+13
| | | | | | | | | | | | | | | | The Meraki MX100 has ten 1000BASE-T and 2 SFP ethernet ports through 3, 4-port PCIe devices. The default enumeration of these network devices' names does not correspond to their labeling. Fix this by explicitly naming the devices, mapping against their sysfs path. Note that these default network names can only be up to 8 characters, because we can have up to 8 characters of modifiers (e.g. ^br-, .4096$), and because the maximum network interface name is 16 characters long. Signed-off-by: Martin Kennedy <hurricos@gmail.com> [lowercase subject] Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: bump 5.10 to 5.10.136John Audia2022-08-121-1/+1
| | | | | | All patches automatically rebased. Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.15 to 5.15.60John Audia2022-08-111-1/+1
| | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B, mt7622/RT3200 Run-tested: bcm2711/RPi4B, mt7622/RT3200 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: Activate CONFIG_GPIOLIB in generic configurationHauke Mehrtens2022-08-106-6/+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>
* x86: add missing Lex 3I380NX network detectionPaul Spooren2022-08-052-0/+104
| | | | | | | | | | | | | | | | | | | The Lex 3I380NX industrial PC has 4 ethernet controllers on board which need pmc_plt_clk0 - 3 to function, add it to the critclk_systems DMI table, so that drivers/clk/x86/clk-pmc-atom.c will mark the clocks as CLK_CRITICAL and they will not get turned off. This commit is nearly redundant to 3d0818f5eba8 ("platform/x86: pmc_atom: Add Lex 3I380D industrial PC to critclk_systems DMI table") but for all Lex Baytrail devices. The original vendor firmware is only available using the WaybackMachine: http://www.lex.com.tw/products/3I380NX.html Signed-off-by: Michael Schöne <michael.schoene@rhebo.com> Signed-off-by: Paul Spooren <paul.spooren@rhebo.com> (Hans broader version for more Lex Baytrail systems, v5.15) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: update defconfig for 5.15.57John Audia2022-07-311-0/+7
| | | | | | | | Add some new/missing symbols relating to speculative execution mitigations[1]. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/arch/x86/Kconfig?id=v5.15.57&id2=v5.15.56 Signed-off-by: John Audia <therealgraysky@proton.me>
* x86: update defconfig for 5.10.133John Audia2022-07-291-1/+7
| | | | | | | | Add some new/missing symbols relating to speculative execution mitigations[1]. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/arch/x86/Kconfig?id=v5.10.133&id2=v5.10.132 Signed-off-by: John Audia <therealgraysky@proton.me>
* x86: 64: Add kmod-igc to default packagesHauke Mehrtens2022-06-291-1/+1
| | | | | | | | This adds the igc driver for the Intel 2.5GBit Ethernet chip to the default packages. Fixes: #10064 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>
* x86: fix damaged config 5.10 refreshChristian Lamparter2022-06-243-5/+3
| | | | | | | | | | | | Restore CONFIG_I8K + CONFIG_INTEL_INT0002_VGPIO that got removed when I refreshed the config. Each x86 target gets its own CONFIG_CRYPTO_BLAKE2S + LIB settings as only the x86_64 can use the accelerated x86 version. Also remove two extra spaces that sneaked into geode's config. Fixes: 539e60539a2f ("generic: enable CRYPTO_LIB_BLAKE2S[_X86|_ARM]") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* generic: enable CRYPTO_LIB_BLAKE2S[_X86|_ARM]Tomasz Maciej Nowak2022-06-2410-2/+20
| | | | | | | | | | | | 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>
* kernel/x86: move x86' specific watchdogs to the x86 targetChristian Lamparter2022-05-071-0/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | upstream linux have these watchdogs locked behind X86. These will not build on other architectures. So move them to target/linux/x86/modules.mk drivers/watchdog/Kconfig: |config F71808E_WDT | tristate "Fintek F718xx, F818xx Super I/O Watchdog" | depends on X86 |[...] |config IT87_WDT | tristate "IT87 Watchdog Timer" | depends on X86 |[...] |config ITCO_WDT | tristate "Intel TCO Timer/Watchdog" | depends on (X86 || IA64) && PCI |[...] |config W83627HF_WDT | tristate "Watchdog timer for W83627HF/W83627DHG and compatibles" | depends on X86 |[...] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: detangle meraki-mx100 / nu801 build confusionChristian Lamparter2022-05-071-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Grommish reported the dreaded build error that happend with 5.4 since the kernel didn't have the cgpio v2 interface. His reason for the removed 5.4 was that the octeon target had a memory leak issue, so he had to backport the removed 5.4 kernel for his tests. Chen Minqiang chimed in and noted that no matter what (i.e. @TARGET_x86 in depends) didn't prevent the package from being build on other targets. From what I can tell, the reason for this was that +nu801 meant that kmod-meraki-mx100 pulled in an unconditional dependency as part of to the kernel build. |scripts/package-metadata.pl mk tmp/.packageinfo | |$(curdir)/kernel/linux/compile += $(curdir)/firmware/linux-firmware/compile \ | $(curdir)/firmware/prism54-firmware/compile \ | $(curdir)/kernel/gpio-button-hotplug/compile \ | >>> $(curdir)/system/gpio-cdev/nu801/compile <<< change this by making the dependency conditional on the meraki-mx100 module itself. Note that the nu801 enables/sets the KCONFIG for the cgpio v2 interface itself, since the userspace program and not the kernel meraki-mx100 relies on it. Reference: <https://github.com/openwrt/openwrt/commit/eeb8fd4ce7e9> Reported-by: Grommish <grommish@gmail.com> Reported-by: Chen Minqiang <ptpt52@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: add ib700wdt module for x86 qemu watchdogsChristian Lamparter2022-05-071-0/+18
| | | | | | | | QEMU+Libvirt can emulate the ib700wdt watchdogs which due to its I/O-Port mapping makes it x86 specific. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: x86: remove an upstreamed patchRui Salvaterra2022-04-202-100/+0
| | | | | | | | | 012-pcengines-apu2-detect-apuv4-board.patch is upstream since Linux 5.5 [1]. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.5&id=3d00da1de3ea36ba44f4a7ba76c8c8b16f98204b Acked-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: move some symbols to generic configAleksander Jan Bajkowski2022-04-091-5/+0
| | | | | | | | | | | | | | | | | | | This commit add some enabled symbols to generic config. LTO is only supported by clang compiler and therefore should be disabled in the generic config instead of duplicating this symbol in each target. CONFIG_LTO_NONE do this job. The second group of symbols is enabled by the options available in the generic config and is therefore added here: * CONFIG_AF_UNIX_OOB is selected by CONFIG_NET && CONFIG_UNIX, * CONFIG_BINARY_PRINTF is selected by CONFIG_BPF_SYSCALL, * CONFIG_NET_SOCK_MSG is selected by CONFIG_BPF_SYSCALL && CONFIG_NET. The other symbols are disabled and should be in the generic config. This commit also removes these symbols from subtargets. Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
* kernel: modules: fix kmod-mdio-devres dependency for 5.15Petr Štetiar2022-03-291-1/+1
| | | | | | | | | | | | | | | Fixes following build issues: Package kmod-r8169 is missing dependencies for the following libraries: mdio_devres.ko Package kmod-ixgbe is missing dependencies for the following libraries: mdio_devres.ko Package kmod-amd-xgbe is missing dependencies for the following libraries: mdio_devres.ko Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: update config for 5.15Petr Štetiar2022-03-295-33/+92
| | | | | | Refresh kernel config with `make kernel_oldconfig` make target. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: enable 5.15 as testing kernelPetr Štetiar2022-03-291-0/+1
| | | | | | | So anyone interested can help with new kernel version integration and testing. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: copy config and patches from 5.10 to 5.15Petr Štetiar2022-03-297-0/+1784
| | | | | | | | | | | | | | 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>
* gpio-cdev: move kmod-leds-uleds dependency to MX100Christian Lamparter2022-03-271-2/+2
| | | | | | | | | | | | | The inclusion of the kmod-leds-uleds into the userspace nu801 package causes a circular dependency inside the buildsystem... which causes it to be picked regardless of other DEPENDS values. In case of the mx100, this could be solved by moving the kmod-leds-uled dependency to the kmod-meraki-mx100. Bonus: drop @!LINUX_5_4 from kmod-meraki-mx100 Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: Add support for Sophos XG 85 and XG 86 devicesRaylynn Knight2022-03-262-2/+3
| | | | | | | | | | | | This commit builds on previous efforts to add support for Sophos devices. * Add support for Sophos XG 85 with/without wireless * Add support for Sophos XG 86 with/without wireless Tested on Sophos XG 85w rev1 and XG 86 rev 1 Signed-off-by: Raylynn Knight <rayknight@me.com>
* gpio-cdev: re-add nu801 userspace driverChris Blake2022-03-252-2/+2
| | | | | | | | | | | | | | | | | | | | | This reverts commit 80b7a8a7f5a0a88fde6dd19f097df4d7cac9ff04. Now that 5.10 is the default kernel for all platforms, we can bring back the NU801 userspace driver for platforms that rely on it. Currently it's used on the MX100 x86_64 target, but other Meraki platforms use this controller. Note that we also now change how we load nu801. The way we did this previously with procd worked, but it meant it didn't load until everything was up and working. To fix this, let's call nu801 from boot and re-trigger the preinit blink sequence. Since nu801 runs as a daemon this is now something we can do. Signed-off-by: Chris Blake <chrisrblake93@gmail.com> (removed empty line, currently only MX100 uses it so: @TARGET_x86) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: legacy: enable pata_sis driverMatthias Schiffer2022-03-101-0/+1
| | | | | | | | This driver is needed to boot from CompactFlash on the Siemens Futro S400. The device has an AMD NX1500 CPU, which seems to be unsupported by the geode subtarget, so it must use legacy. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* kernel: 5.10: allocate last level PTEs in high memoryRui Salvaterra2022-03-011-1/+1
| | | | | | | | | | Enable support for allocating user space page table entries in high memory [1], for the targets which support this feature. This saves precious low memory (permanently mapped, the only type of memory directly accessible by the kernel). [1] https://www.kernel.org/doc/html/latest/vm/highmem.html Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* x86: geode: fix package nameing kmod-crypto-ebc does not existFlorian Eckert2022-02-261-1/+1
| | | | | | | This commit fixes the package naming that was added by commit: e1e4cbde5ceb228e60fff1fc752cb90d9a7df2ab Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* x86: grub2: search for the "kernel" filesystem on all disksJax Jiang2022-02-242-11/+1
| | | | | | | | | | | | | | | | | | | Previously, grub2 was hardcoded to always look on "hd0" for the kernel. This works well when the system only had a single disk. But if there was a second disk/stick present, it may have look on the wrong drive because of enumeration races. This patch utilizes grub2 search function to look for a filesystem with the label "kernel". This works thanks to existing setup in scripts/gen_image_generic.sh. Which sets the "kernel" label on both the fat and ext4 filesystem variants. Signed-off-by: Jax Jiang <jax.jiang.007@gmail.com> Suggested-by: Alberto Bursi <bobafetthotmail@gmail.com> (MX100 WA) (word wrapped, slightly rewritten commit message, removed MX100 WA) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: fix support for Sophos SG/XG wireless productsRaylynn Knight2022-02-191-8/+8
| | | | | | | | | | Correct typo that caused network interfaces for Sophos SG/XG wireless devices to not be configured properly. Tested on Sophos SG 135wr2, Sophos XG 125wr2 and Sophos SG 105wr1 Signed-off-by: Raylynn Knight <rayknight@me.com>
* x86: geode: add kmod-crypto-ebc needed for hw accelerationPaul Fertser2022-02-191-1/+2
| | | | | | | | | | Module kmod-crypto-hw-geode provides accelerated cbc(aes) and ecb(aes) but the software implementation is also needed when AES key size isn't 128 so that the operation can fall back. Add the kmod so that it would all work as expected out of the box. Tested-by: timur_davletshin Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* x86: improve sysinfo handling of dummy valuesStefan Lippers-Hollmann2022-01-081-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | Fall back to using board_vendor and board_name, if known dummy values are used for sys_vendor and product_name. Examples: To be filled by O.E.M.:To be filled by O.E.M. --> INTEL Corporation:ChiefRiver System manufacturer:System Product Name --> ASUSTeK COMPUTER INC.:P8H77-M PRO To Be Filled By O.E.M.:To Be Filled By O.E.M. --> ASRock:Q1900DC-ITX Gigabyte Technology Co., Ltd.:To be filled by O.E.M. --> Gigabyte Technology Co., Ltd.:H77M-D3H empty:empty --> TYAN Computer Corporation:TYAN Toledo i3210W/i3200R S5211 To Be Filled By O.E.M.:To Be Filled By O.E.M. --> ASRock:H77 Pro4-M Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* x86: add/improve support for Sophos SG/XG productsRaylynn Knight2021-12-292-2/+12
| | | | | | | | * Add support for Sophos SG/XG-115 r1, r2 with/without wireless * Add support for Sophos SG/XG-125 r1, r2 with/without wireless * Add wireless support for SG/XG-105 Signed-off-by: Raylynn Knight <rayknight@me.com>
* kernel: 5.10: consolidate mac80211 crypto optionsSergey Ryazanov2021-12-173-13/+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>
* kernel: filter out both Clang and LLD versionsSergey Ryazanov2021-12-171-1/+0
| | | | | | | | Both CLANG_VERSION and LLD_VERISON are autogenerated runtime configuration options, so add them to the kernel configuration filter and remove from generic and per-target configs to keep configs clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* x86: remove old lzma tuning patchChristian Lamparter2021-12-111-22/+0
| | | | | | | | | | | | | | | | | | | | | Chen Minqiang reported in his GitHub PR #4733 that: With CONFIG_TARGET_INITRAMFS_COMPRESSION_LZMA=y option set, the popular x86/amd64 target's initramfs-kernel failed to boot. The cause for this boot failure is that the LZMA compression uses a the first bytes to encode the compression parameters. It does not have a fixed magic. Yes, this only works if the the existing lzma options in the upstream are not changed. This patch does away with OpenWrt special LZMA options tuning since it is rather unlikely that upstream will improve the compression algorithm detection after all this time. Even though, the tuning produced a smaller initramfs (~1.1% in a spot check). Link: <https://github.com/openwrt/openwrt/pull/4733> Reported-by: Chen Minqiang <ptpt52@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: add/improve support for Sophos SG/XG productsStan Grishin2021-12-112-4/+13
| | | | | | | | | * Better product ID for Sophos SG/XG-105 models * Add support for Sophos SG/XG-135 r1, r2 with/without wireless Signed-off-by: Stan Grishin <stangri@melmac.ca> [Changed subject to x86 - probably eaten somewhere, the PR had it] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: added support to generate VHDX imagesOldřich Jedlička2021-12-052-1/+7
| | | | | | | Added support to generate dynamic-sized VHDX images for Hyper-V. Compile-tested on x86 and run-tested on Windows 10 21H2 (Hyper-V). Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com>
* x86: sort alphabetically default packagesAlberto Bursi2021-11-061-3/+4
| | | | | | | | | sorting alphabetically default packages and placing them on their own line. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it> [fixed whitespaces before tab, double whitespaces] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: enable kmod-tg3 on 64-bit by defaultAlberto Bursi2021-11-061-1/+2
| | | | | | | | | | | | | Gigabit ethernet adapters using BCM5719/5720 chipset are common on servers and as easy/cheap to get as Intel based ones. Usually found in 2-port and 4-port cards. Also some devices recently added to x86_64 target like the Meraki MX100 use this chipset for 8 of their 12 integrated ports. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* kernel: bump 5.10 to 5.10.73Rui Salvaterra2021-10-212-18/+5
| | | | | | Patches automatically refreshed. Signed-off-by: Rui Salvaterra <rsalvaterra@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>
* Revert "gpio-cdev: add nu801 userspace driver"Christian Lamparter2021-10-102-2/+2
| | | | | | | | | | | 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>
* x86: add support for Meraki MX100Chris Blake2021-10-106-0/+369
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* x86: remove obsolete Kernel 5.4Paul Spooren2021-10-0210-2009/+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>
* x86: use device vendor/model variableMoritz Warning2021-09-234-5/+10
| | | | | | | | Remove use of DEVICE_TITLE in favor of the DEVICE_VENDOR and DEVICE_MODEL as used by all other targets. Signed-off-by: Moritz Warning <moritzwarning@web.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-13 00:50:11 +0000