summaryrefslogtreecommitdiffstats
path: root/configs
Commit message (Collapse)AuthorAgeFilesLines
...
* rpi: barebox: version bump 2018.03.0 -> 2020.08.1Roland Hieber2020-09-154-19/+185
| | | | | | | | | | | | | | | | | | | | | | Update to the latest barebox version, which also has the side effect that it can boot the newer Linux kernel (first bad Distrokit commit was 61b5ec910db2fe82a39f, 2019-05-06: "platform-rpi/v7a: kernel version bump 5.0 -> 5.1"). Enable regulator support to get around a build issue in the RPi board code [1], and allow color by default on the console. Also enable PINCTRL_BCM283X, since it was renamed from GPIO_BCM283X. For all other settings, use their default value. Add a patch to fix a build failure with the bcm2835 sdhci driver. [1]: "rpi-common.c:462:8: error: implicit declaration of function 'regulator_get_name'; did you mean 'regulator_enable'? [-Werror=implicit-function-declaration]", fixed upstream via <https://www.mail-archive.com/barebox@lists.infradead.org/msg36326.html> Tested-by: Roland Hieber <rhi@pengutronix.de> on rpi1-b, rpi-zero-w Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* rpi: install kernel into /boot so that barebox can find itRoland Hieber2020-09-151-2/+6
| | | | | | (I don't know how this has worked before…?!) Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* rpi: kernel: version bump 5.6.2 -> 5.8.9Roland Hieber2020-09-152-47/+81
| | | | | | | | Update to the most recent kernel version and do an oldconfig with default values. Tested-by: Roland Hieber <rhi@pengutronix.de> on rpi1-b, rpi-zero-w Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* mips: kernel: version bump 5.6.2 -> 5.8.9Roland Hieber2020-09-156-144/+241
| | | | | | | | Update to the most recent kernel version and do an oldconfig with default values. Tested-by: Roland Hieber <rhi@pengutronix.de> on qemu-malta Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* PTXdist: migrate 2020.08.0 -> 2020.09.0Roland Hieber2020-09-156-13/+25
| | | | | | Migrate to the most current PTXdist version with default settings. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: kernel: version bump 5.8 -> 5.8.9Roland Hieber2020-09-141-2/+2
|
* x86_64: update to OSELAS.Toolchain 2020.08.0Roland Hieber2020-08-312-5/+5
| | | | | | Update to the latest toolchain, which was released this week. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v8a: update to OSELAS.Toolchain 2020.08.0Roland Hieber2020-08-312-6/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update to the latest toolchain, which was released this week. Updating to GCC 10 prompts for new kernel options: | CONFIG_ARM64_PTR_AUTH: | | Pointer authentication (part of the ARMv8.3 Extensions) provides | instructions for signing and authenticating pointers against secret | keys, which can be used to mitigate Return Oriented Programming (ROP) | and other attacks. | | This option enables these instructions at EL0 (i.e. for userspace). | Choosing this option will cause the kernel to initialise secret keys | for each process at exec() time, with these keys being | context-switched along with the process. | | If the compiler supports the -mbranch-protection or | -msign-return-address flag (e.g. GCC 7 or later), then this option | will also cause the kernel itself to be compiled with return address | protection. In this case, and if the target hardware is known to | support pointer authentication, then CONFIG_STACKPROTECTOR can be | disabled with minimal loss of protection. | | The feature is detected at runtime. If the feature is not present in | hardware it will not be advertised to userspace/KVM guest nor will it | be enabled. However, KVM guest also require VHE mode and hence | CONFIG_ARM64_VHE=y option to use this feature. | | If the feature is present on the boot CPU but not on a late CPU, then | the late CPU will be parked. Also, if the boot CPU does not have | address auth and the late CPU has then the late CPU will still boot | but with the feature disabled. On such a system, this option should | not be selected. | | This feature works with FUNCTION_GRAPH_TRACER option only if | DYNAMIC_FTRACE_WITH_REGS is enabled. | CONFIG_ARM64_BTI_KERNEL: | | Build the kernel with Branch Target Identification annotations | and enable enforcement of this for kernel code. When this option | is enabled and the system supports BTI all kernel code including | modular code must have BTI enabled. Use their default values for enhanced security. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: update to OSELAS.Toolchain 2020.08.0Roland Hieber2020-08-312-6/+6
| | | | | | Update to the latest toolchain, which was released this week. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* rpi: update to OSELAS.Toolchain 2020.08.0Roland Hieber2020-08-312-5/+5
| | | | | | Update to the latest toolchain, which was released this week. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* mips: update to OSELAS.Toolchain 2020.08.0Roland Hieber2020-08-316-11/+11
| | | | | | Update to the latest toolchain, which was released this week. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* reason: arm64 has pci, but distrokit no pciutilsRobert Schwebel2020-08-271-0/+2
| | | | Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v8a: Update platformconfig for i.MX8M boardsSascha Hauer2020-08-211-1/+15
| | | | | | Enable i.MX8M boards recently added to the platform. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Add i.MX8MQ-EVK imageSascha Hauer2020-08-213-0/+57
| | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Add i.MX8MP-EVK imageSascha Hauer2020-08-213-0/+57
| | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Add i.MX8MM-EVK imageSascha Hauer2020-08-213-0/+57
| | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Add blspec entry for the i.MX8MQ-EVKSascha Hauer2020-08-213-0/+49
| | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Add blspec entry for the i.MX8MP-EVKSascha Hauer2020-08-213-0/+49
| | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Add blspec entry for the i.MX8MM-EVKSascha Hauer2020-08-213-0/+49
| | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* platform-v8a: Update Kernel to Linux-5.8Sascha Hauer2020-08-212-549/+3879
| | | | | | | | | | | | | This updates the Kernel to Linux-5.8 The configuration has been started from "make defconfig" with the following modifications: - all architectures except mvebu and i.MX disabled - modified until reason has nothing more to mourn about - enabled Realtek Phy (needed for i.MX8MP-EVK) Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* i.MX8M: add imx-atfRouven Czerwinski2020-08-212-0/+96
| | | | Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
* i.MX8M: add firmware-imx 8.8Rouven Czerwinski2020-08-212-0/+134
| | | | Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
* Add barebox for i.MX8M boardsSascha Hauer2020-08-2110-0/+1487
| | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ptxdist: version bump 2020.07.0 -> 2020.08.0Robert Schwebel2020-08-107-18/+41
| | | | | | | | | A new ptxdist version is out. We set PTXCONF_KERNEL_CONFIG_BASE_VERSION=y in all platforms, as DistroKit is a base layer for other BSPs. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a: kernel patch to fix PHY warningsHolger Assmann2020-08-103-0/+70
| | | | | | | | | | | | | | | | With the recent move to Linux v5.8, we get a new kernel warning because it skew timings are now specified twice; once from use of "rgmii-id" and one from the [rt]xc-skew-ps in the device tree. This patch removes those timings since the board works fine with the new default settings. Patch has also been sent[1] to the respective mailing lists for upstream inclusion. [1]: https://lore.kernel.org/linux-arm-kernel/20200807150355.6116-1-h.assmann@pengutronix.de/ Signed-off-by: Holger Assmann <h.assmann@pengutronix.de>
* platform-v7a: kernel version bump 5.6.2 -> 5.8Holger Assmann2020-08-104-642/+116
| | | | | | | | | | | | | | | | | | | The latest kernel release now contains the device trees for the Linux Automation MC-1. We can thus drop them from the BSP. On the Kconfig front, we dropped CONFIG_MMC_OMAP(_HS) in favor of CONFIG_MMC_SDHCI_OMAP. For a while now, Linux has had a sdhci-omap driver for TI's OMAP SoCs making use of the SDHCI core library. This was in addition to the older omap-hsmmc driver, which didn't. Linux commit 0b4edf11187 ("ARM: dts: Move am33xx and am43xx mmc nodes tosdhci-omap driver") first included in v5.8 changes the device tree compatible of the mmc nodes on the am33xx and am43xx SoCs away from the omap-hsmmc to the SDHCI driver. Add the new compatibles, so we aren't broken by the change. Co-authored-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Holger Assmann <h.assmann@pengutronix.de>
* bsp.ref: use variants instead of redefining an existing assertionJan Luebbe2020-07-311-9/+10
| | | | | | | | ptxdist_debug_pci is defined in reference/ptxdist_debug.ref and available for all platforms. We only want to get different results for this assertion depending on the platform. Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
* bsp.ref: disable lspci reason check on platforms with pciRobert Schwebel2020-07-251-0/+10
| | | | | | | In DistroKit, we have patforms with and without PCI. As long as we don't actively use PCI, disable check for lcpci on platforms with PCI. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* bsp.ref: add vim filetype hint lineRobert Schwebel2020-07-251-0/+2
| | | | | | | To make vim recognize reason .ref files as yaml, add a corresponding filetype hint line. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* add x86_64 platformOleksij Rempel2020-07-243-0/+4113
| | | | | | and add a qemu script for testing. Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
* ptxdist: version bump 2020.06.0 -> 2020.07.0Robert Schwebel2020-07-155-14/+17
| | | | | | A new ptxdist version is out, update. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: stm32mp: enable PWM LEDs for MC-1Ahmad Fatoum2020-06-172-3/+8
| | | | | | | | With the barebox version bump, we now also have drivers for the STM32's PWM peripherals. The Linux Automation MC-1 features a PWM RGB LED, so enable the drivers for it to be usable. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: barebox: version bump v2020.04.0 → v2020.06.0Ahmad Fatoum2020-06-1719-913/+154
| | | | | | | | | | | | | | This allows us to drop the patch stack we had for Linux Automation MC-1 support. The series went into barebox with a fix that makes a warning about the eMMC environment go away. In return we import a single patch to address a breakage on the rpi3b platform. Being a bug fix, we should be able to drop the patch along with v2020.07.0. On the Kconfig front, CONFIG_OF_NET was dropped upstream, because it was an unreferenced symbol. All Kconfig changes are the result of an olddefconfig. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* ptxdist: version bump 2020.05.0 -> 2020.06.0Robert Schwebel2020-06-175-15/+25
| | | | | | A new ptxdist version is out, so we update our configs. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: images: stm32mp: remove cargo-culted partition-type in GPT configAhmad Fatoum2020-06-171-2/+0
| | | | | | | | | | | | | | | | | | | | | | partition-type is specific to DOS partitions. The counterpart for GPT partitions would be partition-type-uuid, which already defaults to "L", which is ok for our purposes. So far, this didn't have an impact, but starting with genimage v13, commit 013b22f26b73 ("Add support for Hybrid MBR partitions"), support for a partition-type key in a GPT partition was introduced: Using this option with a GPT partition table will create a hybrid MBR partition table with a maximum of 3 partition entries(this limit does not effect the maximum number of GPT partition entries in the same image). The ARM TF-A can't cope with this new format and fails to boot barebox with a "ERROR: Partition ssbl not found" message. Drop partition-type to prevent the ptxdist 2020.06.0 upgrade that includes host-genimage v13 from breaking the stm32mp157c-dk2 and lxa-mc1 images. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: lxa-mc1: migrate loglevel to barebox environment variableAhmad Fatoum2020-06-032-1/+2
| | | | | | | | | | | The MC-1 is the only supported board that configures loglevel via bootspec and not via barebox environment. For symmetry and because internal CI checks for it, migrate the loglevel to the environment. This also affects the stm32mp157c-dk2 target, which is fine. No one minds shorter boot times. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: barebox: stm32mp: enable sha1sum commandAhmad Fatoum2020-06-032-6/+4
| | | | | | | | The barebox images for all v7a boards (e.g. rpi3, bbb) have this already enabled. For symmetry with them and because internal CI checks for it, enable the command. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: barebox: stm32mp: enable barebox-state supportAhmad Fatoum2020-06-032-6/+5
| | | | | | | | The barebox images for all v7a boards (e.g. rpi3, bbb) have this already enabled. For symmetry with them and because internal CI checks for it, enable state support. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* ptxdist: version bump 2020.04.0 -> 2020.05.0Robert Schwebel2020-05-085-22/+17
| | | | | | A new ptxdist version is out, update DistroKit. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* MIPS: kernel: malta: remove flash partition tableOleksij Rempel2020-04-282-1/+47
| | | | | | it should be provided by the bootloader Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
* MIPS: platform: make sure KERNEL_LZOP is enabledOleksij Rempel2020-04-282-0/+2
| | | | | | Without prompt we can't enable it. Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
* MIPS: kernel: use LZO compressionOleksij Rempel2020-04-285-8/+8
| | | | | | With LZO we need 1 second less of boot time. Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
* v7a: generate image for Linux Automation MC-1Ahmad Fatoum2020-04-276-0/+95
| | | | | | | With TF-A and barebox support added in previous commits, everything is now in place for having DistroKit generate a MC-1 rootfs image. Do so. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: barebox: add support for Linux Automation MC-1Ahmad Fatoum2020-04-2717-17/+937
| | | | | | | | | | | | | This adds barebox support for the Linux Automation GmbH MC-1 board built around the Octavo Systems OSD32MP157C-512M SiP. The patches have been posted[1] upstream, but are not yet accepted. It's however expected for them to be part of barebox v2020.06.0, at which time we can drop the patchset again. [1]: https://lists.infradead.org/pipermail/barebox/2020-April/041653.html Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: stm32mp: add Linux Automation MC-1 device treeAhmad Fatoum2020-04-273-2/+593
| | | | | | | | | | | The device tree is based on the one in linux-stm32/stm32-next, which will probably be merged for Linux v5.8-rc1. Instead of waiting that long, we import it here with some stuff removed/changed, so it's usable without the prerequisite patches. We can drop them again, when we upgrade to v5.8-rc1. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: kernel: configure for MC-1Ahmad Fatoum2020-04-271-4/+4
| | | | | | | | | | | | Our current kernel config already supports one STM32MP board, but we have some HW on the MC-1, that the DK-2 lacks, namely a KSZ9031 PHY, an EEPROM in the SiP and PWM LEDs. We also got a display controller, but in interest of keeping kernel code size down, enabling DRM and associated drivers is left to a ptxdist layer specific to the MC-1. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: tf-a: add support for Linux Automation MC-1Ahmad Fatoum2020-04-263-1/+416
| | | | | | | | | | | | | The MC-1 can boot from SD-Card with the DK2 TF-A, but for use in production, it's meant to boot from eMMC. Patch in the MC-1 device tree, which enables the appropriate SDMMC controller. RAM timings are those of the DK-2, which have worked so far, but should be reconsidered prior to upstreaming. [Note: eMMC boot doesn't yet work, presumably due to hardware issues.] Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: tf-a: version bump v2.2 -> v2.3Ahmad Fatoum2020-04-261-3/+3
| | | | | | | | | | | | | | TF-A v2.3 brings in support for multi-image STM32MP1 builds, which means less boilerplate for us, because we can build images for multiple STM32MP1 boards at once with the same rule. We want to do this in the follow-up commit, so bump the version now. With this update, all boot device drivers are disabled by default. We can afford continuing to waste a few kilobytes in the first stage bootloader and in the future, we might want to support boards that don't boot from SDMMC anyway, so just (re-)enable all of them. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* ptxdist: migrate 2020.03.0 -> 2020.04.0 with defaultsAhmad Fatoum2020-04-265-13/+23
| | | | | | | | | With this release, the TF-A rule went upstream in revised form, so it's dropped as part of the migration. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> [adapted to current next] Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a: kernel: enable USB support for i'MX6Oleksij Rempel2020-04-251-2/+3
| | | | | | tested on RIoTBoard Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>