Hi,
On 6/21/21 7:27 PM, Jorge Ramirez-Ortiz, Foundries wrote:
> hi Michal,
>
> Is secure boot supported using SPL? or is there a plan for it (maybe a
> branch somewhere that I can work from and contribute to?).
I have it on my list but haven't had a time to dig into it yet.
>
> ATM looking int
Hello,
Does anyone have a feedback on that fix ?
I think the location of the fix is important to be discussed too as it needs to
be generic but not overlap with existing checks.
Have a nice day,
Timothée Cercueil
‐‐‐ Original Message ‐‐‐
On Tuesday, June 15th, 2021 at 10:53 AM, Timothée
Hello Stefano,
> -Original Message-
> From: Stefano Babic
> Sent: Monday, June 21, 2021 1:36 PM
> To: ZHIZHIKIN Andrey ;
> sba...@denx.de
> Cc: U-Boot-Denx ; Peng Fan ;
> Fabio Estevam
> Subject: Re: [PATCH 1/3] imx8mm: configs: enable distro default features
>
> On 17.06.21 18:03, ZHIZ
Hi,
On 6/22/21 4:24 PM, litchi.pi wrote:
> Hello,
> Does anyone have a feedback on that fix ?
> I think the location of the fix is important to be discussed too as it needs
> to be generic but not overlap with existing checks.
> Have a nice day,
Reviewed-by: Jaehoon Chung
Best Regards,
Jaehoon
On Fri, Jun 18, 2021 at 11:19:11AM +0300, Ramon Fried wrote:
> Reviewed-by: Ramon Fried
Ramon, could you please take these patches through your tree? Thanks.
Hello,
I'm using u-boot v2020.01 and run on cm4 model it boots fine just
report that model is unknown:
DRAM: 948 MiB
RPI: Board rev 0x14 outside known range
RPI Unknown model (0xa03140)
I checked and in later releases there is added support for cm4 but
what I'm missing is devicetree blob. In ma
As 'part_get_info_by_name' now returns more status codes than just
-1 to indicate failure, we need to update the return value check.
Signed-off-by: Anders Dellien
---
cmd/part.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/part.c b/cmd/part.c
index 3395c17b89..e0463b5a
Hi again
El jue, 17 jun 2021 a las 15:07, Alvaro Gamez
() escribió:
>
> Hi!
>
> I'm trying to use buildroot to generate a system for the Digilent
> Genesys ZU board, which is based on the zynqmp SOC.
> I'm having trouble getting it to boot, and I was hoping I could get
> some guidance on what to d
On 22/06/21, Michal Simek wrote:
> Hi,
>
> On 6/21/21 7:27 PM, Jorge Ramirez-Ortiz, Foundries wrote:
> > hi Michal,
> >
> > Is secure boot supported using SPL? or is there a plan for it (maybe a
> > branch somewhere that I can work from and contribute to?).
>
> I have it on my list but haven't h
On 6/22/21 12:42 PM, Alvaro Gamez wrote:
> Hi again
>
> El jue, 17 jun 2021 a las 15:07, Alvaro Gamez
> () escribió:
>>
>> Hi!
>>
>> I'm trying to use buildroot to generate a system for the Digilent
>> Genesys ZU board, which is based on the zynqmp SOC.
>> I'm having trouble getting it to boot,
From: Chao Zeng
When operating the write-protection flash,spi_flash_std_write() and
spi_flash_std_erase() would return wrong result.The flash is protected,
but write or erase the flash would show "OK".
Check the flash write protection state if the write-protection has enbale
before operating the
Tpm test cases relies on tpm device setup. Provide an environment
variable "env__tpm_device_test_skip = True" to skip the test case
if tpm device is not present.
Only needed will have to add variable to the py-test framework.
Test runs successfully even this variable is absent.
Signed-off-by: T Ka
Hi Michal,
El mar, 22 jun 2021 a las 13:16, Michal Simek () escribió:
>
>
>
> On 6/22/21 12:42 PM, Alvaro Gamez wrote:
> > Hi again
> >
> > El jue, 17 jun 2021 a las 15:07, Alvaro Gamez
> > () escribió:
> >>
> >> Hi!
> >>
> >> I'm trying to use buildroot to generate a system for the Digilent
> >>
Hi,
On 6/22/21 6:24 AM, Kunihiko Hayashi wrote:
> This adds serial parameters that include stop bit mode, parity mode,
> and character length. Mark parity and space parity modes are not
> supported.
>
> Signed-off-by: Kunihiko Hayashi
> ---
> drivers/serial/serial_zynq.c | 64
> +++
On Tue, Jun 22, 2021 at 07:33:21AM +0800, Bin Meng wrote:
> MSYS2 Windows build started to fail since yesterday (Jun 21):
>
> checking keyring...
> checking package integrity...
> error: gcc-libs: signature from "David Macek " is
> unknown trust
> :: File /var/cache/pacman/pkg/gcc-libs-1
On Tue, Jun 22, 2021 at 07:33:21AM +0800, Bin Meng wrote:
> MSYS2 Windows build started to fail since yesterday (Jun 21):
>
> checking keyring...
> checking package integrity...
> error: gcc-libs: signature from "David Macek " is
> unknown trust
> :: File /var/cache/pacman/pkg/gcc-libs-1
At present the block device creation happens in the NVMe uclass
driver post_probe() phase. In preparation to support multiple
namespaces, we should issue namespace identify before creating
block devices but that touches the underlying hardware hence it
is not appropriate to do such in the uclass dr
At present for each namespace there is a block device created for it.
There is no issue if the number of supported namespaces reported from
the NVMe device is only 1.
Since QEMU commit 7f0f1acedf15 ("hw/block/nvme: support multiple namespaces"),
the number of supported namespaces reported has been
At present there is an offset of one added during the creation of
block device. This can be very confusing as we wanted to encode the
namespace id in the block device name but namespae id cannot be zero.
This changes to use the namespace id directly in the block device
name, eliminating the offset
A udevice's priv space is cleared in alloc_priv() in the DM core.
Don't do it again in its probe() routine.
Signed-off-by: Bin Meng
---
Changes in v2:
- new patch: Don't clear nvme blk device's priv space
drivers/nvme/nvme.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/nvme/nvme
mode_select_num_blocks and mode_select_block_len in 'struct nvme_ns'
are not useful. Drop them.
Signed-off-by: Bin Meng
---
Changes in v2:
- new patch: Drop useless members of 'struct nvme_ns'
drivers/nvme/nvme.c | 4 +---
drivers/nvme/nvme.h | 2 --
2 files changed, 1 insertion(+), 5 deletio
This converts the existing README.nvme to reST, and puts it under
the develop/driver-model/ directory.
Signed-off-by: Bin Meng
---
Changes in v2:
- new patch: Convert README.nvme to reST
doc/develop/driver-model/index.rst| 1 +
.../driver-model/nvme.rst}| 25 +
This was missed when NVMe support was initially brought to U-Boot
back in 2017. Add an entry for it and list myself as the maintainer.
Signed-off-by: Bin Meng
---
Changes in v2:
- new patch: Add an entry for NVMe
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAIN
Hi,
On 6/22/21 2:43 PM, Alvaro Gamez wrote:
> Hi Michal,
>
> El mar, 22 jun 2021 a las 13:16, Michal Simek () escribió:
>>
>>
>>
>> On 6/22/21 12:42 PM, Alvaro Gamez wrote:
>>> Hi again
>>>
>>> El jue, 17 jun 2021 a las 15:07, Alvaro Gamez
>>> () escribió:
Hi!
I'm trying to us
Hi Alex,
On Mon, 24 May 2021 at 13:59, Alex G. wrote:
>
>
>
> On 5/21/21 2:39 PM, Simon Glass wrote:
> > Hi Alex,
> >
> > On Thu, 20 May 2021 at 18:07, Alex G. wrote:
> >>
> >>
> >>
> >> On 5/20/21 6:17 PM, Simon Glass wrote:
> >>> Hi Alex,
> >>>
> >>> On Thu, 20 May 2021 at 17:13, Alex G. wrot
On Mon, 24 May 2021 at 14:23, Alexandru Gagniuc wrote:
>
> Host tool features, such as mkimage's ability to sign FIT images were
> enabled or disabled based on the target configuration. However, this
> misses the point of a target-agnostic host tool.
>
> A target's ability to verify FIT signatures
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> wdt_start() does the "no ->start? return -ENOSYS" check, don't
> open-code that in wdt_expire_now().
>
> Also, wdt_start() maintains some global (and later some per-device)
> state, which would get out of sync with this direct method call -
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> The addition of .pre_probe and .per_device_auto made this look
> bad. Fix it.
>
> Signed-off-by: Rasmus Villemoes
> ---
> drivers/watchdog/wdt-uclass.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
Reviewed-by: Simon
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> As preparation for having the wdt-uclass provided watchdog_reset()
> function handle all DM watchdog devices, and not just the first such,
> introduce a uclass-owned struct to hold the reset_period and
> next_reset, so these become per-devi
On Tue, Jun 22, 2021 at 09:16:23PM +0800, Bin Meng wrote:
> This was missed when NVMe support was initially brought to U-Boot
> back in 2017. Add an entry for it and list myself as the maintainer.
>
> Signed-off-by: Bin Meng
>
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description: PGP si
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> In preparation for handling all DM watchdogs in watchdog_reset(), pull
> out the code which handles starting (or not) the gd->watchdog_dev
> device.
>
> Include the device name in various printfs.
>
> Signed-off-by: Rasmus Villemoes
> ---
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> A later refactoring will put most of initr_watchdog() into a
> .post_probe function, which means that all watchdog devices end up
> being subject to the auto-start functionality. For the unit tests, it
> is more convenient if the tests are
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> Check that the watchdog_reset() implementation in wdt-uclass behaves
> as expected:
>
> - resets all activated watchdog devices
> - leaves unactivated/stopped devices alone
> - that the rate-limiting works, with a per-device threshold
>
> S
On Mon, 31 May 2021 at 02:57, Michal Simek wrote:
>
> On ARM64 secure OS can run as 64bit or 32bit that's why it is necessary to
> record information about architecture that other code can read it and
> properly pass it to TF-A and start in 64bit or 32bit mode.
>
> Signed-off-by: Michal Simek
> -
Hi Rasmus,
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> A board can have and make use of more than one watchdog device, say
> one built into the SOC and an external gpio-petted one. Having
> wdt-uclass only handle the first is both a little arbitrary and
> unexpected.
>
> So change i
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> As a step towards handling all DM watchdogs in watchdog_reset(), use a
> per-device flag to keep track of whether the device has been started
> instead of a bit in gd->flags.
>
> We will still need that bit to know whether we are past
> ini
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> It seems that no other test has claimed gpio_a:7 yet, so use that.
>
> The only small wrinkle is modifying the existing wdt test to use
> uclass_get_device_by_driver() since we now have two UCLASS_WDT
> instances in play, so it's a little m
Hi,
On Mon, 31 May 2021 at 05:39, Chee, Tien Fong wrote:
>
> Hi Ley Foon,
>
> > -Original Message-
> > From: Ley Foon Tan
> > Sent: Friday, 14 May, 2021 5:13 PM
> > To: Lim, Elly Siew Chin
> > Cc: ZY - u-boot ; Marek Vasut ;
> > Tan, Ley Foon ; See, Chin Liang
> > ; Simon Goldschmidt
>
On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
wrote:
>
> A rather common kind of external watchdog circuit is one that is kept
> alive by toggling a gpio. Add a driver for handling such a watchdog.
>
> The corresponding linux driver apparently has support for some
> watchdog circuits which can be
On Mon, Jun 21, 2021 at 10:17 AM Bin Meng wrote:
>
> The existing intructions in the U-Boot on EFI doc do not work with
> the latest QEMU. Update the doc with the correct instructions, as
> well as using the new OVMF URL link.
>
> Signed-off-by: Bin Meng
> ---
>
> doc/develop/uefi/u-boot_on_efi.
Hi,
El mar, 22 jun 2021 a las 15:20, Michal Simek () escribió:
>
> Hi,
>
> On 6/22/21 2:43 PM, Alvaro Gamez wrote:
> > Hi Michal,
> >
> > El mar, 22 jun 2021 a las 13:16, Michal Simek () escribió:
> >>
> >>
> >>
> >> On 6/22/21 12:42 PM, Alvaro Gamez wrote:
> >>> Hi again
> >>>
> >>> El jue, 17 ju
From: Roland Gaudig
U-Boot uses almost everywhere hexadecimal numbers. But some bootargs
passed to Linux are expecting decimal numbers. As long as the values
are in the range 0 to 9 it is sufficient to just strip 0x from the
number. But for greater values a method for converting numbers to
decim
From: Roland Gaudig
This patch extends the setexpr command with a dec operator to
convert an input value to decimal.
Signed-off-by: Roland Gaudig
---
cmd/setexpr.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/cmd/setexpr.c b/cmd/setexpr.c
index e828be3
On Mon, Jun 21, 2021 at 10:48:17PM -0400, Da Xue wrote:
> This breaks the build if CONFIG_CMD_MBR is enabled. Christian Melki sent a
> patch but it didn't get picked up?
Ah. The commit message wasn't clear that it was reproducible problem
so it was on my list to look at / confirm at some point.
On 6/22/21 8:31 AM, Simon Glass wrote:
[snip]
+config TOOLS_USE_LIBCRYPTO
would HOST_LIBCRYPTO be better?
I had considered a shorter kconfig such as the above. Does it mean
(1) The build host has libcrypto available?
(2) We use the libcrypto on the host?
(3) There is a libcrypto
Chapter 23 of the EFI spec (rev 2.9) says:
"A specific updatable hardware firmware store must be represented by
exactly one FMP instance".
This is not the case for us, since both of our FMP protocols can be
installed at the same time because they are controlled by a single
'dfu_alt_info' env variab
From: Masami Hiramatsu
When running the efidebug capsule disk-update command, the efi_fmp_raw
protocol installation fails with 2 (EFI_INVALID_PARAMETER) as below.
This is because the code passes efi_root instead of the handle local var.
=> efidebug capsule disk-update
EFI: Call: efi_install_mult
We only install FMPs if a CapsuleUpdate is requested. Since we now have an
ESRT table which relies on FMPs to build the required information, it
makes more sense to unconditionally install them. This will allow userspace
applications (e.g fwupd) to make use of the ERST and provide us with files
w
On 6/22/21 5:40 AM, Anders Dellien wrote:
As 'part_get_info_by_name' now returns more status codes than just
-1 to indicate failure, we need to update the return value check.
Signed-off-by: Anders Dellien
---
cmd/part.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/c
On Mon, Jun 21, 2021 at 4:49 PM Vladimir Oltean wrote:
>
> On Mon, Jun 21, 2021 at 04:10:51PM -0700, Tim Harvey wrote:
> > Greetings,
> >
> > I've written a U-Boot phy driver for a Microchip KSZ9477 ethernet
> > switch that I submitted some time ago as an RFC [1] which simply
> > enables the ports
Hi Alex,
On Tue, 22 Jun 2021 at 08:13, Alex G. wrote:
>
> On 6/22/21 8:31 AM, Simon Glass wrote:
>
> [snip]
>
> >> +config TOOLS_USE_LIBCRYPTO
> >
> > would HOST_LIBCRYPTO be better?
>
> I had considered a shorter kconfig such as the above. Does it mean
> (1) The build host has libcrypto ava
Hi Roland,
On Tue, 22 Jun 2021 at 07:51, wrote:
>
> From: Roland Gaudig
>
> This patch extends the setexpr command with a dec operator to
> convert an input value to decimal.
>
> Signed-off-by: Roland Gaudig
> ---
>
> cmd/setexpr.c | 16 ++--
> 1 file changed, 14 insertions(+), 2 d
On 6/22/21 3:25 PM, Simon Glass wrote:
> Hi Roland,
>
> On Tue, 22 Jun 2021 at 07:51, wrote:
>>
>> From: Roland Gaudig
>>
>> This patch extends the setexpr command with a dec operator to
>> convert an input value to decimal.
>>
>> Signed-off-by: Roland Gaudig
>> ---
>>
>> cmd/setexpr.c | 16
Hi Simon,
Thanks for review.
>> - if (!CONFIG_IS_ENABLED(WATCHDOG_AUTOSTART)) {
>> - printf("WDT: Not starting %s\n", dev->name);
>> - return;
>> - }
>> -
>> - ret = wdt_start(dev, priv->timeout * 1000, 0);
>> - if (ret != 0) {
>> -
On 22/06/2021 15.31, Simon Glass wrote:
> On Thu, 27 May 2021 at 16:00, Rasmus Villemoes
> wrote:
>>
>> Check that the watchdog_reset() implementation in wdt-uclass behaves
>> as expected:
>>
>> - resets all activated watchdog devices
>> - leaves unactivated/stopped devices alone
>> - that the rat
Hi,
2021年6月22日(火) 23:39 Ilias Apalodimas :
>
> Chapter 23 of the EFI spec (rev 2.9) says:
> "A specific updatable hardware firmware store must be represented by
> exactly one FMP instance".
> This is not the case for us, since both of our FMP protocols can be
> installed at the same time because t
Hi Sean,
On Tue, 22 Jun 2021 at 13:30, Sean Anderson wrote:
>
>
>
> On 6/22/21 3:25 PM, Simon Glass wrote:
> > Hi Roland,
> >
> > On Tue, 22 Jun 2021 at 07:51, wrote:
> >>
> >> From: Roland Gaudig
> >>
> >> This patch extends the setexpr command with a dec operator to
> >> convert an in
Hi Tom,
Resend with new mail address that subscribed to u-boot list.
Please pull u-boot-mmc.
---
Revert fsl_esdhc_imx using VENDORSPEC_FRC_SDCLK_ON
Fix data read for dw_mmc
Increase minimum bus freq for mtk-sd
Minor cleanup
---
CI: https:/
> -Original Message-
> From: Ramon Fried [mailto:rfried@gmail.com]
> Sent: 2021年6月12日 7:47
> To: Z.Q. Hou
> Cc: Joe Hershberger ; U-Boot Mailing List
>
> Subject: Re: [PATCH] net: e1000: Fix Unchecked return value coverity
>
> On Fri, Jun 11, 2021 at 5:56 AM Z.Q. Hou wrote:
> >
>
On 22.06.21 22:28, Rasmus Villemoes wrote:
Hi Simon,
Thanks for review.
- if (!CONFIG_IS_ENABLED(WATCHDOG_AUTOSTART)) {
- printf("WDT: Not starting %s\n", dev->name);
- return;
- }
-
- ret = wdt_start(dev, priv->timeout * 1000, 0);
- if (re
Dear Roland,
In message <20210622135042.133904-2-roland.gaudig-...@weidmueller.com> you
wrote:
>
> This patch extends the setexpr command with a dec operator to
> convert an input value to decimal.
...
> + /* hexadecimal to decimal conversion: "setexpr name dec value" */
> + if (argc == 4
Dear Simon,
In message
you wrote:
>
> > > 0m123 ? ('m' for deciMal).
> >
> > Perhaps 0d123? Though I would prefer to remove many of the implicit
> > assumptions of hex input.
>
> Right, we can't use 'd' because it is valid hex.
>
> I believe hex is the right default. We just need an easy way to
63 matches
Mail list logo
