Hi Luca,
On Tue, Feb 21, 2023 at 9:55 AM Luca Ellero wrote:
> +int imx93_adc_channel_data(struct udevice *dev, int channel,
static int
> +int imx93_adc_start_channel(struct udevice *dev, int channel)
static int
> +int imx93_adc_stop(struct udevice *dev)
static int
> +int
All fields in kwbimage header are in little endian format.
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/kwbimage.c b/tools/kwbimage.c
index 1128c934dda9..97be3bed79cb 100644
--- a/tools/kwbimage.c
+++
In Dove functional specification, which use kwbimage v0, is also defined
nand block size field. So dump NAND_BLKSZ also for v0 images.
In Kirkwood functional specification, which also use kwbimage v0, this
field is not defined. So when it is zero and Kirkwood is detected, do not
dump it.
Fixes:
Add a new Kconfig option CONFIG_MVEBU_SPL_BOOT_DEVICE_PEX which instruct
make to generate kwbimage with PEX header. This image is used for booting
from PCI Express device which is in the Root Complex mode.
Support is very simple, SPL after finishes DDR training returns back to the
BootROM (via
Upper-bound for iterating for-loop over register set entries is incorrect.
Fix it byt calculating correct number of entries.
And fix also dumping the last entry DATA_DELAY, which is the last and not
first (zero).
Fixes: 1a8e6b63e24f ("tools: kwbimage: Dump kwbimage config file on '-p -1'
For all images except SATA is data offset in bytes. For SATA it is in LBA
format (number of sectors). This is how Marvell BootROM interprets it.
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tools/kwbimage.c b/tools/kwbimage.c
index
Secure boot header signature is calculated from the image header with
zeroed header checksum. Calculation is done in add_secure_header_v1()
function. So after calling this function no header member except
main_hdr->checksum can be modified. Commit 2b0980c24027 ("tools: kwbimage:
Fill the real
Signed-off-by: Pali Rohár
---
.../serdes/a38x/high_speed_env_spec.c | 4 +--
.../serdes/a38x/high_speed_env_spec.h | 4 +--
arch/arm/mach-mvebu/serdes/a38x/sys_env_lib.c | 14 +++--
arch/arm/mach-mvebu/serdes/a38x/sys_env_lib.h | 30 ---
4 files changed, 8
MVEBU_SPL_BOOT_DEVICE_SPI is for NOR flash. Either serial or parallel. Not
for general serial/SPI devices. The correct name should be BOOT_DEVICE_NOR
but name SPI is already used in mkimage config format which we do not want
to change for compatibility reasons.
MVEBU_SPL_BOOT_DEVICE_MMC is for
Variable image_size contains size of the header, not size of the whole
image. Rename this variable to reflect content.
Signed-off-by: Pali Rohár
---
cmd/mvebu/bubt.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/cmd/mvebu/bubt.c b/cmd/mvebu/bubt.c
index
Show image type and version during parsing of kwbimage.
And show reasons in error messages when parsing failed.
This can help to debug issues with invalid images.
Signed-off-by: Pali Rohár
---
tools/kwboot.c | 39 ++-
1 file changed, 34 insertions(+), 5
kwbimage nandblocksize field is in 64 kB unit, but NAND_BLKSZ command
expects it in bytes. So do required unit conversion.
Also zero value in nandblocksize field has special meaning. When this field
is set to zero, the default block size is used. This default size is
defined by the NAND flash
Some NOR images may be execute-in-place and do not contain DDR init code in
its kwbimage header. Such images cannot be booted over UART as BootROM
loads them to RAM. Add check that kwbimage contains DDR init code in its
header (either as binary code header or as the simple register-value set).
In
Add information of all available image types and where they should be
stored. Storage location offsets where documented from the disassembly of
the A385 BootROM image dump.
Signed-off-by: Pali Rohár
---
tools/kwboot.c | 62 ++
1 file changed, 62
In SPL are active memory maps set by the BootROM. Define them in cpu.h file
to the correct values. Some peripherals are not mapped at all.
Signed-off-by: Pali Rohár
---
arch/arm/mach-mvebu/include/mach/cpu.h | 16
1 file changed, 16 insertions(+)
diff --git
Proper U-Boot moves SPI0 CS0 Flash mapping from 0xD400 to 0xF400
and change its size from 64 MB to 8 MB. Definitions are already in
MBUS_SPI_BASE/MBUS_SPI_SIZE macros. So define these macros also for SPL
build, use them in env_sf_get_env_addr() function and move this function
from spl.c to
To make add_secure_header_v1() function more readable, call it directly
with arguments: header pointer with header size and data image pointer with
data image size. No functional change.
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 15 +--
1 file changed, 5 insertions(+), 10
Fixes: 1a8e6b63e24f ("tools: kwbimage: Dump kwbimage config file on '-p -1'
option")
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/kwbimage.c b/tools/kwbimage.c
index 1719b0415da1..a6f6f1578c79 100644
---
This new db-88f6820-amc_nand_defconfig file is copy of existing
db-88f6820-amc_defconfig file and changed to instruct build system to
generate final kwbimage for NAND booting. It was done by adding options:
CONFIG_MVEBU_SPL_BOOT_DEVICE_NAND=y
CONFIG_MVEBU_SPL_NAND_BADBLK_LOCATION=0x00
When asking mkimage to create a new image file and option -d is not
specified then mkimage show human unfriendly error message:
mkimage: Can't open (null): Bad address
Without debugger it is hard to debug what is the issue. Function open() is
being called with file name set to NULL. So add a
Signed-off-by: Pali Rohár
---
arch/arm/mach-mvebu/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-mvebu/cpu.c b/arch/arm/mach-mvebu/cpu.c
index 1f8cdf8744e6..c5089a91c747 100644
--- a/arch/arm/mach-mvebu/cpu.c
+++ b/arch/arm/mach-mvebu/cpu.c
@@ -25,7 +25,7
Secure boot data image signature is calculated from the data image without
trailing 4-bit checksum. Commit 37cb9c15d70d ("tools: kwbimage: Simplify
aligning and calculating checksum") unintentionally broke this calculation
when it increased payloadsz variable by 4 bytes which was propagated also
This change allows to load boot image from the first SATA/SCSI device
partition and burn it to board boot location (e.g. SPI-NOR). This is
particularly when storage device is not handled by U-Boot as USB mass
storage (which is already supported by bubt) but as SATA/SCSI device.
Signed-off-by:
Mention fact about changing baudrate back when -B is used.
Signed-off-by: Pali Rohár
---
doc/kwboot.1 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/kwboot.1 b/doc/kwboot.1
index a528fbbe8c38..5cda3b4d88a8 100644
--- a/doc/kwboot.1
+++ b/doc/kwboot.1
@@ -159,7 +159,8
Skip filling legacy_img_hdr structure for XIP images which do not use
legacy_img_hdr structure header. Adding unwanted header to other image
formats, like kwbimage cause generation of broken image.
Signed-off-by: Pali Rohár
---
tools/mkimage.c | 4 +++-
1 file changed, 3 insertions(+), 1
Use for it pretty print function: genimg_print_size(). This makes it more
human readable, like other offset and sizes printed by this tool.
Signed-off-by: Pali Rohár
---
tools/kwbimage.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/kwbimage.c
This new clearfog_sata_defconfig file is copy of existing
clearfog_defconfig file and changed to instruct build system to
generate final kwbimage for SATA booting.
This change is more readable via git option --find-copies-harder.
Signed-off-by: Pali Rohár
---
configs/{clearfog_defconfig =>
This makes updating of u-boot/firmware on Marvell boards easier.
Signed-off-by: Pali Rohár
---
cmd/mvebu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/cmd/mvebu/Kconfig b/cmd/mvebu/Kconfig
index 029f722096b1..e83a98294912 100644
--- a/cmd/mvebu/Kconfig
+++ b/cmd/mvebu/Kconfig
@@
This change add support for mkimage's -s option to kwbimage format. It will
create an kwbimage with empty data part of image (data part would contain
only required 32-bit checksum). mkimage's -s option is indicated by skipcpy
flag and it is basically in conflict with mkimage's -d (datafile)
Marvell BootROM loads MMC image from sector 0 (HW boot or data partition)
and SD image from sector 1.
So for SD card booting it is needed to not use constant CONFIG MMC options
and instead of them it is needed to define functions spl_mmc_boot_mode()
spl_mmc_get_uboot_raw_sector() which
Add reference to Avanta Boot Flow documentation, BobCat2, AlleyCat3 and
PONCat3 BootROM Firmware documentation and links to public Marvell tools:
hdrparser.c and doimage.c
Signed-off-by: Pali Rohár
---
tools/kwboot.c | 19 +++
1 file changed, 19 insertions(+)
diff --git
For 32-bit Armada boards which use SPL we can determinate boot device from
existing MVEBU_SPL_BOOT_DEVICE_* option. For all other boards (e.g. 64-bit
Armada) default option still needs to be set manually.
Signed-off-by: Pali Rohár
---
cmd/mvebu/Kconfig | 4
1 file changed, 4 insertions(+)
'secure_mode' and 'fuse_read_u64' are used only on A38x and A37xx.
Fixes: f7b0bbca2b62 ("cmd: mvebu/bubt: Check for A38x/A37xx OTP secure bits and
secure boot")
Signed-off-by: Pali Rohár
---
cmd/mvebu/bubt.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
Support for burning into the correct eMMC HW boot partition was broken and
removed in commit 96be2f072768 ("mvebu: bubt: Drop dead code"). Reimplement
this functionality and bring it back again.
Fixes: 96be2f072768 ("mvebu: bubt: Drop dead code")
Signed-off-by: Pali Rohár
---
cmd/mvebu/bubt.c
Despite the official specification, Marvell BootROM does not interpret
srcaddr from SATA image as number of sectors the beginning of the hard
drive, but as number of sectors relative to the main header.
To process SATA kwbimage and load U-Boot proper from it in the same way as
Marvell BootROM, it
This patch series contains various improvements and fixes for existing
logical errors. Boot phase was adjusted to match behavior of Armada 385
BootROM by inspecting and disassembling of BootROM binary dump itself.
Important information are included in documentation patch for kwboot.
Most of the
There is no need to export these local functions and structures.
Signed-off-by: Pali Rohár
---
cmd/mvebu/bubt.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/cmd/mvebu/bubt.c b/cmd/mvebu/bubt.c
index 72ed87b89ec3..820d342ae100 100644
--- a/cmd/mvebu/bubt.c
+++
Marvell BootROM interprets execaddr of SPI/NOR XIP images as relative byte
offset from the from the beginning of the flash device. So if data image
offset and execute offset are not same then it is needed to adjust them
also in DDR RAM.
Fixes: f2c644e0b8bc ("tools: kwboot: Patch destination
Signed-off-by: Pali Rohár
---
cmd/mvebu/bubt.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/cmd/mvebu/bubt.c b/cmd/mvebu/bubt.c
index 1b08ca9298c2..74ea037dda98 100644
--- a/cmd/mvebu/bubt.c
+++ b/cmd/mvebu/bubt.c
@@ -725,9 +725,8 @@ static int
BOOT_DEVICE_MMC2 and BOOT_DEVICE_MMC2_2 are representing mmc dev 1 but all
Armada SoCs have only one mmc controller. So remove references to
non-existent second mmc controller.
Fixes: f830703f4284 ("arm: mvebu: Check that kwbimage blockid matches boot
mode")
Signed-off-by: Pali Rohár
---
Despite the official specification, Marvell BootROM does not interpret
srcaddr from SATA image as number of sectors the beginning of the hard
drive, but as number of sectors relative to the main header.
To parse SATA kwbimage in the same way as Marvell BootROM, it is needed to
interpret srcaddr
Despite the official specification, Marvell BootROM does not interpret
srcaddr from SDIO image as offset in number of sectors (like for SATA
image), but as offset in bytes (like for all other images except SATA).
To ensure that we do not store invalid SDIO image to the boot location
(read by the
Despite the official specification, Marvell BootROM does not interpret
srcaddr from SDIO image as offset in number of sectors (like for SATA
image), but as offset in bytes (like for all other images except SATA).
To parse SDIO kwbimage in the same way as Marvell BootROM, it is needed to
interpret
Despite the official specification, Marvell BootROM does not interpret
srcaddr from SATA image as number of sectors the beginning of the hard
drive, but as number of sectors relative to the main header.
Reject invalid and accept valid SATA images.
Fixes: 5a0653493307 ("cmd: mvebu/bubt: Check for
Despite the official specification, Marvell BootROM does not interpret
srcaddr from SDIO image as offset in number of sectors (like for SATA
image), but as offset in bytes (like for all other images except SATA).
To generate SDIO kwbimage compatible with Marvell BootROM, it is needed to
have
Hello,
my goal is to load OP-TEE after BL31 and before u-boot, so I enabled
CONFIG_SPL_OPTEE_IMAGE.
But it fails to build (tested current master):
$ make -j$(nproc) CROSS_COMPILE=aarch64-linux-gnu- rock-pi-4-rk3399_defconfig
all
./arch/arm/include/asm/unified.h: Assembler messages:
On Sat, Feb 04, 2023 at 09:00:56PM -0600, jassisinghb...@gmail.com wrote:
> From: Jassi Brar
>
> The patchset reduces ~400 lines of code, while keeping the functionality same
> and making
> meta-data operations much faster (by using cached structures).
>
> Issue:
> meta-data copies (primary
Thanks! Do I need someone else to be able to merge this or your review
is enough?
Best regards,
Svyatoslav R.
вт, 21 лют. 2023 р. о 21:37 Simon Glass пише:
>
> On Mon, 20 Feb 2023 at 10:41, Svyatoslav Ryhel wrote:
> >
> > Remove need of dts binding for button keyboard since it reuses
> >
On Tue, 21 Feb 2023 at 09:22, Tom Rini wrote:
>
> From: Pali Rohár
>
> Now that the Dockerfile creates images which have the binaries we
> require included, have CI make symlinks for them and update the existing
> script to support this.
>
> Signed-off-by: Tom Rini
> ---
> Pali, since you
Unfortunately the IRAM used to stash the bootstage records in TPL
becomes accessible after SPL runs. Presumably this is because of ATF
taking it over.
We could move the stash to another address in SPL, before passing it to
U-Boot proper. But it seems easier to wait until we have support for
This is needed to enable the boot command used to start standard boot.
Enable it by default. This brings in quite a few features, mostly in
common with DISTRO_DEFAULTS
Signed-off-by: Simon Glass
---
boot/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/boot/Kconfig b/boot/Kconfig
This board has moved to standard boot but the old 'distro_bootcmd'
command is still active. Disable DISTRO_DEFAULTS to fix this.
Signed-off-by: Simon Glass
---
configs/rockpro64-rk3399_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/rockpro64-rk3399_defconfig
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> Using the mkimage entry with the multiple-data-files prop and having a
> missing external blob result in an unexpected ValueError exception using
> the --allow-missing flag.
>
> ValueError: Filename 'missing.bin' not found in input path
Hi Heinrich,
On Mon, 20 Feb 2023 at 10:15, Andre Przywara wrote:
>
> On Sun, 19 Feb 2023 12:36:28 +0100
> Heinrich Schuchardt wrote:
>
> Hi,
>
> > We want to move from using #ifdef to using if in our code. A lot of our
> > code using #ifdef is structured like:
> >
> > #ifdef CONFIG_FOO
> >
Hi Peter,
On Mon, 20 Feb 2023 at 03:16, Peter Robinson wrote:
>
> On Wed, Feb 1, 2023 at 8:46 PM Simon Glass wrote:
> >
> > This seems to have been used by ppc4xx which was removed a while back.
> > The Kconfig does not exist so it is never built. Drop it.
>
> That assumption isn't entirely
On Fri, 17 Feb 2023 at 17:59, Rasmus Villemoes
wrote:
>
> Use the helper part_get_info_by_dev_and_name_or_num() for parsing a
> dev[:part] string and obtaining the partition info in one go, instead
> of open-coding all that.
>
> As a bonus, this will automatically allow using the dev#partname
>
Hi Rasmus,
On Fri, 17 Feb 2023 at 17:59, Rasmus Villemoes
wrote:
>
> It's almost no extra code to hook up a buddy to the 'read' command. In
> fact, since the command is passed its own 'struct cmd_tbl', we can use
> the exact same callback, and let it figure out for itself whether it
> was
Hi Jonas
+Tom Rini
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> When binman is invoked during a build of U-Boot and an external blob is
> missing, the user is usually presented with a generic file not found in
> input path message.
>
> Invoke binman with --allow-missing so that binman
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> Show the filename next to the node path in missing blob help messages,
> also show a generic missing blob message when there was no help message
> for the help tag.
>
> Signed-off-by: Jonas Karlman
> ---
> tools/binman/control.py | 13
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> There is no blank line between last missing blob help message and the
> header line for optional blob help messages.
>
> Image 'simple-bin' is missing external blobs and is non-functional: atf-bl31
>
>
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> The mkimage entry is working like a section entry but inherits from
> Entry not Entry_section. Copy implementations of missing Check-functions
> from Entry_section and adopt to Entry_mkimage.
>
> Signed-off-by: Jonas Karlman
> ---
>
Hi Heinrich,
On Thu, 16 Feb 2023 at 23:56, Heinrich Schuchardt
wrote:
>
>
>
> On 2/17/23 03:55, Simon Glass wrote:
> > " properHi Heinrich,
> >
> > On Thu, 16 Feb 2023 at 14:31, Heinrich Schuchardt
> > wrote:
> >>
> >>
> >>
> >> On 2/16/23 21:17, Simon Glass wrote:
> >>> Hi Heinrich,
> >>>
>
This cuts down build performance considerably and is not always needed,
when checking for build errors, etc.
Add a flag to disable it.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/buildman/builder.py | 5 -
tools/buildman/builderthread.py | 2 ++
This is quite a useful thing to use when building since it avoids small
size changes between commits. Add a -r flag for it.
Also undefine CONFIG_LOCALVERSION_AUTO since this appends the git hash
to the version string, causing every build to be slightly different.
Signed-off-by: Simon Glass
---
It is sometimes useful to see the exact 'make' command used by buildman
for a commit. Add an output file for this.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/buildman/builderthread.py | 13 +
tools/buildman/buildman.rst | 8
This file holds the environment used when doing a build. Add a note
about it.
Signed-off-by: Simon Glass
---
(no changes since v1)
tools/buildman/buildman.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/buildman/buildman.rst b/tools/buildman/buildman.rst
index
On Sun, 19 Feb 2023 at 23:13, Samuel Holland wrote:
>
> This array is private to the IPU driver, so it should be declared there.
>
> Signed-off-by: Samuel Holland
> ---
>
> drivers/remoteproc/ipu_rproc.c | 4 +++-
> include/remoteproc.h | 1 -
> 2 files changed, 3 insertions(+), 2
On Sat, 18 Feb 2023 at 08:27, Ilias Apalodimas
wrote:
>
> As described in [0] if a command requires use of an untested algorithm
> or functional module, the TPM performs the test and then completes the
> command actions.
>
> Since we don't check for TPM_RC_NEEDS_TEST (which is the return code of
Hi Heinrich,
On Sat, 18 Feb 2023 at 02:17, Heinrich Schuchardt
wrote:
>
> Compiling sandbox_defconfig with CONFIG_SPL_MMC=y results in
>
> drivers/mmc/mmc-uclass.c:211:
> undefined reference to `dev_read_u32_default'
>
> Revert the fraudulent patch.
>
> Fixes: ef79ef21a852 ("dm: core:
On Sat, 18 Feb 2023 at 08:27, Ilias Apalodimas
wrote:
>
> A prior patch adds a new API function for TPM2.0, which performs
> the full startup sequence of the TPM. Add a selftest for that.
>
> Signed-off-by: Ilias Apalodimas
> ---
> Changes since v4:
> - New patch
>
> test/dm/tpm.c | 5 +
>
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> Replace notes with nodes in code comments and docstrings.
>
> Signed-off-by: Jonas Karlman
> ---
> tools/binman/etype/fit.py | 2 +-
> tools/binman/etype/section.py | 2 +-
> tools/binman/state.py | 2 +-
> 3 files changed, 3
On Mon, 20 Feb 2023 at 10:41, Svyatoslav Ryhel wrote:
>
> Remove need of dts binding for button keyboard since it reuses
> gpio-keys binding. Select gpio-keys driver if button keyboard
> is selected since button keyboard can not operate on its own.
>
> Tested-by: Svyatoslav Ryhel # HTC One X T30
On Sun, 19 Feb 2023 at 23:13, Samuel Holland wrote:
>
> This removes code that abused the device's platform data, interpreting
> the driver platform data as if it was the uclass platform data.
>
> Signed-off-by: Samuel Holland
> ---
>
> .../driver-model/remoteproc-framework.rst | 29
Hi Heinrich,
On Sat, 18 Feb 2023 at 02:34, Heinrich Schuchardt
wrote:
>
> Building sandbox_defconfig with CONFIG_SPL_TIMER=y results in an error
>
> include/dm/platdata.h:63:33: error: static assertion failed:
> "Cannot use U_BOOT_DRVINFO with of-platdata.
> Please use devicetree
On Sat, 18 Feb 2023 at 01:34, Heinrich Schuchardt
wrote:
>
> Building sandbox_spl with CONFIG_DEBUG leads to errors due to missing
> symbols:
>
> /usr/bin/ld: common/spl/spl_fit.o: in function `spl_fit_upload_fpga':
> common/spl/spl_fit.c:595: undefined reference to `fpga_load'
>
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> Missing optional blobs was not reported for generated entries, e.g.
> tee-os on rockchip targets. Implement a CheckOptional to fix this.
>
> After this the following can be shown:
>
> Image 'simple-bin' is missing external blobs but is
Hi Tom,
On Tue, 14 Feb 2023 at 09:31, Tom Rini wrote:
>
> On Sun, Feb 12, 2023 at 04:15:14PM -0700, Simon Glass wrote:
> > This converts 1 usage of this option to the non-SPL form, since there is
> > no SPL_PHY_CADENCE_SIERRA defined in Kconfig
> >
> > Signed-off-by: Simon Glass
> > ---
> >
> >
On Sat, 18 Feb 2023 at 08:27, Ilias Apalodimas
wrote:
>
> All the TPM drivers as well as out TCG TIS API for a TPM2.0 device
> return -EBUSY if the device has already been opened. Adjust
> the sandbox TPM do return the same error code.
>
> Signed-off-by: Ilias Apalodimas
> ---
> Changes since
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> Entry_blob_ext contains an implementation of SetAllowFakeBlob that is
> identical to the one in the base Entry class, remove it.
>
> Signed-off-by: Jonas Karlman
> ---
> tools/binman/etype/blob_ext.py | 8
> 1 file changed, 8
On Sun, 19 Feb 2023 at 15:02, Jonas Karlman wrote:
>
> Use correct argument name in docstrings.
>
> Signed-off-by: Jonas Karlman
> ---
> tools/binman/entry.py | 2 +-
> tools/binman/etype/blob.py| 2 +-
> tools/binman/etype/section.py | 4 ++--
> 3 files changed, 4 insertions(+), 4
Hi Quentin,
On Mon, 20 Feb 2023 at 04:15, Quentin Schulz
wrote:
>
> Hi Simon,
>
> On 2/18/23 00:49, Simon Glass wrote:
> > Hi Quentin,
> >
> > On Fri, 17 Feb 2023 at 05:21, Quentin Schulz
> > wrote:
> >>
> >> Hi all,
> >>
> >> On 2/17/23 03:55, Simon Glass wrote:
> >>> Hi Tom,
> >>>
> >>> On
Hi Neha,
On Fri, 17 Feb 2023 at 04:46, Neha Malcom Francis wrote:
>
> Currently, bintool supports external compilable tools as single
> executable files. Adding support for git repos that can be used to run
> non-compilable scripting tools that cannot otherwise be present in
> binman.
>
>
Hi Vagrant,
On Mon, 20 Feb 2023 at 09:21, Simon Glass wrote:
>
> Hi Vagrant,
>
> On Sat, 18 Feb 2023 at 19:19, Vagrant Cascadian wrote:
> >
> > On 2022-12-07, Simon Glass wrote:
> > > Drop the use of scripts and rely on standard boot for all operation.
> >
> > This patch, applied as
Hi Mark,
On Tue, 21 Feb 2023 at 02:28, Mark Kettenis wrote:
>
> > Date: Tue, 21 Feb 2023 01:46:22 +0100
> > From: Marek Vasut
>
> Hi Marek,
>
> > On 2/21/23 00:45, Simon Glass wrote:
> > > On Sat, 21 Jan 2023 at 12:28, Mark Kettenis wrote:
> > >>
> > >> When a system has multiple XHCI
On Sat, Feb 04, 2023 at 09:02:02PM -0600, jassisinghb...@gmail.com wrote:
> From: Jassi Brar
>
> The common code can now read, verify and fix meta-data copies
> while exposing one consistent structure to users.
> Only the .read_mdata() and .write_mdata() callbacks of fwu_mdata_ops
> are
On Tuesday 21 February 2023 11:22:29 Tom Rini wrote:
> From: Pali Rohár
>
> Now that the Dockerfile creates images which have the binaries we
> require included, have CI make symlinks for them and update the existing
> script to support this.
>
> Signed-off-by: Tom Rini
> ---
> Pali, since you
Now that the gwventana_emmc_defconfig is the same as the
gwventana_gw5904_defconfig we can remove the latter.
Signed-off-by: Tim Harvey
---
board/gateworks/gw_ventana/MAINTAINERS | 1 -
configs/gwventana_gw5904_defconfig | 179 -
2 files changed, 180 deletions(-)
The MV88E61XX switch is used on the GW5904 which is an eMMC based board.
Adding it here allows us to remove the gwventana_gw5904_defconfig.
Signed-off-by: Tim Harvey
---
configs/gwventana_emmc_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/configs/gwventana_emmc_defconfig
From: Pali Rohár
Now that the Dockerfile creates images which have the binaries we
require included, have CI make symlinks for them and update the existing
script to support this.
Signed-off-by: Tom Rini
---
Pali, since you posted this in a thread as untested, can you please
reply with a S-o-b
Thanks in advance!
I would love to get any ACKs/Tested-By/Reviewed-By's but most likely
no one, apart from the Transformers community and me, relies so much
on display drivers in u-boot. Most likely this is why it was barely
set and only for T20.
Best regards,
Svyatoslav R.
вт, 21 лют. 2023 р.
Buildman ran fine on TOT u-boot-tegra/master rebased w/TOT u-boot/master on
Friday. I'll send a PR today.
I'll look at merging your new DC 11-patch series later in the week. If we could
get any ACKs/Tested-By/Reviewed-By's in ASAP that would be great.
Tom
-Original Message-
From:
If the use of MTD is restricted to passive serial, this is OK with me.
Yeah, but that is not how upstream things work. You need to also think
of any other use cases.
These are the things I want to achieve.
* transfer data using the SPI driver and not use board files.
For that, the FPGA
On Mon, 20 Feb 2023 at 03:49, Dzmitry Sankouski wrote:
>
> - move common code to vidconsole_internal.h and console_core.c
> - unite probe functions
> - get rid of code duplications in switch across bpp values
> - extract common pixel fill logic in two functions one per
> horizontal and vertical
Den 2023-02-21 kl. 12:19, skrev Michael Walle:
Am 2023-02-21 11:42, schrieb Ulf Samuelsson:
Den 2023-02-21 kl. 10:08, skrev Michael Walle:
If it is right or wrong to use that as an MTD is a matter of opinion.
I am still hoping the MTD maintainer would provide input here.
I might be missing
On 2/21/23 10:28, Mark Kettenis wrote:
Date: Tue, 21 Feb 2023 01:46:22 +0100
From: Marek Vasut
Hi Marek,
On 2/21/23 00:45, Simon Glass wrote:
On Sat, 21 Jan 2023 at 12:28, Mark Kettenis wrote:
When a system has multiple XHCI controllers, some of the
properties described in the
This file is included by the different chameleonv3 variants. Change the
name to .dtsi.
Signed-off-by: Paweł Anikiel
Reviewed-by: Simon Glass
---
...arria10_chameleonv3.dts => socfpga_arria10_chameleonv3.dtsi} | 0
arch/arm/dts/socfpga_arria10_chameleonv3_270_3.dts | 2 +-
This file was missed during the conversion process. Add the symbol to
defconfig.
Signed-off-by: Paweł Anikiel
Reviewed-by: Simon Glass
---
configs/socfpga_chameleonv3_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/socfpga_chameleonv3_defconfig
Add devicetree for chameleonv3 with the 270-2I2-D11E variant of the
Mercury+ AA1 module
Signed-off-by: Paweł Anikiel
Reviewed-by: Simon Glass
---
arch/arm/dts/Makefile| 1 +
.../socfpga_arria10_chameleonv3_270_2-u-boot.dtsi| 12
Allow SPL to boot from an ext4 filesystem.
Signed-off-by: Paweł Anikiel
Reviewed-by: Simon Glass
---
configs/socfpga_chameleonv3_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/socfpga_chameleonv3_defconfig
b/configs/socfpga_chameleonv3_defconfig
index
Set the bitstream name per Chameleon variant. This allows the same
boot filesystem with all bitstream variants to be used on different
boards.
Signed-off-by: Paweł Anikiel
Reviewed-by: Simon Glass
---
arch/arm/dts/socfpga_arria10_chameleonv3_270_3-u-boot.dtsi | 4
101 - 200 of 243 matches
Mail list logo