On Fri, 15 Sept 2023 at 15:32, Ilias Apalodimas
wrote:
>
> Hi Kojima-san,
>
> > > > + efi_handle_t *image_handle)
> > > > +{
> > > > + efi_status_t ret;
> > > > + efi_handle_t bm_handle;
> > > > + struct efi_handler *handler;
> > > > + struct e
On jeu., sept. 14, 2023 at 10:55, Simon Glass wrote:
> Phrases like 'Enable support for' are pointless since this is an option
> which enables things. Drop that part so it is easier to follow.
>
> Signed-off-by: Simon Glass
Reviewed-by: Mattijs Korpershoek
> ---
>
> (no changes since v1)
>
>
Hi Maxim,
On Thu, 14 Sept 2023 at 19:20, Maxim Uvarov wrote:
>
> changelog:
> v9: - added first patch describing git submodule for lwip. So
> the build procedure is:
> git submodule init
> git submodule update
> make
>
Kojima-san
[...]
>
> We just followed the EDK2 reference implementation.
>
> > IOW if we pick this up, can we also use it on the efibootmgr code and scan
> > all disks on the fly instead of adding boot options?
>
> Yes, it is possible, but I'm not sure scanning all the disks on the fly
> is a goo
On Fri, 15 Sept 2023 at 14:07, Ilias Apalodimas
wrote:
> Hi Maxim,
>
> On Thu, 14 Sept 2023 at 19:20, Maxim Uvarov
> wrote:
> >
> > changelog:
> > v9: - added first patch describing git submodule for lwip. So
> > the build procedure is:
> > git submodule ini
From: Lukas Funke
Currently the pcap_prog struct variable is pointing to 0x3004 which is
incorrect according to [1]. The variable should point to 0x3000.
[1]
https://www.xilinx.com/htmldocs/registers/ug1087/ug1087-zynq-ultrascale-registers.html#csu___pcap_prog.html
Signed-off-by: Lukas Funke
+CC Jose who's maintaining the metadata spec from Arm side.
On Fri, 15 Sept 2023 at 02:38, Tom Rini wrote:
>
> On Thu, Sep 14, 2023 at 04:41:43PM -0600, Simon Glass wrote:
> > Hi Rob,
> >
> > On Wed, 13 Sept 2023 at 16:39, Rob Herring wrote:
> [snip]
> > > I don't think we should decide what to
DTSOs are stored in vendor specific directories in Linux.
Add the vendor prefix to the path to load the overlay correctly.
Signed-off-by: Ravi Gunasekaran
---
include/env/ti/mmc.env | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/env/ti/mmc.env b/include/env/ti/mmc.en
This series adds the EFI HTTP boot support.
User can add the URI device path with "efidebug boot add" command.
efibootmgr handles the URI device path, download the
specified file using wget, mount the downloaded image with
blkmap, then boot with the default file(e.g. EFI/BOOT/BOOTAA64.EFI).
This v
This introduces the valid range check to store the received
blocks using lmb. The same logic is implemented in tftp.
Signed-off-by: Masahisa Kojima
---
net/wget.c | 80 +-
1 file changed, 73 insertions(+), 7 deletions(-)
diff --git a/net/wget.
Current wget takes the target uri in this format:
":" e.g.) 192.168.1.1:/bar
The http server ip address must be resolved before
calling wget.
This commit adds the utility function runs wget with dhs.
User can call wget with the uri like "http://foo/bar";.
Signed-off-by: Masahisa Kojima
---
in
User needs to call several functions to create the ramdisk
with blkmap.
This adds the utility function to create blkmap device and
mount the ramdisk.
Signed-off-by: Masahisa Kojima
Reviewed-by: Simon Glass
---
drivers/block/Makefile| 1 +
drivers/block/blkmap.c| 15 --
This supports to boot from the URI device path.
When user selects the URI device path, bootmgr downloads
the file using wget into the address specified by loadaddr
env variable.
If the file is .iso or .img file, mount the image with blkmap
then try to boot with the default file(e.g. EFI/BOOT/BOOTAA
The buffer used to download the ISO image file must be
reserved to avoid the unintended access to the image.
For PE-COFF file case, this memory reservation is done
in LoadImage Boot Service.
Signed-off-by: Masahisa Kojima
---
include/efi_loader.h | 2 ++
lib/efi_loader/efi_bootmgr.c |
This adds the URI device path option for 'boot add' subcommand.
User can add the URI load option for downloading ISO image file
or EFI application through network. Currently HTTP is only supported.
Signed-off-by: Masahisa Kojima
---
cmd/efidebug.c | 50 +++
includ
This adds the description about HTTP Boot.
Signed-off-by: Masahisa Kojima
---
doc/develop/uefi/uefi.rst | 30 ++
1 file changed, 30 insertions(+)
diff --git a/doc/develop/uefi/uefi.rst b/doc/develop/uefi/uefi.rst
index a7a41f2fac..65eea89265 100644
--- a/doc/develop/
On 9/8/23 09:11, Michal Simek wrote:
Use proper project name in README, rst and comment.
Done in connection to commit bb922ca3eb4b ("global: Use proper project name
U-Boot (next)").
Signed-off-by: Michal Simek
---
Changes in v2:
- Revert change in tools/binman/entries.rst reported by Simon
This old patch was marked as deferred. Bring it back to life, to continue
towards the removal of common.h
Move this out of the common header and include it only where needed.
Signed-off-by: Simon Glass
---
arch/arm/lib/gic-v3-its.c | 1 +
arch/arm/mach-imx/imx8/fdt
Hi Michal,
> -Original Message-
> From: Simek, Michal
> Sent: Thursday, September 14, 2023 7:34 PM
> To: Abbarapu, Venkatesh ; u-
> b...@lists.denx.de
> Cc: ja...@amarulasolutions.com; g...@xilinx.com; Ashok Reddy Soma
>
> Subject: Re: [PATCH] spi: zynqmp_qspi: Workaround for small data
Change flush cache to invalidate cache and also fix
cache related issues are seen with small sized data reads.
Due to this, proper data is not read. Also some times
sf probe fails randomly.
Ashok Reddy Soma (1):
spi: zynqmp_qspi: Change flush cache to invalidate cache
Venkatesh Yadav Abbarapu (
From: Ashok Reddy Soma
Before DMA read, ideally cache should be invalidated, so that data from
memory will be updated to cache after DMA is completed. But
flush_dcache_range is being used which is incorrect. Change
flush_dcache_range to invalidate_dcache_range.
Signed-off-by: Ashok Reddy Soma
S
Cache related issues are seen with small sized data reads.
Due to this, proper data is not read. Also some times sf probe
fails randomly. To workaround this issue, invalidate dcache after read DMA
is triggered.
Signed-off-by: Ashok Reddy Soma
Signed-off-by: Venkatesh Yadav Abbarapu
---
drivers/
Current code expects bridge phy address at 0 which is not correct
expectation because bridge phy address is configurable.
That's why update the code to read reg property to figure it out
where bridge is and use it in phy creation code.
Signed-off-by: Michal Simek
Signed-off-by: Tejas Bhumkar
---
Hi Neil,
On Thu, Jun 22, 2023 at 06:19:33PM +0200, neil.armstr...@linaro.org wrote:
> On 21/06/2023 15:29, Alexey Romanov wrote:
> > Add support for hardware random number generator
> > of Amlogic Meson SoCs.
> >
> > Signed-off-by: Alexey Romanov
> > ---
> > arch/arm/dts/meson-a1.dtsi | 5
Hi Neil,
On Wed, Jun 21, 2023 at 04:29:53PM +0300, Alexey Romanov wrote:
> ao-secure node can be used to get information about the board,
> so, for example, using show_board_info() we can get following
> information for board with Meson A1 SoC:
>
> SoC: Amlogic Meson A1 (A113L) Revision 2c:a (1:
On 9/15/23 11:39, lukas.funke-...@weidmueller.com wrote:
From: Lukas Funke
Currently the pcap_prog struct variable is pointing to 0x3004 which is
incorrect according to [1]. The variable should point to 0x3000.
[1]
https://www.xilinx.com/htmldocs/registers/ug1087/ug1087-zynq-ultrascale-reg
On 9/14/23 12:06, Venkatesh Yadav Abbarapu wrote:
Read the tristate config for all the pins and display it.
ZynqMP> pinmux status MIO1
MIO1: slew:fast bias:enabled pull:up input:cmos drive:12mA
volt:1.8 tri_state:enabled
Signed-off-by: Venkatesh Yadav Abbarapu
---
drivers/pinctrl/p
Hi,
sandbox is getting bigger and bigger and I have reached the case that
adding some more functions ends up in CI loop failure. After some
investigation I found that flyrecord header have incorrect information
about data offset which is caused by incorrect alignment calculation.
That's why this s
tputq() requires variables to have 64bit width that's why make them 64bit
to clean alignment requirement.
Signed-off-by: Michal Simek
Reviewed-by: Simon Glass
---
(no changes since v1)
tools/proftool.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/proftool.c b/to
Flyrecord tracing data are page aligned that's why it is necessary to
calculate alignment properly. Because trace_clocks description is the part
of record length it is necessary to have information about length earlier.
Signed-off-by: Michal Simek
Reviewed-by: Simon Glass
---
(no changes since
Current alignment which is using 16 bytes is not correct in connection to
trace_clocks description and it's length.
That's why use start_addr variable and record proper size based on used
entries.
Fixes: be16fc81b2ed ("trace: Update proftool to use new binary format").
Signed-off-by: Michal Simek
On 9/6/2023 11:09 PM, Robin Murphy wrote:
> On 2023-09-06 19:10, Laurentiu Tudor wrote:
>>
>>
>> On 9/6/2023 8:21 PM, Robin Murphy wrote:
>>> On 2023-09-06 17:01, Laurentiu Tudor wrote:
MC being a plain DMA master as any other device in the SoC and
being live at OS boot time, as soon as
On 15:42-20230915, Ravi Gunasekaran wrote:
> DTSOs are stored in vendor specific directories in Linux.
what is dtso? kernel generates dtbo
> Add the vendor prefix to the path to load the overlay correctly.
>
> Signed-off-by: Ravi Gunasekaran
> ---
> include/env/ti/mmc.en
Hi Marek,
I was testing fastboot image download over usb for imx8mp (from usb
recovery patch of verdin-imx8mp) and i am having error messages on
endpoint request dequeue function of DWC3 gadget controller. However,
download is working fine, so this message may not be an error. They are
happening b
On 15/09/2023 15.05, João Paulo Silva Gonçalves wrote:
> Hi Marek,
>
> I was testing fastboot image download over usb for imx8mp (from usb
> recovery patch of verdin-imx8mp) and i am having error messages on
> endpoint request dequeue function of DWC3 gadget controller. However,
> download is work
There is no reason to setup ROM source if read_rom_hwaddr hook doesn't
exist or reading mac address fails. It is ending up with confusion about
mac address source.
It is nicely visible if you put mac address to DT as
local-mac-address = [ff ff ff ff ff ff];
but also save ethaddr to variables
seten
There is no reason to setup ROM source if read_rom_hwaddr hook doesn't
exist or reading mac address fails. It is ending up with confusion about
mac address source.
It is nicely visible if you put mac address to DT as
local-mac-address = [ff ff ff ff ff ff];
but also save ethaddr to variables
seten
On 9/10/23 5:36 PM, Simon Glass wrote:
Hi Andrew,
On Tue, 5 Sept 2023 at 12:15, Andrew Davis wrote:
On 9/5/23 1:09 PM, Andrew Davis wrote:
If the source .env file changes to one that is also older than
the generated env.txt file then it is not regenerated. This means
when switching board con
If the source .env file changes to one that is also older than the
generated env.txt file then the .env file is not regenerated. This
means when switching board configs we do not regenerate the env.
This can be tested with:
$ make j721e_evm_a72_defconfig
$ make # this may fail to complete but tha
Hi Rasmus,
Make sense to me. At least now I know that these messages
are not a critical error and will not give me problems
on the future.
Thanks for the patch too.
Regards,
João Paulo
On Fri, 2023-09-15 at 15:47 +0200, Rasmus Villemoes wrote:
> This message originated from outside your organiz
Amlogic MMC on the GX (and later) SoCs has been problematic for years,
especially with u-boot.
Linux has been fairly stable for a few years. It is using a fixed phase
setting with Core = 180, Tx = 0 and Rx = 0 (the latter cannot be set
starting from the v3 MMC IPs)
Still the results were not good
* Remove obsolete comments
* Set core phase to 180 regardless of the SoC like Linux
* Enable always-on clock
AML mmc driver has been working okay(ish) for a few years
The purpose of this patch is to bring u-boot closer to what
Linux is doing
Signed-off-by: Jerome Brunet
---
drivers/mmc/meson_gx
It has been reported that some devices have problems with a 180 degree
core phase. Setting 270 helped some of these devices. Other continue to
struggle (while it works fine with 180 in Linux ... :sigh:)
Poking around the HW, it seems that setting a 270 core phase during the
identification, then us
Currently, one can have both SYS_SPL_MALLOC=y and
SPL_SYS_MALLOC_SIMPLE=y.
However, while the former does make board_init_r() in spl.c call
mem_malloc_init(), that has no effect at all, because that just
updates a few bookkeeping variables, but as the linker map shows, the
latter setting has (as e
Currently, setting both CONFIG_SPL_SYS_MALLOC_SIMPLE and
CONFIG_SYS_SPL_MALLOC (but not CONFIG_SPL_STACK_R) doesn't work as
expected: The SIMPLE option means that all malloc etc. calls are
directed at build-time to the implementation in malloc_simple.c, but
the mem_alloc_init() call which is done i
I was running out of malloc() in SPL, and the message told me to look
at CONFIG_SYS_SPL_MALLOC_SIZE. So I did, and bumped it quite a bit,
but that had no effect whatsoever.
The reason for that was that I also have
CONFIG_SPL_SYS_MALLOC_SIMPLE=y. So while board_init_r() in spl.c duly
calls
mem_m
On Thu, Sep 14, 2023 at 10:55:38AM -0600, Simon Glass wrote:
> The view from 'make menuconfig' is confusing in places. This series aims
> to improve the top-level menu and also the boot menu.
>
> It also groups FDT-fixup options tegether, at least the ones I could fine.
>
> Finally this series m
On Thu, Sep 14, 2023 at 06:21:46PM -0600, Simon Glass wrote:
> This old patch was marked as deferred. Bring it back to life, to continue
> towards the removal of common.h
>
> Move this out of the common header and include it only where needed.
>
> Signed-off-by: Simon Glass
[snip]
> 317 files
Hi Tom,
On Fri, 15 Sept 2023 at 13:48, Tom Rini wrote:
>
> On Thu, Sep 14, 2023 at 06:21:46PM -0600, Simon Glass wrote:
>
> > This old patch was marked as deferred. Bring it back to life, to continue
> > towards the removal of common.h
> >
> > Move this out of the common header and include it onl
On 9/15/23 20:14, Bhupesh Sharma wrote:
Set my current personal email in the MAINTAINERS file.
Why this change so soon ? Did linaro raise any concerns about the
maintainership ?
On Fri, Sep 15, 2023 at 02:01:33PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Fri, 15 Sept 2023 at 13:48, Tom Rini wrote:
> >
> > On Thu, Sep 14, 2023 at 06:21:46PM -0600, Simon Glass wrote:
> >
> > > This old patch was marked as deferred. Bring it back to life, to continue
> > > towards the remo
Hi Tom, Hi Simon,
On Wed, Sep 13, 2023 at 9:53 PM Tony Dinh wrote:
>
> Hi Simon,
>
> On Wed, Sep 13, 2023 at 8:38 PM Simon Glass wrote:
> >
> > Hi Tom,
> >
> > On Wed, 13 Sept 2023 at 14:14, Tom Rini wrote:
> > >
> > > On Wed, Sep 13, 2023 at 12:56:53PM -0700, Tony Dinh wrote:
> > > > Hi Tom,
>
Set my current personal email in the MAINTAINERS file.
Signed-off-by: Bhupesh Sharma
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 536df4a896..b1f5ae0591 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1597,7 +1597,7 @@ T:
From: Mickaël Tansorier
`part` option is in hexadecimal, so information is missing in usage
documentation.
Callgraph for `part` parsing is :
do_load -> fs_set_blk_dev -> part_get_info_by_dev_and_name_or_num ->
blk_get_device_part_str -> hextoul (This is why it is hexadecimal)
Signed-off-by: Mic
On Fri, Sep 15, 2023 at 6:32 PM Tony Dinh wrote:
>
> Hi Tom, Hi Simon,
>
> On Wed, Sep 13, 2023 at 9:53 PM Tony Dinh wrote:
> >
> > Hi Simon,
> >
> > On Wed, Sep 13, 2023 at 8:38 PM Simon Glass wrote:
> > >
> > > Hi Tom,
> > >
> > > On Wed, 13 Sept 2023 at 14:14, Tom Rini wrote:
> > > >
> > > >
55 matches
Mail list logo
