summaryrefslogtreecommitdiffstats
path: root/configs
Commit message (Collapse)AuthorAgeFilesLines
* v7a: barebox update 2020.09.0 -> 2021.02.0Uwe Kleine-König2021-03-1521-78/+234
| | | | | | | | | | | | | | One new patch is required to fix a regression for USB on rpi3. Also USB on rpi3 requires CONFIG_USB_NOP_XCEIV=y now which is enabled in the rpi2 config now. For the beaglebone two patches are added fixing a regression related to a dts sync from upstream. All three patches were already sent to the barebox mailing list. Acked-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
* v7a: barebox: am335x-mlo: use XZ compression to reduce sizeAhmad Fatoum2021-03-151-2/+2
| | | | | | | | | With the upcoming update, our current MLO config will exceed the maximum size allowed. Work around this by using XZ compression instead, which reduces size from 115K to 101K, which gives us a further 8K we can munch. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: barebox: verify MLO size at build timeAhmad Fatoum2021-03-151-1/+1
| | | | | | | SRAM0 on the AM335x is 109K in size. Specify this in the config, so we get a build error if our MLO exceeds this size. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: stm32mp: images: allow differing board names for FSBL and SSBLAhmad Fatoum2021-03-153-5/+7
| | | | | | | | | | | | | | So far, the two STM32MP1 boards we support had the same board name string within the file names of first stage (TF-A) and second stage (barebox) bootloaders. This will no longer be true when updating to a more recent barebox version, as the dk2 image's name has been changed to dkx to indicate support for both dk1 and dk2. Prepare for this by splitting up STM32MP_BOARD_NAME. No functional change. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
* unfs3: Fix generation of export listUwe Kleine-König2021-03-151-1/+1
| | | | | | | | | | | | | | Before this change the content of the export list is by default: / (rw,no_root_squash),insecure which is wrong. The closing parenthesis must be after the insecure keyword. It seems I'm the first user of unfs3 in the v7a platform since 2016. Fixes: c17c88e05a88 ("platform: beaglebone: nfs: add insecure option") Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
* platforms: enable more toolchain hardening optionsRobert Schwebel2021-03-153-4/+4
| | | | | | It is recommended to enable these options. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a: oldconfig kernelRobert Schwebel2021-03-151-1/+0
| | | | | | The kernel config is currently not clean. Run ptxdist oldconfig kernel. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: migrate to 2021.03.0Roland Hieber2021-03-156-14/+16
| | | | | | New version came out today, but the diff is uneventful. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: tf-a: update to v2.4Ahmad Fatoum2021-03-155-88/+167
| | | | | | | | | | | | | | | | | Trusted Firmware-A v2.4 was released last month and adds amongst others, enhancements to make use of the trusted boot chain possible with upstream components. The patch stack has now been posted upstream in hope we can eventually drop it: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/7339 https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/7340 For now, it was rebased with following modifications: - Sync with upstream device tree and new TF-A requirements - CLK_ETH_PLL4P is enabled for possible PTP use Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* platform-v7a: linux: version bump 5.8 -> 5.11Robert Schwebel2021-02-235-157/+159
| | | | | | The patch for lxa-mc1 is mainline, remove it. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* image-rpi2, image-rpi3: remove no-op ptxd_replace_magic callsDistroKit-2021.02.0Roland Hieber2021-02-092-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | The new 'ptxdist lint' feature complained about these lines: Undefined symbol PTXCONF_IMAGE_RPI2_GPU_MEM used in 'next/configs/platform-v7a/rules/image-rpi2.make'. Undefined symbol PTXCONF_IMAGE_RPI3_GPU_MEM used in 'next/configs/platform-v7a/rules/image-rpi3.make'. Indeed, these complaints were caused by multiple issues, probably going back to copy-and-paste from platform-rpi: * IMAGE_RPI2_GPU_MEM and IMAGE_RPI3_GPU_MEM were never defined in any kconfig menu since these lines were added (but a similar kconfig item exists in configs/platform-rpi) * configs/platform-v7a/rpi-firmware/config.txt didn't have any magic replacement markers anymore since commit 98626f8441add596486b * the "replaced" config.txt was never used by anything after writing it to PTXDIST_TEMPDIR (which is the case in configs/platform-rpi) Remove the call completely. Fixes: 1db122202276b9f343eb (2017-06-16, "platform-v7a: rpi2: add board support") Fixes: 98626f8441add596486b (2018-11-29, "add RPI3 Support") Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* ptxdist: version bump 2021.01.0 -> 2021.02.0Roland Hieber2021-02-096-13/+180
| | | | | | | A new PTXdist version was released last week, which also includes a kconfig update from v5.1 to v5.11-rc3. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* ptxdist: version bump 2020.09.0 -> 2021.01.0Robert Schwebel2021-02-026-48/+33
| | | | Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: stm32mp: enable mmc_extcsd utilityAhmad Fatoum2021-02-012-1/+2
| | | | | | | | | The LXA MC-1 can boot from eMMC as well. The BootROM only supports booting with fast boot acknowledge though, which is a one time configuration. Include the mmc_extcsd tool needed to configure this: https://www.barebox.org/doc/latest/boards/stm32mp.html#flashing-barebox Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: images: stm32mp: don't place backup GPT table into imageAhmad Fatoum2021-02-011-0/+1
| | | | | | | | | | | The images sizes don't correspond to a specific SD-Card or eMMC size, so software checking for the backup partition table at the end of the device won't find it. Dropping it will however reduce the STM32MP1 images size (618M -> 66M). Do so. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: images: stm32mp: don't quote boolean in genimageAhmad Fatoum2021-02-011-1/+1
| | | | | | | | Both forms are accepted, but it looks more natural to not quote non-string values. This is also what we do for the other genimage configs (e.g. bootable = true). Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* rpi: image-boot-vfat: remove unused variablesRoland Hieber2021-02-011-3/+1
| | | | | | | | | | | | The variables HEADER and START were apparently meant to be used as replacements in configs/platform-rpi/config/images/boot-vfat.config, but they are not used nowhere Furthermore, HEADER referenced a non-existent file, START used the non-existing Kconfig symbol IMAGE_BOOT_VFAT_START, and was not layer-aware by using PTXDIST_PLATFORMCONFIGDIR, and start.elf is also already referenced in FILES. Reviewed-by: Michael Olbrich <m.olbrich@pengutronix.de> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* rpi: barebox: make BAREBOX_EXTRA_ENV_PATH layer-awareRoland Hieber2021-02-011-1/+1
| | | | | | | | | | Since PTXdist commit 41cb4d9f9287d85ae11b (2018-07-24, Michael Olbrich: "barebox: support layers with BAREBOX_EXTRA_ENV_PATH"), this path is layer-aware and resolved relative to the platformconfig directory. Reviewed-by: Michael Olbrich <m.olbrich@pengutronix.de> Link: https://git.pengutronix.de/cgit/ptxdist/commit/?id=41cb4d9f9287d85ae11b Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* platforms: make DTC_OFTREE_DTS_PATH layer-awareRoland Hieber2021-02-013-3/+3
| | | | | | | | | | | | | | | | | | | | This ports PTXdist commit 4f058f4c37fa9fb1465a: | commit 4f058f4c37fa9fb1465a77757a35c48e5e4a9179 | Author: Michael Olbrich <m.olbrich@pengutronix.de> | Date: 2018-07-31 16:12:58 | | dtc: support layers in DTC_OFTREE_DTS_PATH by default | | PTXDIST_PLATFORMCONFIG_SUBDIR is a relative path and will be searched in | all layers. | | Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> Reviewed-by: Alexander Dahl <ada@thorsis.com> Reviewed-by: Michael Olbrich <m.olbrich@pengutronix.de> Link: https://git.pengutronix.de/cgit/ptxdist/commit/?id=4f058f4c37fa9fb1465a Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* image-stm32mp157c-dk2: fix image creation with new PTXdist versionMichael Olbrich2021-02-011-2/+2
| | | | | | | | | The names of the TF-A files changed with the new PTXdist version. This was necessary to support multiple platforms in one build: The platforms may create images with the same name. Without the aditional prefix, the names clash when copoed to images/. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
* MIPS: malta: enable USB XHCI supportOleksij Rempel2020-11-233-2/+11
| | | | | | | Make malta kernel work with qemu-xhci controller. It was needed to reproduce endiannes bug with candleLight CAN adapter. Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
* platform-v7a: enable IMX6Q_CPUFREQRouven Czerwinski2020-11-011-1/+1
| | | | | | This is required for the i.MX6 platforms supported by platform-v7a. Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
* v7a: sama5d2: generate image for Groboard Giantboard as wellAhmad Fatoum2020-11-016-0/+96
| | | | | | | Add the same bit of boilerplate we added for the EK1 to get an image generated for the giant board as well. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: at91: add sama5d2-based giant board device treeAhmad Fatoum2020-11-012-1/+300
| | | | | | | | | | | The Groboards Giant Board is a ATSAMA5D27C-D1G SiP-based SBC. The board features a 500MHz ARM Cortex-A5 and 128MB DDR2 SDRAM in the SiP as well as a MicroSD slot on the PCB. The device tree is taken from the one in barebox itself based on the vendor's DTS available at https://github.com/Groboards/giantboard-tools Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: generate image for sama5d27 SOM1 Evaluation KitAhmad Fatoum2020-11-017-1/+127
| | | | | | | | | | With the previous barebox and kernel changes, we can combine it with the DistroKit-v7a rootfs to get an image to boot on the sama5d27-som1-ek. Do this. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> [rebased to master] Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: kernel: extend for sama5d2 supportAhmad Fatoum2020-11-011-4/+65
| | | | | | | In preparation for generating images for the sama5d27, have our multiplatform kernel configuration target the sama5d2 as well. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: barebox: add new rule for sama5d2 supportAhmad Fatoum2020-11-016-0/+1102
| | | | | | | | | | | | | Later commits will have the v7a platform generate an image for Cortex-A5 based sama5d2 as well. Import here a new barebox-at91 rule that extends the barebox-common rule to provide support for the two sama5d27 boards supported by barebox: barebox-sama5d27-som1-ek.img barebox-sama5d27-som1-ek-xload-mmc.img barebox-groboards-sama5d27-giantboard.img barebox-groboards-sama5d27-giantboard-xload-mmc.img Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: barebox: version bump v2020.08.1 → v2020.09.0Ahmad Fatoum2020-11-0113-19/+40
| | | | | | | | | | | | | The previous upgrade to v2020.08.1 gave us first stage boot support on the sama5d2, but had slight multi-image breakage because the fresh giantboard support on the sama5d27 messed up the EK1 environment support: it set nv.boot.default=mmc1 in the built-in environment when none should've been set. This is fixed in v2020.09.0, which is imported here. The config changes are those of olddefconfig. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* platforms: host-dtc: version bump 1.5.1 -> 1.6.0Roland Hieber2020-11-014-8/+8
| | | | | | | | | | Version 1.6.0 includes a fix for building on hosts with gcc 10. This ports PTXdist commit 7990fbf116f66f82796b (2020-05-24, Michael Olbrich: "host-dtc: update default version to 1.6.0"). Link: https://lkml.org/lkml/2020/4/1/1206 Link: https://git.pengutronix.de/cgit/ptxdist/commit/?id=7990fbf116f66f82796b Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* reason: disable fixed-partitions check for qemu-mipsRoland Hieber2020-09-161-0/+7
| | | | | Cc: Oleksij Rempel <o.rempel@pengutronix.de> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* x86_64: kernel: version bump 5.6.2 -> 5.8.9Roland Hieber2020-09-152-69/+99
| | | | | | | | Update to the most recent kernel version and do an oldconfig with default values. Tested-by: Roland Hieber <rhi@pengutronix.de> on qemu-x86_64 Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v8a: kernel: version bump 5.8 -> 5.8.9Roland Hieber2020-09-152-6/+7
| | | | | | | Update to the most recent kernel version and do an oldconfig with default values. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: image-vexpress: slim down imageRoland Hieber2020-09-151-4/+5
| | | | | | | | We don't need the whole 1 GiB image, the rootfs is only about 50 MiB in size. Slim the image down to 64 MiB rootfs + 63 MiB data and 1 MiB of padding at the end to keep the kernel happy. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: barebox: version bump 2020.06.0 -> 2020.08.1Roland Hieber2020-09-1516-184/+59
| | | | | | | | | | Update to the most recent barebox release, which includes our patch. CONFIG_USB_GADGET_FASTBOOT_* have been renamed to CONFIG_FASTBOOT_*, for all other new options use the default values. Tested-by: Roland Hieber <rhi@pengutronix.de> on qemu-vexpress, rpi3-b Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: images: add more helpful kconfig help textsRoland Hieber2020-09-157-7/+8
| | | | Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
* v7a: kernel: version bump 5.8 -> 5.8.9Roland Hieber2020-09-151-4/+4
| | | | | | | | Update to the most recent kernel version and do an oldconfig with default values. Tested-by: Roland Hieber <rhi@pengutronix.de> on qemu-vexpress, rpi3-b Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* rpi: barebox: migrate defaultenv from /env/config to nv variablesRoland Hieber2020-09-152-19/+1
| | | | | | | | | | | | | | | | | | | | | All upstream defaultenvs were converted in barebox 2015.01.0 [2] to use nv variables instead of /env/config, and /env/config is no longer sourced by the init script since barebox 2019.06.0 [1]. The default defaultenv already contains our variable definitions for allow_color, user, and autoboot_timeout, and the information in linux.bootargs.base is detected automatically as linux.bootargs.console from the port name given by the serial driver and CONFIG_BAUDRATE in the barebox config, so we don't have to convert those. This leaves boot.default, and converting this variable should also fix the issue of barebox trying to boot from net (instead of SD card) by default. [1]: 2019-02-25, Sascha Hauer: "defaultenv: Convert init script to C", https://git.pengutronix.de/cgit/barebox/commit/?id=90df2a955e3c66fee2c5 [2]: 2014-11-06, Sascha Hauer: "defaultenv-2: Make use of nonvolatile variables", https://git.pengutronix.de/cgit/barebox/commit/?id=7962e7a0b423a5dfba25 Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* 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>