Hi,
This has been discussed in a few forums and the main VBE doc has been
presented in a U-Boot contributor call recently.
I have now written up a proposal for the mechanics of bootmethod /
bootflow for review. Think of it as a newer version of Distro Boot.
I'm not sure how to format it for the
Hi Ilias,
On Mon, 12 Jul 2021 at 03:28, Ilias Apalodimas
wrote:
>
> On Mon, 12 Jul 2021 at 11:40, Masahisa Kojima
> wrote:
> >
> > Hi Simon,
> >
> > On Sun, 11 Jul 2021 at 09:01, Simon Glass wrote:
> > >
> > > Hi Masahisa,
> > >
> > > On Wed, 7 Jul 2021 at 20:21, Masahisa Kojima
> > > wrote:
Hi Masahisa,
On Mon, 12 Jul 2021 at 02:40, Masahisa Kojima
wrote:
>
> Hi Simon,
>
> On Sun, 11 Jul 2021 at 09:01, Simon Glass wrote:
> >
> > Hi Masahisa,
> >
> > On Wed, 7 Jul 2021 at 20:21, Masahisa Kojima
> > wrote:
> > >
> > > On Wed, 7 Jul 2021 at 22:47, Heinrich Schuchardt
> > > wrote:
Add a new 'quiet' argument to mmc_get_op_cond() function which avoids
printing error message when SD/eMMC card is not detected.
Espressobin and mx6cuboxi boards use this function for detecting presence
of eMMC and therefore it is expected and normal that eMMC does not have to
be connected. So
Ensure that 'env default -a' always set correct value to $fdtfile, even
when custom user variable is already stored in non-volatile env storage
(means that env_get("fdtfile") call returns non-NULL value).
As default value is now correctly set like if specified at compile time in
Use function mmc_get_op_cond() instead of mmc_init() for detecting presence
of eMMC. Documentation for this function says that it could be used to
detect the presence of SD/eMMC when no card detect logic is available.
This function is also used by mx6cuboxi board for detecting presence of eMMC.
Hi Jan,
On Wed, 14 Jul 2021 at 03:53, Jan Kiszka wrote:
>
> On 05.07.21 17:29, Simon Glass wrote:
> > Hi Jan,
> >
> > On Sun, 27 Jun 2021 at 23:40, Jan Kiszka wrote:
> >>
> >> On 27.06.21 20:18, Simon Glass wrote:
> >>> Hi Jan,
> >>>
> >>> On Sun, 27 Jun 2021 at 12:01, Jan Kiszka wrote:
>
This commit adds the comment of the TCG Specification
efi_tcg2.h file refers, and comment for the structure.
Signed-off-by: Masahisa Kojima
---
Changes in v2:
- newly create commit from v2
include/efi_tcg2.h | 51 ++
1 file changed, 51 insertions(+)
Refactor efi_append_scrtm_version() to use common
function for adding eventlog and extending PCR.
Signed-off-by: Masahisa Kojima
---
Changes in v2:
no update
lib/efi_loader/efi_tcg2.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/lib/efi_loader/efi_tcg2.c
TCG PC Client PFP spec requires to measure
"Exit Boot Services Invocation" if ExitBootServices() is invoked.
Depending upon the return code from the ExitBootServices() call,
"Exit Boot Services Returned with Success" or "Exit Boot Services
Returned with Failure" is also measured.
Signed-off-by:
TCG PC Client PFP spec requires to measure "Boot"
and "BootOrder" variables, EV_SEPARATOR event prior
to the Ready to Boot invocation.
Since u-boot does not implement Ready to Boot event,
these measurements are performed when efi_start_image() is called.
TCG spec also requires to measure
TCG PC Client PFP spec requires to measure the secure
boot policy before validating the UEFI image.
This commit adds the secure boot variable measurement
of "SecureBoot", "PK", "KEK", "db" and "dbx".
Note that this implementation assumes that secure boot
variables are pre-configured and not be
TCG PC Client PFP spec says "The Log Area Minimum Length
for the TCG event log MUST be at least 64KB." in ACPI chapter.
This commit increase the buffer size to 64KB.
Signed-off-by: Masahisa Kojima
---
Changes in v2:
- increase buffer size to 64KB, it follows the minimum size
requirement
This patch series add the support of measurement
descibed in TCG PC Client PFP spec(Version 1.05 Revision 23).
Eventlog generated with this patch series are tested on
the aarch64 based machine(Socionext Developerbox) and fTPM
running on OP-TEE.
The eventlog result is almost same result as the one
On 14/07/21 3:09 pm, Jan Kiszka wrote:
> On 14.07.21 11:29, Lokesh Vutla wrote:
>> Hi Jan,
>>
>> On 12/06/21 1:12 am, Jan Kiszka wrote:
>>> This is the baseline support for the SIMATIC IOT2050 devices.
>>>
>>> Changes in v3:
>>> - rebased
>>> - addressed several checkpatch warnings
>>> -
On Wed, Jul 14, 2021 at 2:22 PM Bin Meng wrote:
>
> Hi Zong,
>
> On Fri, Jul 9, 2021 at 4:06 PM Zong Li wrote:
> >
> > This patch reverts the following commits:
> > - 4b4159d0f3 ("riscv: dts: add dts for unmatched rev1")
> > - ffe9a394df ("board: sifive: support spl multi-dtb on unmatched
Hi Zong,
On Fri, Jul 9, 2021 at 4:06 PM Zong Li wrote:
>
> This patch reverts the following commits:
> - 4b4159d0f3 ("riscv: dts: add dts for unmatched rev1")
> - ffe9a394df ("board: sifive: support spl multi-dtb on unmatched board")
>
> We won't plan to support unmatched that the revision
On 14.07.21 11:55, Jagan Teki wrote:
> On Tue, Jul 13, 2021 at 2:45 PM Frieder Schrempf wrote:
>>
>> From: Frieder Schrempf
>>
>> The driver depends on DM_SPI and if it's not available (e. g. in SPL),
>> then we should not try to build it as this will fail.
>>
>> Signed-off-by: Frieder Schrempf
On Tue, Jul 13, 2021 at 2:45 PM Frieder Schrempf wrote:
>
> From: Frieder Schrempf
>
> The driver depends on DM_SPI and if it's not available (e. g. in SPL),
> then we should not try to build it as this will fail.
>
> Signed-off-by: Frieder Schrempf
> ---
> drivers/spi/Makefile | 2 +-
> 1
On 7/5/21 6:29 PM, Simon Glass wrote:
Hi Nandor,
On Mon, 28 Jun 2021 at 03:44, Nandor Han wrote:
On 6/26/21 9:30 PM, Simon Glass wrote:
Hi Nandor,
On Thu, 10 Jun 2021 at 07:57, Nandor Han wrote:
RTC devices could provide battery-backed memory that can be used for
storing the reboot mode
On 05.07.21 17:29, Simon Glass wrote:
> Hi Jan,
>
> On Sun, 27 Jun 2021 at 23:40, Jan Kiszka wrote:
>>
>> On 27.06.21 20:18, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Sun, 27 Jun 2021 at 12:01, Jan Kiszka wrote:
On 26.06.21 20:29, Simon Glass wrote:
> Hi,
>
> On Fri, 11
On 14.07.21 11:29, Lokesh Vutla wrote:
> Hi Jan,
>
> On 12/06/21 1:12 am, Jan Kiszka wrote:
>> This is the baseline support for the SIMATIC IOT2050 devices.
>>
>> Changes in v3:
>> - rebased
>> - addressed several checkpatch warnings
>> - a few #ifdef -> IS_ENABLED conversions
>> -
Hi Jan,
On 12/06/21 1:12 am, Jan Kiszka wrote:
> This is the baseline support for the SIMATIC IOT2050 devices.
>
> Changes in v3:
> - rebased
> - addressed several checkpatch warnings
> - a few #ifdef -> IS_ENABLED conversions
> - comment marker for SPDK identifier in .S file
> -
At the moment pressing the volume down key does not actually launch
fastboot. This is because setting "bootdelay" to "-1" actually
disables autoboot and drops to the U-Boot console. It does not execute
the "bootcmd".
The correct value for "bootdelay" here would be "-2", which disables
the delay
For some reason, the DragonBoard 410c aborts autoboot immediately if
U-Boot is started without LK. It looks like it picks up a single broken
character via serial and therefore believes a key was pressed to abort
autoboot.
After some debugging, it seems like adding some delay after pinctrl
setup
I spent some more time testing the "U-Boot without LK" changes [1] on DB410c
last week and noticed some minor issues that are fixed in this patch series.
Ideally they should be applied on top of [1]. However, actually PATCH 1/3
and PATCH 2/3 are completely unrelated to [1] and could be also
The DragonBoard 410c has proprietary firmware from Qualcomm that
reserves 8 MiB of memory for tz/smem/hyp/rmtfs/rfsa from 0x8600
to 0x8680. I'm not aware of any ATF (ARM Trusted Firmware) port
for DB410c that would reserve 30 MiB of memory at the end of RAM.
I suspect the comment might
Hello folks,
Any insight would be highly appreciated.
On 7/13/21 2:53 PM, Ahsan Hussain wrote:
On 7/13/21 2:25 PM, Mark Rutland wrote:
On Tue, Jul 13, 2021 at 02:15:08PM +0500, Ahsan Hussain wrote:
Hello,
I'm dumbfounded by a seemingly unrelated early kernel hang/failing
to boot
when
-JJ since the email would bounce.
On 13/07/21 11:02PM, Patrick Wildt wrote:
> The macro should be passed a state, which should be passed
> to the actual function. Otherwise using that macro would
> yield a build error.
Nitpick: Lines are too short. The usual convention is 72 chars and you
seem
Hi,
On 7/14/21 9:37 AM, Jorge Ramirez-Ortiz, Foundries wrote:
> On 13/07/21, Jorge Ramirez-Ortiz, Foundries wrote:
>> On 13/07/21, Jorge Ramirez-Ortiz, Foundries wrote:
>>> On 13/07/21, Jorge Ramirez-Ortiz, Foundries wrote:
On 13/07/21, Michal Simek wrote:
>
>
> On 7/13/21 11:25
On 13/07/21, Jorge Ramirez-Ortiz, Foundries wrote:
> On 13/07/21, Jorge Ramirez-Ortiz, Foundries wrote:
> > On 13/07/21, Jorge Ramirez-Ortiz, Foundries wrote:
> > > On 13/07/21, Michal Simek wrote:
> > > >
> > > >
> > > > On 7/13/21 11:25 AM, Jorge Ramirez-Ortiz, Foundries wrote:
> > > > > On
CONFIG_NET_MULTI has been removed long time ago by commit 795428fc679f
("net: remove CONFIG_NET_MULTI") but 4 boards were added later which wasn't
found. The patch is removing this reference from 4 boards.
Signed-off-by: Michal Simek
---
include/configs/SBx81LIFKW.h| 1 -
From: Raju Kumar Pothuraju
Add kernel_comp_addr_r, kernel_comp_size env variables for zynqmp and
versal to be able to use the compressed kernel Image(.gz,.bz2,.lzma,.lzo)
using booti command.
Signed-off-by: Raju Kumar Pothuraju
Signed-off-by: Michal Simek
---
include/configs/xilinx_versal.h
It is default value which had been converted by commit 432e39806805
("include/configs: drop default definitions of CONFIG_SYS_PBSIZE"). That's
why also remove it.
Signed-off-by: Michal Simek
---
include/configs/xilinx_versal.h | 2 --
1 file changed, 2 deletions(-)
diff --git
On 7/2/21 12:40 PM, Ashok Reddy Soma wrote:
> This patch set adds Xilinx AXI Multirate MAC(MRMAC) driver support.
>
> This MRMAC is a high performance, low latency, adaptable Ethernet integrated
> hard IP. This can be configured up to four ports with MAC rates from 10GE to
> 100GE.
>
>
Hi Zong,
On Fri, Jul 09, 2021 at 04:06:01PM +0800, Zong Li wrote:
> This patch reverts the following commits:
> - 4b4159d0f3 ("riscv: dts: add dts for unmatched rev1")
> - ffe9a394df ("board: sifive: support spl multi-dtb on unmatched board")
>
> We won't plan to support unmatched that the
On Wed, 7 Jul 2021 21:43:48 -0400, Tom Rini wrote:
> The usbtty functionality is not currently used on these two platforms,
> disable it.
Applied to https://source.denx.de/u-boot/custodians/u-boot-ti.git for-rc,
thanks!
[1/1] arm: omap4: Disable USB_TTY and related options
On Tue, 13 Jul 2021 10:11:39 -0400, Tom Rini wrote:
> Swap out the TI-centric "envboot" logic for the generic distro_bootcmd
> logic for the bootcmd we run before trying to do something more complex
> involving additional firmware, etc.
Applied to
On Thu, 10 Jun 2021 19:01:47 -0400, Tom Rini wrote:
> Remove the environment support for various legacy boot methods. With
> this, we will now default to booting any distribution that follows the
> generic distro boot framework and no longer attempt to boot various
> legacy (to this SoC)
On Thu, 1 Jul 2021 10:27:43 -0400, Tom Rini wrote:
> Swap out the TI-centric "envboot" logic for the generic distro_bootcmd
> logic for the bootcmd we run before trying to do something more complex
> involving additional firmware, etc.
Applied to
On Thu, 1 Jul 2021 09:26:10 -0400, Tom Rini wrote:
> Remove the environment support for various legacy boot methods. With
> this, we will now default to booting any distribution that follows the
> generic distro boot framework and no longer attempt to boot various
> legacy (to this SoC)
On Fri, 11 Jun 2021 16:13:32 +, gireesh.hirem...@in.bosch.com wrote:
> address the v3 review comments
>
> >There are some build errors with this series, can you take a look?:
>
On Tue, 22 Jun 2021 12:04:26 +0530, Lokesh Vutla wrote:
> This series adds support for remoteproc driver for PRUSS in AM65 SoCs.
>
> Changes since v1:
> - Fixed checkpatch warnings
>
> Keerthy (2):
> soc: ti: pruss: Add a platform driver for PRUSS in TI SoCs
> remoteproc: pru: Add support
On Thu, 24 Jun 2021 12:16:14 -0500, Gowtham Tammana wrote:
> The `struct udevice *` reference is needed for either of the
> K3_LOAD_SYSFW, K3_AM64_DDRSS config guards. Adding the missing
> K3_AM64_DDRSS guard.
Applied to https://source.denx.de/u-boot/custodians/u-boot-ti.git for-rc,
thanks!
On Fri, 25 Jun 2021 14:23:05 -0500, Adam Ford wrote:
> Several functions in omap3/board.c are only used in that file, and
> two of them are only called when certain conditions are true in an
> ifdef. Rearange these functions to also be inside the ifdef and
> make them static.
>
> Before:
>
>
On Wed, 16 Jun 2021 22:08:19 +0530, Aswath Govindraju wrote:
> The following series of patches,
> - Update the location of TF-A
> - Indicate reserved locations for DMSC code and secure proxy
>
> changes since v1:
> - Moved the load address of TF-A to 0x701c to account for future
>
On Sat, 26 Jun 2021 08:42:58 -0500, Adam Ford wrote:
> SPL is really tight on space, so decrease a little memory that we
> allocate in order to fix boot hang.
Applied to https://source.denx.de/u-boot/custodians/u-boot-ti.git for-rc,
thanks!
[1/1] configs: am3517_evm: Fix boot hang
On Fri, 25 Jun 2021 13:57:17 -0500, Adam Ford wrote:
> The AM3517 uses SYS_MALLOC_F_LEN of size 0x3000, but the rest of
> the OMAP3 boards from LogicPD / BeaconEmbedded use 0x4000, but
> they don't boot SPL.
>
> Reduce the malloc size to restore booting.
Applied to
On 14/07/21 12:48 am, Tom Rini wrote:
> On Mon, Jul 12, 2021 at 11:50:24AM +0530, Kishon V;ijay Abraham I wrote:
>
>> Move j721e document from board/ti/j721e/README to
>> doc/board/ti/j721e_evm.rst after converting it to RST format.
>>
>> Signed-off-by: Kishon Vijay Abraham I
> [snip]
>> diff
101 - 149 of 149 matches
Mail list logo
