-11-18-regression-fixes' (2021-11-18 18:25:19 -0500)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-amlogic.git
> tags/u-boot-amlogic-2029
>
> for you to fetch changes up to 28f70cfcfd82ac509c8da772b74e5dc2df795fd2:
>
On Fri, Nov 19, 2021 at 07:22:29PM +0200, Ilias Apalodimas wrote:
> Hi Tom,
>
> Please pull for master
>
> The following changes since commit 3144ba23bf4649f699078259fdf2e5cb4eab8f53:
>
> Merge branch '2021-11-15-assorted-fixes' (2021-11-16 14:23:30 -0500)
>
> are available in the Git
GNU has a very useful third argument to match() but this is not supported
in the POSIX awk. It is a great shame.
Update the code to cope.
Signed-off-by: Simon Glass
---
scripts/env2string.awk | 23 +++
1 file changed, 15 insertions(+), 8 deletions(-)
diff --git
+Rob Herring oops
On Fri, 19 Nov 2021 at 17:04, Simon Glass wrote:
>
> This adds three new options with varying degree of interest / precedent.
>
> This being sent to the mailing list since it might attract more review.
> A PR will be sent when this has had some review. That is why the file
>
This adds three new options with varying degree of interest / precedent.
This being sent to the mailing list since it might attract more review.
A PR will be sent when this has had some review. That is why the file
path is set up for https://github.com/devicetree-org/dt-schema rather
than the
On Fri, Nov 19, 2021 at 10:52:27PM +0100, Heinrich Schuchardt wrote:
>
>
> Am 19. November 2021 22:33:04 MEZ schrieb Tom Rini :
> >If we look at the path that bootm/booti take when preparing to boot the
> >OS, we see that as part of (or prior to calling do_bootm_states,
> >explicitly) the
Am 19. November 2021 22:33:04 MEZ schrieb Tom Rini :
>If we look at the path that bootm/booti take when preparing to boot the
>OS, we see that as part of (or prior to calling do_bootm_states,
>explicitly) the process, bootm_disable_interrupts() is called prior to
>announce_and_cleanup() which
If we look at the path that bootm/booti take when preparing to boot the
OS, we see that as part of (or prior to calling do_bootm_states,
explicitly) the process, bootm_disable_interrupts() is called prior to
announce_and_cleanup() which is where udc_disconnect() /
board_quiesce_devices() /
On Fri, Nov 19, 2021 at 01:12:43PM -0500, Tom Rini wrote:
> On Fri, Nov 19, 2021 at 03:33:21PM +0100, Linus Walleij wrote:
>
> > When using a recent kernel with a bunch of compiled-in
> > stuff the kernel image easily becomes bigger than 8 MB
> > yielding this error:
> >
> > Loading Kernel
On Fri, Nov 19, 2021 at 06:52:57AM -0600, Adam Ford wrote:
> On Thu, Nov 18, 2021 at 3:30 PM Tom Rini wrote:
> >
> > On Thu, Nov 18, 2021 at 03:26:40PM -0600, Adam Ford wrote:
> > > On Thu, Nov 18, 2021 at 3:12 PM Tom Rini wrote:
> > > >
> > > > On Wed, Nov 17, 2021 at 08:08:10AM -0600, Adam
This converts the following to Kconfig:
CONFIG_VIDEO_LOGO
Note that this option depends on CONFIG_DM_VIDEO now, since cfb_console is
deprecated. The only relevant code is now in splash.c
Drop the check for DM_VIDEO in that file.
Signed-off-by: Simon Glass
---
README
At present it is possible to show a logo on the display but it requires
some board configuration and an image.
This series aims to make this easier, by showing a logo automatically if
there is a display but no splash screen.
The logo is embedded in U-Boot and takes approximately 7KB of space.
If `sb_load_cmdfile()` fails to open the configuration file it will jump
to error handling where the code will try to `fclose()` the FILE pointer
which is NULL causing `mkimage` to segfault.
This patch removes the `fclose()` since `fopen()` always returns NULL
instead of the file descriptor when
This driver is obsolete and only used by nokia_rx51. It should be deleted.
For now, drop the VIDEO_LOGO code to avoid confusion with the new
implementation.
Signed-off-by: Simon Glass
---
drivers/video/cfb_console.c | 325 +---
1 file changed, 1 insertion(+),
Enable this for boards with a display, unless they are using the SPLASH
feature.
This shows a U-Boot logo on boards with a display, which seems like a
useful thing.
Signed-off-by: Simon Glass
---
configs/gurnard_defconfig | 1 +
configs/tbs2910_defconfig | 1 +
drivers/video/Kconfig | 1 +
Convert the current preprocessor macros to C code.
Signed-off-by: Simon Glass
---
drivers/video/video_bmp.c | 97 ---
1 file changed, 49 insertions(+), 48 deletions(-)
diff --git a/drivers/video/video_bmp.c b/drivers/video/video_bmp.c
index
It is useful to boot coreboot (with U-Boot as a payload) from qemu. Add
a sample script to show how to do this.
Signed-off-by: Simon Glass
---
scripts/build-cb.sh | 19 +++
1 file changed, 19 insertions(+)
create mode 100755 scripts/build-cb.sh
diff --git
Add a compressed 16bpp BMP file and a test to cover this.
Signed-off-by: Simon Glass
---
.gitattributes | 1 +
configs/sandbox_defconfig | 1 +
configs/sandbox_flattree_defconfig | 1 +
test/dm/video.c| 24
Enable this feature so that a splash screen can be provided.
Signed-off-by: Simon Glass
---
board/coreboot/coreboot/coreboot.c | 20 ++--
include/configs/coreboot.h | 3 +++
include/configs/x86-common.h | 6 +-
3 files changed, 26 insertions(+), 3
Show the U-Boot logo by default. This is only 7KB in size so seems like
a useful default for boards that enable a display.
If SPLASH_SCREEN is enabled, it is not enabled by default, so as not to
conflict with that feature.
Also disable it for tests, since we don't want to complicate the output.
This is useful for showing a logo when booting from qemu.
Signed-off-by: Simon Glass
---
common/splash_source.c | 14 ++
include/splash.h | 1 +
include/virtio.h | 1 +
3 files changed, 16 insertions(+)
diff --git a/common/splash_source.c b/common/splash_source.c
At present this uses RGB555 format for blitting to a display. Sandbox uses
565 and that seems to be more normal for BMP as well. Update the code
accordingly and add a test.
Note that this likely breaks the theadorable board so we may need to
discuss supporting both formats.
Signed-off-by: Simon
We don't need this anymore since we use the BMP palette directly. Drop it.
Signed-off-by: Simon Glass
---
drivers/video/video-uclass.c | 23 ---
drivers/video/video_bmp.c| 22 --
include/video.h | 2 --
3 files changed, 47 deletions(-)
Drop the unnecessary brackets.
Signed-off-by: Simon Glass
---
drivers/video/video_bmp.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/video/video_bmp.c b/drivers/video/video_bmp.c
index 466c0f54363..ba36589effb 100644
---
Update this code to use write_pix8() rather than writing the pixels only
for a single supported display depth. This allows us to support any
depth.
Add some more tests too.
Signed-off-by: Simon Glass
---
drivers/video/video_bmp.c | 49 +--
test/dm/video.c
At present the code that writes to a pixel is quite convoluted. It uses a
colour map which is in the uclass and the same code is repeated in
different places within video_bmp_display().
As a first step, create a function which can write a pixel from the
bitmap, no matter what the display depth.
These functions are not used with driver model, nor in any U-Boot boards.
Drop them and inline the code.
Signed-off-by: Simon Glass
---
drivers/video/video_bmp.c | 22 +-
1 file changed, 5 insertions(+), 17 deletions(-)
diff --git a/drivers/video/video_bmp.c
On sandbox these addresses are 16 hex digits log so we need more space
for the debug string. Update it.
Signed-off-by: Simon Glass
---
drivers/video/video-uclass.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/video-uclass.c
The intention is for the copy base to start halfway through the
frame-buffer area. At present is it actually below the frame buffer,
which could have anything in it (probably it is malloc space). Fix
this.
Signed-off-by: Simon Glass
---
drivers/video/sandbox_sdl.c | 2 +-
1 file changed, 1
This does not work with sandbox at present. Fix it up to use map_sysmem()
to convert an address to a pointer.
Signed-off-by: Simon Glass
---
cmd/unzip.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/cmd/unzip.c b/cmd/unzip.c
index 3d1f5f3ac10..bc6cee06043 100644
---
Add a few more tests for BMP rendering. Use a back door into the sandbox
SDL driver to adjust the resolution at runtime.
The truetype code does not support 8bpp. Add this so that the display is
not blank when running in this mode.
Signed-off-by: Simon Glass
---
arch/sandbox/include/asm/test.h
If U-Boot starts with the frame buffer set to 16bpp but then runs a test
that uses 32bpp, there is not enough space. Update the driver to use the
maximum possible frame-buffer size, to avoid this.
Signed-off-by: Simon Glass
---
drivers/video/sandbox_sdl.c | 18 +-
1 file
The video driver uses this for debugging, but if used before relocation it
crashes at present. Avoid trying to output debugging before the console is
ready.
Signed-off-by: Simon Glass
---
common/console.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
When unit tests are run they currently create a new window. Update the
code so that the old one is removed first. This avoids the confusion as to
which one is active.
Signed-off-by: Simon Glass
---
arch/sandbox/cpu/sdl.c | 33 +++--
At present sandbox only supports 16 and 32bpp depths, since those are the
easy ones with SDL.
We can support other depths by manually converting the pixel formats. Add
support for this, to enable an 8ppp (monochrome) format.
Signed-off-by: Simon Glass
---
arch/sandbox/cpu/sdl.c | 65
On Fri, Nov 19, 2021 at 03:33:21PM +0100, Linus Walleij wrote:
> When using a recent kernel with a bunch of compiled-in
> stuff the kernel image easily becomes bigger than 8 MB
> yielding this error:
>
> Loading Kernel Image
> Image too large: increase CONFIG_SYS_BOOTM_LEN
> Must RESET
Hi!
It seems that lib/physmem.c is either not used or used only by sandbox
(not sure).
Do we need CONFIG_PHYSMEM at all?
Note x86 has its own implementation that is always present for all platforms.
--
With Best Regards,
Andy Shevchenko
-amlogic.git
tags/u-boot-amlogic-2029
for you to fetch changes up to 28f70cfcfd82ac509c8da772b74e5dc2df795fd2:
configs: meson64_android: add PANIC stage for SYSTEM fails (2021-11-19
18:15:26 +0100)
- pinctrl: Correct the driver GPIO
Hi Tom,
Please pull for master
The following changes since commit 3144ba23bf4649f699078259fdf2e5cb4eab8f53:
Merge branch '2021-11-15-assorted-fixes' (2021-11-16 14:23:30 -0500)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-tpm/ tags/tpm-19112021
On 11/18/21 7:03 AM, Michal Simek wrote:
Using clock-frequency property to define desired clock speed for
controllers.
Signed-off-by: Michal Simek
---
drivers/mmc/zynq_sdhci.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/mmc/zynq_sdhci.c
On 11/18/21 7:09 AM, Michal Simek wrote:> SGMII configuration depends on proper
GT setting that's why when node has
phys property call PSGTR driver to configure it properly.
Signed-off-by: Michal Simek
---
drivers/net/zynq_gem.c | 16
1 file changed, 16 insertions(+)
When using a recent kernel with a bunch of compiled-in
stuff the kernel image easily becomes bigger than 8 MB
yielding this error:
Loading Kernel Image
Image too large: increase CONFIG_SYS_BOOTM_LEN
Must RESET board to recover
Fix this by bumping to SZ_16MB.
Cc: Stephan Gerhold
Define LOG_CATEGORY to allow filtering with log command
for generic clock and CCF clocks.
This patch also change existing printf, debug and pr_ macro
to log_ or dev_ macro.
Signed-off-by: Patrick Delaunay
---
drivers/clk/clk-composite.c| 3 +++
drivers/clk/clk-divider.c | 6 +-
Reorder include files in the U-Boot expected order:
the common.h header should always be first,
followed by other headers in order,
then headers with directories,
then local files.
It is a preliminary step for next patch.
Signed-off-by: Patrick Delaunay
---
drivers/clk/clk-composite.c| 6
Hello Michael,
> -Original Message-
> From: Michael Nazzareno Trimarchi
> Sent: Thursday, November 18, 2021 10:48 PM
> To: ZHIZHIKIN Andrey
> Cc: Ye Li ; Stefano Babic ; Fabio Estevam
> ; u-boot@lists.denx.de; Ariel D'Alessandro
> ; linux-amar...@amarulasolutions.com; Anthony
> Brandon
On Thu, Nov 18, 2021 at 3:30 PM Tom Rini wrote:
>
> On Thu, Nov 18, 2021 at 03:26:40PM -0600, Adam Ford wrote:
> > On Thu, Nov 18, 2021 at 3:12 PM Tom Rini wrote:
> > >
> > > On Wed, Nov 17, 2021 at 08:08:10AM -0600, Adam Ford wrote:
> > >
> > > > On Fri, Oct 22, 2021 at 2:36 PM Adam Ford
Hi,
On 11/18/21 20:54, Tom Rini wrote:
On Thu, Nov 18, 2021 at 08:04:22PM +0100, Wolfgang Denk wrote:
Dear Tom,
In message <2028162920.GH24579@bill-the-cat> you wrote:
It is perfectly OK for U-Boot to start with a random MAC address,
use this for a while, and change it so something
The Khadas VIM3 and VIM3L board are well supported in AOSP[1].
However, there is no mainline U-Boot support for it.
The U-Boot used in AOSP is based on a vendor tree [2]
Add a special defconfig for each board to allow booting Android.
Note: this is a copy-paste of khadas-vim3{l}_defconfig
meson64_android.h also relies on CMD_AB_SELECT so enable that as well.
Signed-off-by: Guillaume La Roque
Signed-off-by: Mattijs Korpershoek
---
configs/khadas-vim3_android_ab_defconfig | 2 ++
configs/khadas-vim3l_android_ab_defconfig | 2 ++
include/configs/khadas-vim3_android.h | 16
Add all the necessary bits to flash and boot Android for both Khadas
VIM3 and VIM3L boards.
For Android instructions, refer to [1]
[1] https://source.android.com/setup/build/devices#vim3_and_vim3l_boards
Signed-off-by: Guillaume La Roque
Signed-off-by: Mattijs Korpershoek
---
In AOSP, the bot VIM3 and VIM3L have 2 bootloader flavors,
depending on A/B enablement.
For example, for vim3l, the naming is:
- u-boot_kvim3l_noab.bin : legacy support
- u-boot_kvim3l_ab.bin : A/B support
Prepare a defconfig to support u-boot_kvim3_ab.bin and
u-boot_kvim3l_ab.bin.
This is
This allows us to define extra board variables, such as "board" and
"board_name".
Signed-off-by: Guillaume La Roque
Signed-off-by: Mattijs Korpershoek
---
include/configs/meson64_android.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/include/configs/meson64_android.h
The VIM3 and VIM3L boards are well supported in the
Android Open Source project via the yukawa [1] platform.
Their U-Boot version, despite being public [2] is not in mainline.
[1] https://android.googlesource.com/device/amlogic/yukawa
[2]
The IPCC mailbox is only used for communication with M4 firmware but
it is not used in the stm32 remoteproc driver; it was planed but the
support of this mailbox in remoteproc for STM32MP15x is dropped.
So the associated drivers and config CONFIG_STM32_IPCC can be
deactivated to reduce the U-Boot
hi Wolfgang
tnx for your comments
On Fri, Nov 19, 2021 at 3:49 PM Wolfgang Denk wrote:
>
> Dear Artem,
>
> In message <2029043647.1251416-1-...@khadas.com> you wrote:
> > Add possibility setup env variable with additional resolving vars inside
> > value.
>
> Hm... if you want to evaluate
Add a message on probe in driver model core when the default
pinctrl selection failed.
This message is displayed only when the pinctrl API is
implemented, i.e. when result is not ENOSYS.
Signed-off-by: Patrick Delaunay
Reviewed-by: Simon Glass
---
drivers/core/device.c | 16
Use the return value ENOSYS for unsupported API
- pinctrl_generic_set_state
- pinctrl_select_state
Signed-off-by: Patrick Delaunay
Reviewed-by: Simon Glass
---
include/dm/pinctrl.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/dm/pinctrl.h
57 matches
Mail list logo
