| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
After updating to PTXdist 2021.02.0, our rule file is now identical to
the upstream version.
This reverts commit a9e6149a8348e0f130b1efe5d31d9440a80017ef.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
v14 adds support for gpt-no-backup, which allows us to shrink our GPT
image sizes for the lxa-mc1 and stm32mp157c-dk.
This commit can be reverted with the migration to ptxdist v2020.02.0.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
It's no longer needed with the new ptxdist release.
Tested-by: Roland Hieber <rhi@pengutronix.de>
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
This is required for the i.MX6 platforms supported by platform-v7a.
Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
|
|
|
|
|
|
|
|
| |
Add some basic documentation for the two new boards added in the
previous commits.
Suggested-by: Roland Hieber <rhi@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
Update to the most recent kernel version and do an oldconfig with
default values.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
(I don't know how this has worked before…?!)
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
| |
Since PTXdist 2020.09.0, we have strace 5.8 from upstream.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
| |
Migrate to the most current PTXdist version with default settings.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
sphinx complained about them:
checking consistency...
.../distrokit/platform-x86_64/state/docs/hardware_mips_qemu.rst: WARNING: document isn't included in any toctree
.../distrokit/platform-x86_64/state/docs/hardware_x86_64_qemu.rst: WARNING: document isn't included in any toctree
done
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
|
|
| |
It is enough to describe only once how to select the platform and
build the images, as the steps are the same for every platform. Only the
platformconfig and the toolchain architecture changes, so summarise them
in a table at the beginning of the section.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
| |
Give a brief documentation on how to install the correct PTXdist and
toolchain versions, and update outdated links to the PTXdist homepage.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
Robert, this relies on updated documentation on the PTX homepage. Please
merge www.pengutronix.de, branch rhi/topic/toolchain-install first :-)
|
|
|
|
|
|
|
| |
The handmade configure script in iproute2 doesn't correctly find libcap.
Enforce it to be there in any case.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
| |
This imports the .in file from ptxdist-2020.08.0, as a base for the
following patch.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
| |
Update to the latest toolchain, which was released this week.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Update to the latest toolchain, which was released this week.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
| |
Update to the latest toolchain, which was released this week.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
| |
Update to the latest toolchain, which was released this week.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|