Akashi-san,
> > + {
> > + EFI_CERT_X509_SHA256_GUID,
> > + "sha256",
> > + 256,
>
> => SHA256_SUM_LEN * 8
>
Sure
> > + },
> > + {
> > + EFI_CERT_SHA256_GUID,
> > + "sha256",
> > + 256,
> > + },
> > + {
> > +
On Tue, Apr 19, 2022 at 10:54:14AM +0900, AKASHI Takahiro wrote:
> On Mon, Apr 18, 2022 at 09:07:23PM +0300, Ilias Apalodimas wrote:
> > The previous patch adds support for rejecting images when the sha384/512
> > of an x.509 certificate is present in dbx. Update the sandbox selftests
> >
> >
Add Nuvoton BMC NPCM7xx/NPCM8xx timer driver.
Signed-off-by: Jim Liu
Signed-off-by: Stanley Chu
---
Changes for v3:
- no changes since v2
Changes for v2:
- coding style cleanup
---
drivers/timer/Kconfig | 9 +++
drivers/timer/Makefile | 1 +
drivers/timer/npcm-timer.c | 115
Add Nuvoton BMC NPCM7xx/NPCM8xx uart driver
Signed-off-by: Jim Liu
Signed-off-by: Stanley Chu
---
Changes for v3:
- no changes since v2
Changes for v2:
- coding style cleanup
- Add support for setting parent clock
---
drivers/serial/Kconfig | 9 ++
drivers/serial/Makefile
Add clock controller driver for NPCM750
Signed-off-by: Jim Liu
Signed-off-by: Stanley Chu
---
Changes for v3:
- no changes since v2
Changes for v2:
- combine NPCM750 and NPCM845 clk driver.
---
drivers/clk/Makefile | 1 +
drivers/clk/nuvoton/Makefile
Add basic support for the Nuvoton NPCM750 EVB (Poleg).
Signed-off-by: Jim Liu
---
Changes for V3:
- remove unused define in poleg.h
- add define to defconfig
Changes for v2:
- coding style cleanup
- remove reset.c and use sysreset function
- re-generate the defconfig
- remove
The patch series add basic supoorts for NPCM750, which
is Nuvoton's 3th-generation BMC (Baseboard Management Controller).
Add drivers to support Clock,Timer,Uart for NPCM7xx SoC.
the NPCM750 computing subsystem comprises a dual-core ARM a9
at 800MHz speed with L1/L2 caches
dts,dtsi and
HW accelerated hash operations are giving incorrect hash output.
so invalidate cache lines to avoid cache overwriting in DDR memory region.
caam_hash()
-moved address alignment check in the beginning of function.
-added invalidate_dcache_range for pout buffer before running descriptor.
Fixes:
On Mon, Apr 18, 2022 at 11:09:38PM -0400, Tom Rini wrote:
> On Tue, Apr 19, 2022 at 10:01:54AM +0900, AKASHI Takahiro wrote:
>
> > Some defconfig enables CMD_PART even if none of any partition table
> > types (CONFIG_*_PARTITION) are enabled.
> > This will lead to the size growth in SPL/TPL code
On Tue, Apr 19, 2022 at 10:01:54AM +0900, AKASHI Takahiro wrote:
> Some defconfig enables CMD_PART even if none of any partition table
> types (CONFIG_*_PARTITION) are enabled.
> This will lead to the size growth in SPL/TPL code since disk/part.c
> will be compiled in any way.
> We will change
On 19/04/22 01:25, Alper Nebi Yasak wrote:
On 06/04/2022 15:29, 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
On 19/04/22 01:26, Alper Nebi Yasak wrote:
On 06/04/2022 15:29, Neha Malcom Francis wrote:
For K3 devices that require a sysfw image, add entry for SYSFW. It can
contain system firmware image that can be packaged into sysfw.itb by
binman. The method ReadBlobContents in sysfw.py runs the TI K3
On Mon, Apr 18, 2022 at 09:07:23PM +0300, Ilias Apalodimas wrote:
> The previous patch adds support for rejecting images when the sha384/512
> of an x.509 certificate is present in dbx. Update the sandbox selftests
>
> Signed-off-by: Ilias Apalodimas
> ---
> changes since v2:
> - None
> changes
Ilias,
On Mon, Apr 18, 2022 at 09:07:22PM +0300, Ilias Apalodimas wrote:
> Currently we don't support sha384/512 for the X.509 certificate
> in dbx. Moreover if we come across such a hash we skip the check
> and approve the image, although the image might needs to be rejected.
>
> Rework the
In most of all cases, we can avoid using blk_desc which is expected
to be private to udevice(UCLASS_BLK), that is, the data should not
be manipulated outside the device driver unless really needed.
Now efi_disk's internally use dev_read/write() interfaces
if CONFIG_PARTITIONS is enabled.
In include/blk.h, Simon suggested:
===>
/*
* These functions should take struct udevice instead of struct blk_desc,
* but this is convenient for migration to driver model. Add a 'd' prefix
* to the function operations, so that blk_read(), etc. can be reserved for
* functions with the correct
When we create an efi_disk device with an UEFI application using driver
binding protocol, the 'efi_driver' framework tries to create
a corresponding block device(UCLASS_BLK/IF_TYPE_EFI). This will lead to
calling a PROBE callback, efi_disk_probe().
In this case, however, we don't need to create
Add efi_disk_probe() function.
This function creates an efi_disk object for a raw disk device (UCLASS_BLK)
and additional objects for related partitions (UCLASS_PARTITION).
So this function is expected to be called through driver model's "probe"
interface every time one raw disk device is
This function is expected to be called, in particular from dm's pre_remove
hook, when associated block devices no longer exist.
Add efi_disk_remove() function.
This function removes an efi_disk object for a raw disk device (UCLASS_BLK)
and related objects for its partitions (UCLASS_PARTITION).
When we create an efi_disk device with an UEFI application using driver
binding protocol, the 'efi_driver' framework tries to create
a corresponding block device(UCLASS_BLK/IF_TYPE_EFI). This will lead to
calling a PROBE callback, efi_disk_probe().
In this case, however, we don't need to create
In the next commit, CONFIG_EFI_SETUP_EARLY will become mandated
in order to support dynamic enumeration of efi_disk objects.
This can, however, be problematic particularly in case of file-based
variable storage (efi_variable.c, default).
Non-volatile variables are to be restored from EFI system
Now that all the block device drivers have enable a probe hook, we will
call part_create_block_devices() to enumerate all the partitions and
create associated udevices when a block device is detected.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
---
drivers/block/blk-uclass.c | 4
NOTE: probably we have to update config dependencies,
in particular, SPL/TPL_PRINTF?
With this new function, UCLASS_PARTITION devices will be created as
child nodes of UCLASS_BLK device.
Signed-off-by: AKASHI Takahiro
---
disk/Makefile | 3 +
disk/disk-uclass.c | 153
The new test covers all tag-related interfaces.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
---
test/dm/Makefile | 1 +
test/dm/tag.c| 84
2 files changed, 85 insertions(+)
create mode 100644 test/dm/tag.c
diff --git
Some basic stuff about tag support is explained under
doc/devlop/driver-model.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
---
doc/develop/driver-model/design.rst | 20
1 file changed, 20 insertions(+)
diff --git a/doc/develop/driver-model/design.rst
ENOMEM is a more common error code for memory starvation.
Signed-off-by: AKASHI Takahiro
---
drivers/core/tag.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/core/tag.c b/drivers/core/tag.c
index 6829bcd8806c..22999193a5a3 100644
--- a/drivers/core/tag.c
+++
With this patch set[1] applied, UEFI subsystem maintains a list of its
disk objects dynamically at runtime based on block device's probing.
(See "issues" and "prerequisite" below.)
[1] https://github.com/t-akashi/u-boot/tree/efi/dm_disk
For instance,
=> dm tree
Class Index Probed Driver
Under the current Kconfigs, disk/part.c will be compiled in even if none of
partition table types are enabled. This will lead to the size growth of SPL
/TPL code.
With this patch, CONFIG_PARTITIONS is selected only if, at least, one of
CONFIG_*_PARTITION is enabled.
Signed-off-by: AKASHI
Now we can build efi_loader with block device support (CONFIG_BLK) and
without CONFIG_PARTITIONS.
So change Makefile.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_loader/Makefile b/lib/efi_loader/Makefile
Some defconfig enables CMD_PART even if none of any partition table
types (CONFIG_*_PARTITION) are enabled.
This will lead to the size growth in SPL/TPL code since disk/part.c
will be compiled in any way.
We will change disk/Kconfig later so that CONFIG_PARTITIONS is only
enabled when, at least,
In the current implementation, partition table support (either GPT or DOS)
is not mandatory. So CONFIG_PARTITION_UUIDS should not be enabled
(selected) unconditionally.
Fixes: commit 17f8cda505e3 ("efi_loader: set partition GUID in device path for
SIG_TYPE_GUID")
Signed-off-by: AKASHI Takahiro
Since host_get_dev_errr() is defined in drivers/block/sandbox.c,
the associated function prototype should be in a more appropriate
header file.
Fixes: commit 4101f6879256 ("dm: Drop the block_dev_desc_t typedef")
Signed-off-by: AKASHI Takahiro
---
include/part.h| 1 -
Since CONFIG_[SPL|TPL]_PARTITIONS were introduced, part.h has not been
updated. Due to this, while the build won't fail, some functionality may
possibly break as some partition-related functions are nullified even
though some partition table types are enabled for SPL/TPL.
Fixes: commit
Some errno numbers are used in defining inline functions.
So "errno.h" should be explicitly included to avoid possible build errors.
Signed-off-by: AKASHI Takahiro
---
include/part.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/part.h b/include/part.h
index
This is a reworked version of my RFC[1].
When my patch[2] is applied, the size of SPL code on some platform might
exceed the limit of ROM size due to partition support code (disk/*) being
built in even if none of partition table types (CONFIG_*_PARTITION) is
enabled on that particular platform.
Hi Detlev,
On Mon, Apr 18, 2022 at 02:46:21PM -0400, Detlev Casanova wrote:
> Hi Daniel,
>
> The patch only checks the existence of the reserved-memory node.
>
> I guess that before, adding the reserved-memory node failed and so nothing
> else was happening. Now, the node is found and then, it
Loongson 1C is a cost-effective SOC chip for industrial control and
the Internet of Things. The Loongson 1C includes a floating-point
processing unit, supports multiple types of memory, and supports
high-capacity MLC NAND Flash. Loongson 1C provides developers with a
wealth of peripheral
On 06/04/2022 15:29, Neha Malcom Francis wrote:
> Explicit make commands were earlier used to generate tispl.bin image,
> now it is replaced using binman.
>
> Binman picks up and packages entries according to the description of
> entries given in the binman node in the device tree. The make
On 06/04/2022 15:29, Neha Malcom Francis wrote:
> K3 devices introduces the concept of centralized power, resource and
> security management to System Firmware. This is to overcome challenges
> by the traditional approach that implements system control functions on
> each of the processing units.
On 06/04/2022 15:29, 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.
>
> j721e-r5-binman.dtsi has
On 06/04/2022 15:29, Neha Malcom Francis wrote:
> For devices that require sysfw.itb, board config binary artifacts must
> be populated in the R5 output directory. These can be used by binman to
> package sysfw.itb.
>
> config.mk for mach-k3 updated to generate the required binaries using
>
On 06/04/2022 15:29, Neha Malcom Francis wrote:
> For K3 devices that require a sysfw image, add entry for SYSFW. It can
> contain system firmware image that can be packaged into sysfw.itb by
> binman. The method ReadBlobContents in sysfw.py runs the TI K3
> certificate generation script to create
On 06/04/2022 15:29, 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,
The intent of fdt_fixup_reserved_memory is to reserve memory and prevent it from
being included in the kernel's linear map from U-Boot. This is done by creating
a no-map zone into reserved-memory region
no-map (optional) - empty property
Indicates the operating system must not create a virtual
This loads a mac address using a misc device using the nvmem interface.
Signed-off-by: Sean Anderson
---
(no changes since v1)
arch/sandbox/dts/test.dts | 9 -
drivers/misc/misc_sandbox.c | 3 +++
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git
This uses the nvmem API to load a mac address from an RTC.
Signed-off-by: Sean Anderson
Reviewed-by: Simon Glass
---
(no changes since v1)
arch/sandbox/dts/test.dts | 9 -
drivers/rtc/i2c_rtc_emul.c | 10 ++
2 files changed, 18 insertions(+), 1 deletion(-)
diff --git
This uses an i2c eeprom to load a mac address using the nvmem interface.
Signed-off-by: Sean Anderson
Reviewed-by: Simon Glass
---
(no changes since v1)
arch/sandbox/dts/test.dts | 9 -
drivers/misc/i2c_eeprom_emul.c | 4
2 files changed, 12 insertions(+), 1 deletion(-)
This adds support for reading mac addresses from the "mac-address" nvmem
cell. If there is no (local-)mac-address property, then we will try
reading from an nvmem cell.
For some existing examples of this property, refer to imx8mn.dtsi and
imx8mp.dtsi. Unfortunately, fuse drivers have not yet been
This adds support for "nvmem cells" as seen in Linux. The nvmem device
class in Linux is used for various assorted ROMs and EEPROMs. In this
sense, it is similar to UCLASS_MISC, but also includes
UCLASS_I2C_EEPROM, UCLASS_RTC, and UCLASS_MTD. New drivers corresponding
to a Linux-style nvmem device
This enables NVMEM for all sandbox defconfigs, enabling it to be used in
unit tests in the next few commits.
Signed-off-by: Sean Anderson
Reviewed-by: Simon Glass
---
(no changes since v1)
configs/sandbox64_defconfig| 1 +
configs/sandbox_defconfig | 1 +
i2c_eeprom_ops->write uses a const buf, so use one for the wrapper
function as well.
Signed-off-by: Sean Anderson
Reviewed-by: Simon Glass
---
(no changes since v1)
drivers/misc/i2c_eeprom.c | 3 ++-
include/i2c_eeprom.h | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff
This prevents some conflicts when running sandbox with -D, since the
"rom" mac address will be random and won't match the environment. We
still need to keep addresses for eth1 and eth6 in the environment,
because dm_test_eth_rotate expects to be able to disable them by
removing their envaddr
DSA interfaces use the same mac address for each interface, unless
instructed otherwise. Just set eth4addr and let eth2addr and eth7addr be
set automatically.
Signed-off-by: Sean Anderson
Reviewed-by: Simon Glass
---
(no changes since v1)
board/sandbox/sandbox.env | 1 -
1 file changed, 1
Instead of reading a pseudo-rom mac address from the device tree, just use
whatever we get from write_hwaddr. This has the effect of using the mac
address from the environment (or from the device tree, if it is
specified).
Signed-off-by: Sean Anderson
Reviewed-by: Simon Glass
Acked-by: Ramon
This adds a test to make sure that all the ethernet interfaces have
their addresses read properly. At the moment everything is read from the
environment, but the next few commits will add additional sources.
Signed-off-by: Sean Anderson
Reviewed-by: Simon Glass
---
Changes in v3:
- Move patch
The phy_eth0 interface introduced in f3dd213e15 ("net: introduce helpers to
get PHY ofnode from MAC") uses a globally-administered address. Switch to
using a locally-administered address, and add it to the sandbox
environment, like the others.
Signed-off-by: Sean Anderson
---
Changes in v3:
-
Commit f3dd213e15 ("net: introduce helpers to get PHY ofnode from MAC")
changed the ethernet sequence assignment from
uclass 36: ethernet
0 * eth@10002000 @ 05813460, seq 0
1 * eth@10003000 @ 05813550, seq 5
2 * sbe5 @ 05813640, seq 3
3 * eth@10004000 @ 05813730, seq 6
4 * dsa-test-eth
This adds support for the nvmem-cells properties cropping up in manyb
device trees. This is an easy way to load configuration, version
information, or calibration data from a non-volatile memory source. For
more information, refer to patch 6 ("misc: Add support for nvmem
cells").
For the moment I
On 18/04/22 8:26 pm, Andrew Davis wrote:
> On 4/15/22 9:09 AM, Vignesh Raghavendra wrote:
>> Add info of boot flow and build steps for AM62x SK.
>>
>> Signed-off-by: Vignesh Raghavendra
>> ---
>> doc/board/ti/am62x_sk.rst | 231 ++
>
>
> This isn't
Hi Gaurav,
On Mon, Apr 18, 2022 at 6:30 AM Gaurav Jain wrote:
> if (!IS_ALIGNED((uintptr_t)pbuf, ARCH_DMA_MINALIGN) ||
> !IS_ALIGNED((uintptr_t)pout, ARCH_DMA_MINALIGN)) {
> puts("Error: Address arguments are not aligned\n");
> return -EINVAL;
On 4/18/22 1:03 PM, Tom Rini wrote:
> On Mon, Apr 04, 2022 at 03:30:32PM -0400, Sean Anderson wrote:
>
>> This adds a test to make sure that all the ethernet interfaces have
>> their addresses read properly. At the moment everything is read from the
>> environment, but the next few commits
The previous patch adds support for rejecting images when the sha384/512
of an x.509 certificate is present in dbx. Update the sandbox selftests
Signed-off-by: Ilias Apalodimas
---
changes since v2:
- None
changes since RFC:
- new patch
test/py/tests/test_efi_secboot/conftest.py| 6 +++
Currently we don't support sha384/512 for the X.509 certificate
in dbx. Moreover if we come across such a hash we skip the check
and approve the image, although the image might needs to be rejected.
Rework the code a bit and fix it by adding an array of structs with the
supported GUIDs, len and
Apologies for the noise. Feel free to ignore this, I had a new
version with updated changelog. I'll post them shortly
On Mon, 18 Apr 2022 at 08:53, Ilias Apalodimas
wrote:
>
> Currently we don't support sha384/512 for the X.509
> certificate To-Be-Signed contents. Moreover if we come across
From: Fabio Estevam
The imx8mn_evk target have been converted to use binman.
With the binman approach the ATF load address is described via
devicetree, so remove the now unneeded instruction of exporting
ATF_LOAD_ADDR.
Signed-off-by: Fabio Estevam
---
doc/board/nxp/imx8mn_evk.rst | 1 -
1
From: Fabio Estevam
There is no reason for disabling I-cache and D-cache
in SPL.
Remove the unneeded CONFIG_SPL_SYS_ICACHE_OFF and
CONFIG_SPL_SYS_DCACHE_OFF options.
Signed-off-by: Fabio Estevam
---
configs/imx8mn_evk_defconfig | 2 --
1 file changed, 2 deletions(-)
diff --git
On Mon, Apr 04, 2022 at 03:30:32PM -0400, Sean Anderson wrote:
> This adds a test to make sure that all the ethernet interfaces have
> their addresses read properly. At the moment everything is read from the
> environment, but the next few commits will add additional sources.
>
> Signed-off-by:
On 4/15/22 9:09 AM, Vignesh Raghavendra wrote:
Add info of boot flow and build steps for AM62x SK.
Signed-off-by: Vignesh Raghavendra
---
doc/board/ti/am62x_sk.rst | 231 ++
This isn't specific to the SK, more the AM62x in general, suggest name
modified caam descriptor to support black key blob.
Signed-off-by: Gaurav Jain
---
cmd/blob.c| 12
drivers/crypto/fsl/desc.h | 1 +
drivers/crypto/fsl/fsl_blob.c | 21 +
drivers/crypto/fsl/jobdesc.c | 24 +++-
On 4/18/22 00:16, Adam Ford wrote:
Most, if not all of the imx8m[mnp] boards enable the SoC clock
driver. The CLK_IMX8MQ isn't necessarily required yet, but as
the new power domain driver will assume it is present. To simply
this, enable the respective clock drivers when a given imx8m SoC
is
HW accelerated hash operations are giving incorrect hash output.
so invalidate cache lines to avoid cache overwriting in DDR memory region.
caam_hash()
-moved address alignment check in the beginning of function.
-added invalidate_dcache_range for pout buffer before running descriptor.
Fixes:
Hi Simon,
A bit late on this, but at least I found it...
On Wed, Mar 16, 2022 at 10:15:34AM +1300, Simon Glass wrote:
> Hi Ilias,
>
> On Tue, 15 Mar 2022 at 00:34, Ilias Apalodimas
> wrote:
> >
> > Hi Simon,
> >
> > On Mon, 14 Mar 2022 at 20:24, Simon Glass wrote:
> > >
> >
> > [...]
> >
> >
Hi Tom,
Thank you for evaluating the code growth.
On Fri, Apr 15, 2022 at 11:01:48PM -0400, Tom Rini wrote:
> On Fri, Apr 15, 2022 at 04:11:56PM +0900, AKASHI Takahiro wrote:
> > We see some increase of spl code size due to partition support (disk/*)
> > while none of particular partition types
On Fri, Apr 15, 2022 at 10:21:39AM +0200, Heinrich Schuchardt wrote:
> On 4/15/22 09:11, AKASHI Takahiro wrote:
> > We see some increase of spl code size due to partition support (disk/*)
> > while none of particular partition types (CONFIG_SPL_XXX_PARTITION) are
> > enabled.
> > With this patch
On Sat, 16 Apr 2022 at 16:32, Heinrich Schuchardt wrote:
>
> On 3/24/22 14:54, Masahisa Kojima wrote:
> > Provide u16 string version of strlcat().
> >
> > Signed-off-by: Masahisa Kojima
> > Reviewed-by: Simon Glass
> > ---
> > Changes in v4:
> > - add blank line above the return statement
> >
>
Enable DM_SERIAL for both U_Boot and the SPL. The uart4 and its pinmux
are already marked with u-boot,dm-spl but we need to move the call to
preloader_console_init() after spl_init() to avoid a board hang
as dm can't be used until after spl_init().
Remove the manual config of the UART pinmux now
76 matches
Mail list logo
