On 2023-09-21 21:45 +03:00, Simon Glass wrote:
> Binman[1] is a tool for creating firmware images. It allows you to
> combine various binaries and place them in an output file.
>
> Binman uses a DT schema to describe an image, in enough detail that
> it can be automatically built from component pa
On 2023-09-21 18:39 +03:00, Tom Rini wrote:
> On Wed, Sep 20, 2023 at 07:03:07PM -0600, Simon Glass wrote:
>> Hi Maxim,
>>
>> On Thu, 14 Sept 2023 at 10:20, Maxim Uvarov wrote:
>>>
>>> add external lwIP library as a git submodule.
If we add submodules, they should point to mirrors on source.denx.
On 2023-09-04 22:18 +05:30, Simon Glass wrote:
> Hi Rong,
>
> On Sun, 3 Sept 2023 at 20:50, Rong Tao wrote:
>>
>> From: Rong Tao
>>
>> /build-* can't ignore /build.
>
> How does that directory get created?
Most likely `make O=build` as an attempt to do out-of-tree builds? FWIW,
I manually crea
On 2023-08-28 20:54 +03:00, Simon Glass wrote:
> Hi Alper,
>
> On Sun, 27 Aug 2023 at 13:17, Alper Nebi Yasak
> wrote:
>>
>> On 2023-08-24 06:02 +03:00, Simon Glass wrote:
>>> In this early stage of using binman to produce output files, we are mostly
>>
On 2023-08-28 20:54 +03:00, Simon Glass wrote:
> Hi Alper,
>
> On Sun, 27 Aug 2023 at 09:49, Alper Nebi Yasak
> wrote:
>>
>> On 2023-08-15 01:43 +03:00, Simon Glass wrote:
>>> Hi Alper,
>>>
>>> On Mon, 14 Aug 2023 at 11:40, Alper Nebi Yasak
On 2023-08-30 10:33 +03:00, Ilias Apalodimas wrote:
> Hi Alper,
>
> On Sun, 27 Aug 2023 at 18:49, Alper Nebi Yasak
> wrote:
>>
>> On 2023-08-15 01:43 +03:00, Simon Glass wrote:
>>> Hi Alper,
>>>
>>> On Mon, 14 Aug 2023 at 11:40, Alper Nebi
On 2023-08-21 22:11 +03:00, Simon Glass wrote:
> On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak
> wrote:
>>
>> From: Alexander Graf
>>
>> We are going to introduce image damage tracking to fasten up screen
>> refresh on large displays. This patch a
t;>>>
>>>> On 21.08.23 21:11, Simon Glass wrote:
>>>>> Hi Alper,
>>>>>
>>>>> On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak
>>>>> wrote:
>>>>>> From: Alexander Graf
>>>>>>
>&
On 2023-08-21 23:06 +03:00, Alexander Graf wrote:
>
> On 21.08.23 21:11, Simon Glass wrote:
>> Hi Alper,
>>
>> On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak
>> wrote:
>>> From: Alexander Graf
>>>
>>> CONFIG_VIDEO_COPY implemented
;> make FB modifications actually pop up on screen.
>>>
>> Hmmm, so what function is it calling, then? I think we are getting
>> closer to the 'fix' I am trying to tease out.
>
> It literally calls vidconsole_puts():
>
> https://github.com/u-b
On 2023-08-28 20:54 +03:00, Simon Glass wrote:
> Hi Alper,
> On Mon, 28 Aug 2023 at 09:46, Alper Nebi Yasak
> wrote:
>>
>> On 2023-08-22 21:56 +03:00, Simon Glass wrote:
>>> Hi Alper,
>>>
>>> On Tue, 22 Aug 2023 at 06:10, Alper Nebi Y
On 2023-08-22 21:56 +03:00, Simon Glass wrote:
> Hi Alper,
>
> On Tue, 22 Aug 2023 at 06:10, Alper Nebi Yasak
> wrote:
>>
>> From: Alexander Graf
>>
>> Now that we have everything in place to support ramfb, let's wire it up
>> by default in the A
On 2023-08-22 21:56 +03:00, Simon Glass wrote:
> Hi Alper,
>
> On Tue, 22 Aug 2023 at 06:10, Alper Nebi Yasak
> wrote:
>>
>> Now that we have everything in place to support ramfb, let's wire it up
>> by default in the x86 QEMU targets. That way, we can use ra
On 2023-08-22 21:56 +03:00, Simon Glass wrote:
> Hi Alper,
>
> On Tue, 22 Aug 2023 at 06:10, Alper Nebi Yasak
> wrote:
>>
>> QEMU firmware config drivers need to be probed to bind the ramfb device.
>> The ramfb driver needs to be bound before relocation to proper
On 2023-08-22 21:56 +03:00, Simon Glass wrote:
> Hi Alper,
>
> On Tue, 22 Aug 2023 at 06:10, Alper Nebi Yasak
> wrote:
>>
>> From: Alexander Graf
>>
>> Now that we have a ramfb device driver, let's add the necessary glueing
>> magic to also spawn
On 2023-08-24 06:02 +03:00, Simon Glass wrote:
> In this early stage of using binman to produce output files, we are mostly
> seeing people using common extensions such as '.bin' and '.rom'
>
> But unusual extensions appear in some places.
>
> We would like 'buildman -k' to keep the build outputs
On 2023-08-27 19:32 +03:00, Heinrich Schuchardt wrote:
> Am 27. August 2023 16:56:51 MESZ schrieb Alper Nebi Yasak
> :
>> On 2023-08-25 22:28 +03:00, Simon Glass wrote:
>>> so we must allow EFI to write directly to the hardware framebuffer.
>>
>> If you want a
On 2023-08-15 01:43 +03:00, Simon Glass wrote:
> Hi Alper,
>
> On Mon, 14 Aug 2023 at 11:40, Alper Nebi Yasak
> wrote:
>> I actually want to put the root.img device first so that the VM can boot
>> into the installed system when it reboots, but U-Boot can't find
On 2023-08-25 22:28 +03:00, Simon Glass wrote:
> The efi_gop driver uses private fields from the video uclass to obtain a
> pointer to the frame buffer. Use the platform data instead.
>
> Check the VIDEO_COPY setting to determine which frame buffer to use. Once
> the next stage is running (and mak
e the same as its SPL
counterpart, because we're running out of alloc space in pre-reloc stage
with ramfb enabled.
Signed-off-by: Alper Nebi Yasak
---
This also suffers from the same issue with distros as the Bochs display
driver [1], where it results in a hang after GRUB menu selection before
bochs changes, add pre-reloc init and error handling]
Co-developed-by: Alper Nebi Yasak
Signed-off-by: Alper Nebi Yasak
---
Changes in v2:
- Drop imply VIDEO, env changes from RISC-V patch (in u-boot/next)
- Drop imply SYS_CONSOLE_IS_IN_ENV from RISC-V patch (def. y if VIDEO)
- Probe QFW in RISC-V
bochs changes, add pre-reloc init, error handling]
Co-developed-by: Alper Nebi Yasak
Signed-off-by: Alper Nebi Yasak
---
Changes in v2:
- Rebase on "qemu: arm: Enable Bochs, console buffering, USB keyboard"
- Drop env changes from ARM (necessary but in prerequisite series)
- D
can work as an initial vidconsole.
Signed-off-by: Alper Nebi Yasak
---
Alternatively, I guess I could default VIDEO_PCI_DEFAULT_FB_SIZE to a
higher size with "if VIDEO_RAMFB". But it exists because "PCI drivers
cannot be bound before relocation unless they are mentioned in the
devi
From: Alexander Graf
Now that we have a ramfb device driver, let's add the necessary glueing
magic to also spawn it when we find its qfw file node.
Signed-off-by: Alexander Graf
[Alper: Use if IS_ENABLED() instead of #ifdef]
Signed-off-by: Alper Nebi Yasak
---
Changes in v2:
- U
icate depends on DM_VIDEO, drop MAINTAINERS, decouple from
EFI_LOADER, add .bind(), kconfigurable resolution, struct in .h]
Co-developed-by: Alper Nebi Yasak
Signed-off-by: Alper Nebi Yasak
---
Changes in v2:
- Remove extra "depends on DM_VIDEO" already in "if VIDEO&q
From: Alexander Graf
The QEMU fw_cfg device supports writing entries as well. Add the constant
define for it so that we can leverage write functionality later.
Signed-off-by: Alexander Graf
Reviewed-by: Simon Glass
Signed-off-by: Alper Nebi Yasak
---
(no changes since v1)
include/qfw.h
fault"
v1: https://lore.kernel.org/u-boot/20220227144043.37359-1-ag...@csgraf.de/
Alexander Graf (5):
qfw: Add WRITE definition
ramfb: Add driver for ramfb display
qfw: Spawn ramfb device if its file is present
arm: qemu: Enable ramfb by default
riscv: qemu: Enable ramfb by default
Alp
-off-by: Alper Nebi Yasak
---
The second half of copy_to_texture is untested.
arch/sandbox/cpu/sdl.c | 25 +
arch/sandbox/include/asm/sdl.h | 9 +++--
drivers/video/sandbox_sdl.c| 16 +++-
3 files changed, 39 insertions(+), 11 deletions(-)
diff
es if possible. Move the
remaining sandbox sync call into the driver ops. Now that sandbox video
sync attempts can defer without resetting video damage, force a video
sync before checking that video syncs reset video damage.
Signed-off-by: Alper Nebi Yasak
---
drivers/video/sandbox_sdl.c
As a first step of removing sandbox-specific code from the video uclass,
move the sync rate limiter into the SDL code. We lose the ability to
immediately force a screen refresh, but can retry until it does.
Signed-off-by: Alper Nebi Yasak
---
arch/sandbox/cpu/sdl.c | 9 +
arch
can force it by
calling the op again it until it does something.
Signed-off-by: Alper Nebi Yasak
---
Alternatively, add "force" argument into the driver ops->video_sync().
But I think it should go away instead. The problem is video_sync() being
called irregularly and too frequentl
he work area
instead. Change it to display the copy buffer if enabled.
Signed-off-by: Alper Nebi Yasak
---
drivers/video/video-uclass.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/video/video-uclass.c b/drivers/video/video-uclass.c
index 3f9ddaadd15d..7cec6362570f
nt [1], but only the "partial updates" patch
is functionally dependent on it.
[1]
https://lore.kernel.org/u-boot/20230821135111.3558478-1-alpernebiya...@gmail.com/
Alper Nebi Yasak (5):
sandbox: video: Display copy framebuffer if enabled
video: Allow deferring and retrying driver
video damage control for all device drivers that call
video_set_flush_dcache() to make sure they benefit from it.
Signed-off-by: Alexander Graf
[Alper: Add to VIDEO_TIDSS, imply instead of select]
Co-developed-by: Alper Nebi Yasak
Signed-off-by: Alper Nebi Yasak
---
Changes in v5:
- Imply
re. That way, drivers can always rely on it to call the arch
specific callbacks.
This will increase code size for non-ARM platforms with CONFIG_VIDEO=y
slightly.
Reported-by: Heinrich Schuchardt
Signed-off-by: Alexander Graf
Reviewed-by: Simon Glass
Signed-off-by: Alper Nebi Yasak
---
(no chang
height/w, fill_part(), fix memmove(dev),
drop from defconfig, use damage.xstart/yend, use IS_ENABLED(),
call video_sync() before copy_fb check, update video_copy test]
Co-developed-by: Alper Nebi Yasak
Signed-off-by: Alper Nebi Yasak
---
Changes in v5:
- Remove video_sync_copy() a
ed up significantly.
Signed-off-by: Alexander Graf
Reported-by: Da Xue
[Alper: Use damage.xstart/yend, IS_ENABLED()]
Co-developed-by: Alper Nebi Yasak
Signed-off-by: Alper Nebi Yasak
---
Changes in v5:
- Use xstart, ystart, xend, yend as names for damage region
- Use IS_ENABLED() instead of CONFIG_IS_EN
From: Alexander Graf
Now that we have a damage tracking API, let's populate damage done by
UEFI payloads when they BLT data onto the screen.
Signed-off-by: Alexander Graf
Reported-by: Da Xue
Reviewed-by: Heinrich Schuchardt
[Alper: Add struct comment for new member]
Signed-off-by: Alper
From: Alexander Graf
Let's report the video damage when we draw a bitmap on the screen. This
way we can later lazily flush only relevant regions to hardware.
Signed-off-by: Alexander Graf
Reported-by: Da Xue
Reviewed-by: Simon Glass
Signed-off-by: Alper Nebi Yasak
---
(no changes sin
With VIDEO_DAMAGE, the video uclass tracks updated regions of the frame
buffer in order to avoid unnecessary work during a video sync. Enable
the config in sandbox and add a test for it, by printing strings at a
few locations and checking the tracked region.
Signed-off-by: Alper Nebi Yasak
ake rotated
console_putc_xy() damages pass tests, edit patch message]
Co-developed-by: Alper Nebi Yasak
Signed-off-by: Alper Nebi Yasak
---
Changes in v5:
- Use met->baseline instead of priv->baseline
- Use fontdata->height/width instead of VIDEO_FONT_HEIGHT/WIDTH
- Update console_r
ff-by: Alper Nebi Yasak
---
Does video_fill_part() need a video_sync(dev, false) here?
Changes in v5:
- Call video_damage() also in video_fill_part()
drivers/video/video-uclass.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/video/video-uclass.c b/drivers/video/video-uclass.c
code path will follow in later patches.
Signed-off-by: Alexander Graf
Reported-by: Da Xue
[Alper: Use xstart/yend, document new fields, return void from
video_damage(), declare priv, drop headers, use IS_ENABLED()]
Co-developed-by: Alper Nebi Yasak
Signed-off-by: Alper Nebi Yasak
.
Signed-off-by: Alper Nebi Yasak
---
Changes in v5:
- Add patch "video: test: Test partial updates of hardware frame buffer"
test/dm/video.c | 54 +
1 file changed, 54 insertions(+)
diff --git a/test/dm/video.c b/test/dm/video.c
index b9
, since we will want the two to be different in very
specific ways.
Add a boolean argument to the existing helper function to indicate which
frame buffer we want to inspect, and update the existing callers.
Signed-off-by: Alper Nebi Yasak
---
Changes in v5:
- Add patch "video: test: Su
we can skip calling, since we won't want it to error on
those mismatched cases.
Signed-off-by: Alper Nebi Yasak
---
Changes in v5:
- Add patch "video: test: Split copy frame buffer check into a function"
test/dm/video.c | 69 +
1 f
.kernel.org/all/20220606234336.5021-1-ag...@csgraf.de/
Alexander Graf (9):
dm: video: Add damage tracking API
dm: video: Add damage notification on display fills
vidconsole: Add damage notifications to all vidconsole drivers
video: Add damage notification on bmp display
efi_loader: GOP: Ad
Add an example qemu-system-aarch64 command that can make U-Boot on QEMU
boot into the Debian Installer, along with resulting console messages
from U-Boot, based on the existing documentation section for the x86
version.
Signed-off-by: Alper Nebi Yasak
---
I actually want to put the root.img
Commit 02be57caf730 ("riscv: qemu: Enable usb keyboard as an input
device") adds PCI xHCI support to QEMU RISC-V virtual machines and
enables using a USB keyboard as one of the input devices. Similarly,
enable those for ARM virtual machines as well.
Signed-off-by: Alper Nebi Yasak
R
-by: Alper Nebi Yasak
Reviewed-by: Simon Glass
Reviewed-by: Bin Meng
---
Here are select values from bdinfo and env:
DRAM bank = 0x
-> start= 0x4000
-> size = 0x0800
relocaddr = 0x476d6000
fdt_blob= 0x
Commit 716161663ec49 ("riscv: qemu: Enable Bochs video support") enables
a video console for QEMU RISC-V virtual machines using an emulated Bochs
VGA card. Similarly, enable it for ARM virtual machines as well.
Signed-off-by: Alper Nebi Yasak
Reviewed-by: Bin Meng
---
Changes in v2:
iya...@gmail.com/
Alper Nebi Yasak (4):
arm: qemu: Enable Bochs video support
arm: qemu: Enable PRE_CONSOLE_BUFFER
arm: qemu: Enable usb keyboard as an input device
doc: qemu: arm: Add a section on booting Linux distros
arch/arm/Kconfig | 10
board/emulation/qemu-
Commit 02be57caf730 ("riscv: qemu: Enable usb keyboard as an input
device") adds PCI xHCI support to QEMU RISC-V virtual machines and
enables using a USB keyboard as one of the input devices. Similarly,
enable those for ARM virtual machines as well.
Signed-off-by: Alper Nebi Yasak
---
-by: Alper Nebi Yasak
---
Not sure about the address, here are select values from bdinfo and env:
DRAM bank = 0x
-> start= 0x4000
-> size = 0x0800
relocaddr = 0x476d6000
fdt_blob= 0x46595d90
Commit 716161663ec49 ("riscv: qemu: Enable Bochs video support") enables
a video console for QEMU RISC-V virtual machines using an emulated Bochs
VGA card. Similarly, enable it for ARM virtual machines as well.
Signed-off-by: Alper Nebi Yasak
---
arch/arm/Kconfig
g/u-boot/20230723044041.1089804-1-bm...@tinylab.org/
Alper Nebi Yasak (3):
arm: qemu: Enable Bochs video support
arm: qemu: Enable PRE_CONSOLE_BUFFER
arm: qemu: Enable usb keyboard as an input device
arch/arm/Kconfig | 10 ++
board/emulation/qemu-arm/Kcon
Hi Ilias,
On 2023-07-28 14:15 +03:00, Ilias Apalodimas wrote:
> On Sat, 8 Jul 2023 at 18:21, Alper Nebi Yasak
> wrote:
>>
>> Debian's arm64 UEFI Secure Boot shim makes the EFI variable store run
>> out of space while mirroring its MOK database to variables. Th
(Note that I'm not objecting to merging the patchset as is, just
detailing future work you/I might want to do for non-CrOS userspace
support for this bootmeth.)
On 2023-08-04 06:02 +03:00, Simon Glass wrote:
> On Thu, 3 Aug 2023 at 15:31, Alper Nebi Yasak
> wrote:
>> I guess
Hi Simon,
On 2023-07-30 20:16 +03:00, Simon Glass wrote:
> The ChromiumOS bootmeth is fairly basic at present. It is able to boot
> only x86 kernels and contains quite a few hard-coded offsets.
>
> This series tidies it up by bringing in some vboot structures and adding
> support for ARM.
>
> It
On 2023-07-20 22:56 +03:00, Simon Glass wrote:
> With this version I have done with a generic name, in this case 'data',
> as suggested by Alper Nebi Yasak. This may be controversial, but we may
> as well have the dicussion now. I assume that there are no other
> ongoing
(I think I've strayed far away from schema/dtb side of things towards
binman-the-program side, so I'm dropping Rob and devicetree@ from Cc).
On 2023-07-20 22:55 +03:00, Simon Glass wrote:
> On Thu, 20 Jul 2023 at 09:23, Alper Nebi Yasak
> wrote:
>> There's also
Hi Kever,
On 2023-07-31 04:27 +03:00, Kever Yang wrote:
> I have send the review tag for these patches, but the patchwork does not
> able to get my review mail, and not able to update the patch status to
> reviewed,
>
> and that's why I missing this patch set.
>
> I will apply these patch manu
Some veyron boards seem to have Winbond SPI flash chips instead of
GigaDevice ones. At the very least, coreboot builds for veyron boards
have them enabled [1]. Enable support for them here as well.
[1] https://review.coreboot.org/c/coreboot/+/9719
Signed-off-by: Alper Nebi Yasak
---
configs
Hi Simon,
I know I haven't been able to look at binman stuff for a long time, but
I've been occasionally thinking about it through the course of a year
and think binman severely needs a design-wise review before things get
entrenched, even in the most fundamental parts. I do see the
cross-project
This can underflow as the calculation is done in and processed as
unsigned integer types. Check for underflow before doing the subtraction
and return zero if there's no space.
Signed-off-by: Alper Nebi Yasak
---
lib/efi_loader/efi_var_mem.c | 4
1 file changed, 4 insertions(+)
diff -
ere is a
note about this value matching PcdFlashNvStorageVariableSize when
EFI_MM_COMM_TEE is enabled, so keep the old default in that case.
[1] https://github.com/rhboot/shim/pull/577
Signed-off-by: Alper Nebi Yasak
---
I'm not very familiar with EFI things, apologies if this default
should n
node
in the board -u-boot.dtsi instead.
Signed-off-by: Alper Nebi Yasak
---
Not enabling these for chromebit_mickey, as that'd use HDMI in a way I
don't know how.
arch/arm/dts/rk3288-veyron-speedy-u-boot.dtsi | 14 ++
configs/chromebook_speedy_defconfig | 5 +
Sound support for chromebook_jerry needs the MAX98090 codec driver. This
was enabled in commit 2d0c01b8f0ad ("sound: rockchip: Add sound support
for jerry"), but apparently lost in commit 7ae2729401bb ("configs:
Resync with savedefconfig"). Enable it again.
Signed-off-
Commit 815ed79d8338 ("video: rockchip: Use TrueType fonts with jerry")
enables makes chromebook_jerry use TrueType fonts. Make other veyron
boards switch to it as well.
Signed-off-by: Alper Nebi Yasak
---
I have no idea why that commit disables USE_PRIVATE_LIBGCC, but I'm
follow
ble silent console as chromebook_minnie does.
Signed-off-by: Alper Nebi Yasak
---
configs/chromebit_mickey_defconfig | 3 +++
configs/chromebook_minnie_defconfig | 3 ++-
configs/chromebook_speedy_defconfig | 1 +
3 files changed, 6 insertions(+), 1 deletion(-)
diff --git
The rk3288-veyron-speedy-u-boot.dtsi file duplicates the bootphase dts
fragments from rk3288-veyron-u-boot.dtsi even though it #inclues that.
Deduplicate these into the latter file, which should also make the eMMC
available to the other veyron boards' SPL.
Signed-off-by: Alper Nebi
ned-off-by: Alper Nebi Yasak
---
arch/arm/mach-rockchip/rk3288/Kconfig | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-rockchip/rk3288/Kconfig
b/arch/arm/mach-rockchip/rk3288/Kconfig
index ea94ad114247..69a5614b449a 100644
--- a/arch/arm/mach-rockchip/rk3288/Kconfig
+++ b/arc
support")
Fixes: 9749d2ea29e ("rockchip: video: vop: Add reset support")
Signed-off-by: Alper Nebi Yasak
---
configs/chromebit_mickey_defconfig | 1 +
configs/chromebook_minnie_defconfig | 1 +
configs/chromebook_speedy_defconfig | 1 +
3 files changed, 3 inser
any of the
supported boards, and couldn't spent time to port the veyron-mighty I
have yet. Sending so others can test and for the first two patches I
think should go in v2023.07, but take with a grain of salt.
Alper Nebi Yasak (7):
rockchip: veyron: Enable RESET driver
rockchip: veyron: Enable b
On 31/10/2022 15:56, Roger Quadros wrote:> On 31/10/2022 05:40, Neha
Malcom Francis wrote:
>> On 30/10/22 07:13, Simon Glass wrote:
>>> On Fri, 28 Oct 2022 at 04:58, Fabio Estevam wrote:
[Adding Alper - binmam maintainer and Oliver, who faced the same issue on
imx8]
(Sorry I've been un
; >> build.sh
>if [[ "${BUILDMAN}" != "" ]]; then
> + pip install -r test/py/requirements.txt
>ret=0;
>tools/buildman/buildman -o /tmp -P -E -W ${BUILDMAN}
> ${OVERRIDE} || ret=$?;
>if [[ $ret -ne 0 ]]; then
Reviewed-by: Alper Nebi Yasak
On 15/06/2022 09:48, Neha Malcom Francis wrote:
> tispl.bin must be packaged (with ATF, OPTEE, DM and A72 SPL) for J721E.
> Binman picks up and packages entries according to the
> description given in the device tree.
>
> k3-j721e-a72-binman.dtsi has been introduced for A72 specific binman
> node.
On 15/06/2022 09:48, Neha Malcom Francis wrote:
> By providing entries in the binman node of the device tree, binman will
> be able to find and package board config binary artifacts generated by
> TIBoardConfig with sysfw.bin and generate the final image sysfw.itb.
>
> k3-j721e-r5-binman.dtsi has
On 15/06/2022 09:47, Neha Malcom Francis wrote:
> K3 devices requires x509 certificate to be added as header of bootloader
> binaries that allows ROM to validate the integrity of the image. Etype
> that generates a TI x509 certificate is added.
>
> Currently this etype is scaled for J721E. For J72
644 tools/binman/etype/ti_dm.py
> create mode 100644 tools/binman/test/225_ti_dm.dts
Reviewed-by: Alper Nebi Yasak
Same minor issues as the previous patch.
> diff --git a/Makefile b/Makefile
> index d20d264c53..9b29e8e6a2 100644
> --- a/Makefile
> +++ b/Makefile
> @@
gt; tools/binman/test/232_ti_sysfw.dts | 13 +
> 5 files changed, 60 insertions(+)
> create mode 100644 tools/binman/etype/ti_sysfw.py
> create mode 100644 tools/binman/test/232_ti_sysfw.dts
Reviewed-by: Alper Nebi Yasak
Minor points below.
> diff --git a/Makefile b/Mak
On 15/06/2022 09:47, Neha Malcom Francis wrote:
> For validating config files and generating binary config artifacts, here
> board specific config class is added.
>
> Add function cfgBinaryGen() in tibcfg_gen.py. It uses TIBoardConfig
> class to load given schema and config files in YAML, validate
On 15/06/2022 09:47, Neha Malcom Francis wrote:
> [...]
>
> Neha Malcom Francis (11):
> j721e_evm: schema: yaml: Add general schema and J721E board config
> files
> ti: tools: config: Add board config class to generate config binaries
> ti: etype: sysfw: Add entry type for sysfw
> ti:
y KBs.
>
> Tested-by: Tim Harvey #imx8m[m,n,p]-venice
> Signed-off-by: Peng Fan
> Reviewed-by: Alper Nebi Yasak
> [Alper: Check BINMAN_SYMS_OK instead]
> Signed-off-by: Alper Nebi Yasak
> ---
> drivers/ddr/imx/phy/helper.c | 47 +++--
On 23/06/2022 06:00, Peng Fan (OSS) wrote:
> Hi Alper,
>
> 在 2022/6/18 20:13, Alper Nebi Yasak 写道:
>> There's some trouble with an i.MX8M series [1] trying to use binman
>> symbols. The crux of it is the 'u_boot_any' symbols BINMAN_SYMBOLS
>> config
On 10/06/2022 00:38, Heiko Thiery wrote:
> Hi Tim, Hi Simon,
>
> [SNIP]
>
>>
>> Heiko,
>>
>> You can add multi-dtb support to this so that it's usable by the other
>> imx8mn boards with the following:
>>
>> [...]
>>
>> I don't mind sending this as a follow-up to your patch here.
>
> Since this
On 09/06/2022 23:49, Heiko Thiery wrote:
> To have only one place to describe the binman images us the
> imx8mn-u-boot.dtsi. To have support for different DDR firmwares this
> nodes are included dependent on the used DDR config option.
>
> Signed-off-by: Heiko Thiery
> Reviewed-by: Fabio Estevam
On 09/06/2022 23:49, Heiko Thiery wrote:
> To have a flash.bin file that also contains the U-Boot and TF-A/ATF
> create this like already done for other imx8 boards.
>
> Signed-off-by: Heiko Thiery
> Reviewed-by: Fabio Estevam
> Reviewed-by: Peng Fan
> ---
> v2: sync with current master and fix
On 13/06/2022 09:13, Peng Fan (OSS) wrote:
> From: Peng Fan
>
> Use BINMAN to generate flash.bin
>
> Signed-off-by: Peng Fan
> ---
>
> Based on
> https://patchwork.ozlabs.org/project/uboot/cover/20220611132035.32698-1-peng@oss.nxp.com/
>
> V2:
> Typo correct
>
> arch/arm/dts/imx93-11
On 16/06/2022 11:45, Peng Fan wrote:
> Hi all,
>
> I am thinking to extend binman to generate i.MX container
> header and IVT header, that means to replace mkimage to generate header.
>
> There is an NXP downstream imx-mkimage that diverge from upstream that
> double effort. There are still requi
On 15/06/2022 02:25, Peng Fan wrote:
>> Subject: Re: [PATCH 7/8] binman_sym: guard with
>> CONFIG_IS_ENABLED(BINMAN_SYMBOLS)
>>
>> On 13/06/2022 05:34, Peng Fan (OSS) wrote:
>>> 在 2022/6/11 20:44, Alper Nebi Yasak 写道:
>>>> CONFIG_IS_ENABLED(BINMAN)
file
Signed-off-by: Peng Fan
Reviewed-by: Tom Rini
Reviewed-by: Alper Nebi Yasak
---
This is from Peng's i.MX8M binman symbols series [1], picked it onto
this series because it made more sense as a binman symbols fix.
[1] armv8: u-boot-spl.lds: mark __image_copy_start as sy
uild error described above.
Explicitly disable the 'u_boot_any' symbols for i.MX8M boards. They are
already effectively unusable, and they are incompatible with the boards'
current binman image descriptions.
Signed-off-by: Alper Nebi Yasak
---
Changes in v2:
- Add new patch to disab
layouts. Fix the affected values, and check the magic symbol
wherever it makes sense.
Signed-off-by: Alper Nebi Yasak
---
(no changes since v1)
common/spl/spl.c| 1 +
include/binman_sym.h| 45 -
tools/binman/elf.py
The SPL code declares binman symbols for U-Boot phases depending on
CONFIG_IS_ENABLED(BINMAN_UBOOT_SYMBOLS). This config exists for SPL and
TPL, also add a version for VPL.
Signed-off-by: Alper Nebi Yasak
---
Changes in v2:
- Update VPL configs for the new BINMAN_UBOOT_SYMBOLS
common/spl
es to work with CONFIG_IS_ENABLED(BINMAN_SYMBOLS).
Co-developed-by: Peng Fan
[Alper: New config for phase symbols, update Kconfigs, commit message]
Signed-off-by: Alper Nebi Yasak
---
See Peng's patch [1] included in these changes.
[1] binman_sym: guard with CONFIG_IS_ENABLED(BINMAN_SYMB
The binman extern symbol declarations in spl.h are missing the VPL
symbols recently added to spl.c, add them like the others.
Signed-off-by: Alper Nebi Yasak
---
(no changes since v1)
include/spl.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/spl.h b/include/spl.h
index
igned-off-by: Alper Nebi Yasak
---
(no changes since v1)
common/spl/Kconfig.tpl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/spl/Kconfig.tpl b/common/spl/Kconfig.tpl
index 9a0e719cf949..834cb6b6dd82 100644
--- a/common/spl/Kconfig.tpl
+++ b/common/spl/Kconfig.tpl
@@
returning early
in those cases.
Signed-off-by: Alper Nebi Yasak
---
(no changes since v1)
common/spl/spl.c | 10 +++---
common/spl/spl_ram.c | 2 +-
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/common/spl/spl.c b/common/spl/spl.c
index 2a69a7c9324d..5630dcdb5c1e 100644
--- a
_SYMBOLS
- Add new patch to check binman symbols at runtime
- Add new patch to disable u_boot_any symbols for i.MX8M boards
- Pick Peng's __image_copy_start fix
Alper Nebi Yasak (7):
spl: binman: Fix use of undeclared u_boot_any symbols
spl: binman: Make TPL_BINMAN_SYMBOLS depend o
1 - 100 of 466 matches
Mail list logo
