| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since Barebox v2020.11.0, the build system supports a configurable
version string that is baked into the barebox image, see the following
upstream barebox commits:
* commit 98c221e3fad57f271d60 (2020-09-23, "Makefile: add buildsystem version variable")
* commit c7dcac9de597f006fdc8 (2020-09-23, "common: print buildsystem version in barebox banner")
* commit c600d8812e9f3b98591a (2020-09-23, "common: globalvar: add variable for buildsystem_version_string")
* commit 01b53d3b728073996e7e (2020-09-23, "imd: add buildsystem version to metadata")
Set that version string to the Git hash so we can always find out from
which DistroKit version a barebox-in-the-wild was built. (Even if we
don't use barebox >= v2020.11.0 on all platforms yet, future barebox
updates will benefit from this change.)
For mips, we use the upstream barebox rule, which takes the version
string from the platformconfig. For all other platforms, this change
effectively ports the following commit from PTXdist 2021.04.0:
| commit f5500c922424ee71dd99e80f743ed6d994e5bca6
| Author: Steffen Trumtrar <s.trumtrar@pengutronix.de>
| Date: 2021-04-01 10:36:41
|
| rules: barebox: support barebox buildsystem_version
|
| barebox supports setting a buildsystem version. This is useful to have
| an exact buildsystem version like a commit hash accessible from barebox.
|
| Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
| Message-Id: <20210401083641.9251-2-s.trumtrar@pengutronix.de>
| Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
Link: https://git.pengutronix.de/cgit/barebox/commit/?id=98c221e3fad57f271d60
Link: https://git.pengutronix.de/cgit/barebox/commit/?id=c7dcac9de597f006fdc8
Link: https://git.pengutronix.de/cgit/barebox/commit/?id=c600d8812e9f3b98591a
Link: https://git.pengutronix.de/cgit/barebox/commit/?id=01b53d3b728073996e7e
Link: https://git.pengutronix.de/cgit/ptxdist/commit/?id=f5500c922424ee71dd99
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
| |
Migrate with default settings to the new PTXdist version, which was
released today.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
| |
PTXdist 2021.03.0 has a bug: without this, the v7a platform cannot be
built.
This basically reverts 510c23705bc999bda9d0b040418dfebe94fc9c68.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
| |
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
|
|
|
|
|
|
| |
This is enabled in barebox and also in the kernel for rpi and v8a.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
|
|
|
|
| |
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
The kernel config is currently not clean. Run ptxdist oldconfig kernel.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
| |
New version came out today, but the diff is uneventful.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
The patch for lxa-mc1 is mainline, remove it.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
This is required for the i.MX6 platforms supported by platform-v7a.
Signed-off-by: Rouven Czerwinski <r.czerwinski@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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Migrate to the most current PTXdist version with default settings.
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
A new ptxdist version is out, update.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
A new ptxdist version is out, so we update our configs.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
A new ptxdist version is out, update DistroKit.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|