On 10/12/2021 01.14, Simon Glass wrote:
> Hi,
>
> On Wed, 8 Dec 2021 at 11:10, Philippe REYNES
> wrote:
>>
>>
>> Everybody agrees with this proposal ?
>
> So long as this is not a shell script and is done with a binman entry, yes.
No, no and please no. Binman really isn't as wonderful and magi
Hi Michael
Le lun. 29 nov. 2021 à 18:47, Michael Walle a écrit :
> Hi Sahil,
>
> Am 2021-11-29 12:55, schrieb Sahil Malhotra (OSS):
> > Am 2021-11-17 19:11, schrieb Sahil Malhotra (OSS):
> >>> Could you please add some description what this is doing and for what
> >>> this is intended? To have a
With DM-efi_disk integration, we don't need to explicitly call
efi_disk_create_partitions().
The only thing to do is to associate an efi_disk object to
the corresponding udevice as we skip most of processing in
efi_disk_probe() by the previous commit ("efi_loader: disk: not create
BLK device for B
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 ano
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 ar
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 manupulated outside the device driver unless really needed.
Now efi_disk's internally use dev_read/write() interfaces.
Signed-off-by: AKASHI Takahiro
---
lib
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).
So
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 +
include/dm/uclass-id.h | 1 +
include/part.h
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 detected
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
---
drivers/block/blk-uclass.c | 4
1 file changed, 4 inser
With dm-tag feature, any U-Boot subsystem is allowed to associate
arbitrary number of data with a particular udevice. This can been
see as expanding "struct udevice" without modifying the definition.
As a first user, UEFI subsystem makes use of tags to associate
an efi_disk object with a block dev
From: Simon Glass
This is a draft implementation of event notification mechanism from Simon.
Under this scheme, any U-Boot subsystem can register some kind of callback
function to a particular event (more event types will be added later) and
that function will be invoked once the event is fired.
virtio_init() enumerates all the peripherals that are to be materialised
with udevices(UCLASS_VIRIO) and creates particular device instances
(UCLASS_BlK or whatever else) as children.
On the other hand, device_probe() won't be invoked against those resultant
udevices unlike other ordinary device dr
Due to a non-existing parameter name in macro's, use of those macro's will
cause a compiler error of "undefined reference".
Unfortunately, dm test doesn't fail because a wrong name ("&dev", hence it
is accidentally a valid name in the context of a caller site) is passed on.
Signed-off-by: AKASHI T
Every time an ide bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run
additional post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
Reviewed-b
Every time a sata bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run
additional post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
---
drive
Every time a nvme bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run
additional post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
Reviewed-b
Every time a mmc bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run
additional post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
---
driver
Every time a usb bus/port is scanned and a new device is detected,
we want to call device_probe() as it will give us a chance to run
additional post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
Reviewed-by
Every time a scsi bus/port is scanned and a new block device is detected,
we want to call device_probe() as it will give us a chance to run
additional post-processings for some purposes.
In particular, support for creating partitions on a device will be added.
Signed-off-by: AKASHI Takahiro
Revi
This function will be commonly used in block device drivers
in the succeeding patches.
Signed-off-by: AKASHI Takahiro
---
drivers/block/blk-uclass.c | 13 +
include/blk.h | 12
2 files changed, 25 insertions(+)
diff --git a/drivers/block/blk-uclass.c b/driv
In blk_get_device_by_str(), the comment says: "Updates the partition table
for the specified hw partition."
Since hw partition is supported only on MMC, it makes no sense to do so
for other devices.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
---
disk/part.c | 3 ++-
1 file changed,
# This is a kind of snapshot of my current work.
# I submit this to show my progress on this effort, and then
# I haven't addressed all the issues in this version.
# See the change history below.
The purpose of this RPC is to reignite the discussion about how UEFI
subystem would best be integrated
Hi Andrey,
> -Original Message-
> From: ZHIZHIKIN Andrey
> Sent: Wednesday, December 8, 2021 3:43 PM
> To: Sahil Malhotra (OSS) ; Michael Walle
>
> Cc: Clément Faure ; Gaurav Jain
> ; Pankaj Gupta ; Priyanka
> Jain ; u-boot@lists.denx.de; Varun Sethi
> ; Ye Li
> Subject: RE: [PATCH 1/2]
The 12/10/2021 00:15, Simon Glass wrote:
> Hi Jamin,
>
> On Wed, 8 Dec 2021 at 20:57, Jamin Lin wrote:
> >
> > Add to support rsa 30272 bits algorithm in tools
>
> 3072
>
Will fix
> > for image sign at host side and adds rsa 3027 bits
>
> 3072 ?
>
Will fix
> > verification in the image binary
Add to support rsa 3072 bits algorithm in tools
for image sign at host side and adds rsa 3072 bits
verification in the image binary.
Add test case in vboot for sha384 with rsa3072 algorithm testing.
Signed-off-by: Jamin Lin
---
include/u-boot/rsa.h| 1 +
lib/rsa/rsa-ver
Add to support rsa 3072 bits algorithm in tools
for make-image signing at host side and add rsa 3072
bits verification in the image binary.
v3:
- Fix typo
- Add test case in vboot for rsa3072 testing
v2:
- update to send a single patch
Jamin Lin (1):
rsa: adds rsa3072 algorithm
include/u-
On Thu, Dec 9, 2021 at 7:18 PM Andre Przywara wrote:
Hi Andre,
>
> On Thu, 9 Dec 2021 18:50:06 +0330
> Javad Rahimi wrote:
>
> Hi Javad,
>
> thanks for the patch!
>
> > When enabling the LED support for Cubieboard2 (SUN7I)
> > the uboot freezes in status_led_init() function.
> > It uses a stati
Hi Ivan,
On Thu, 9 Dec 2021 at 06:11, Ivan Mikhaylov wrote:
>
> From: Ivan Mikhaylov
>
> Add the 'missing-msg' for blobs for more detailed output on missing system
> firmware and SEBoot blobs.
>
> Signed-off-by: Ivan Mikhaylov
> ---
> arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 5 +
>
Hi Jamin,
On Wed, 8 Dec 2021 at 20:57, Jamin Lin wrote:
>
> Add to support rsa 30272 bits algorithm in tools
3072
> for image sign at host side and adds rsa 3027 bits
3072 ?
> verification in the image binary.
>
> Signed-off-by: Jamin Lin
> wq
> ---
> include/u-boot/rsa.h | 1 +
> lib/rsa
Hi,
On Wed, 8 Dec 2021 at 11:10, Philippe REYNES
wrote:
>
> Hi Rasmus,
>
> First, thanks for the feedback.
>
>
> Le 06/12/2021 à 09:23, Rasmus Villemoes a écrit :
> > On 17/11/2021 18.52, Philippe Reynes wrote:
> >> This commit adds a script gen_pre_load_header.sh
> >> that generate the header us
On Fri, Nov 19, 2021 at 6:04 PM Simon Glass wrote:
>
> This adds three new options with varying degree of interest / precedent.
Send these to devicetree-spec list so it's not in the flood of
devicetree-discuss.
>
> This being sent to the mailing list since it might attract more review.
> A PR wi
On 09/12/2021 05:32, Simon Glass wrote:
> On Tue, 7 Dec 2021 at 13:31, Alper Nebi Yasak
> wrote:
>> On 03/12/2021 06:31, Simon Glass wrote:
>>> On Thu, 25 Nov 2021 at 10:40, Alper Nebi Yasak
>>> wrote:
The RK3399 SoC needs to know the voltage value provided by some
regulators, which i
On 12/4/21 07:56, Simon Glass wrote:
Show the revision of this table as it can be important.
Alo update the 'efi table' entry to show the actual address of the EFI
%s/Alo/Also/
table rather than our table that points to it. This saves a step and the
intermediate table has nothing else in it.
On 12/4/21 07:56, Simon Glass wrote:
At present the 'efi' command only works in the EFI payload. Update it to
work in the app too, so the memory map can be examined.
cmd/efi.c seems to be duplicating function do_efi_show_memmap(). In a
future patch we should try to move to using common code for
On 12/4/21 07:56, Simon Glass wrote:
This provides access to EFI tables after U-Boot has exited boot services.
It is not needed in the app since boot services remain alive and we can
just call them whenever needed.
Add a comment to explain this.
Signed-off-by: Simon Glass
---
(no changes sinc
On 12/4/21 07:56, Simon Glass wrote:
The stub checks for failure with efi_init(). Add this for the app as well.
It is unlikely that anything can be done, but we may as well stop.
Signed-off-by: Simon Glass
---
(no changes since v1)
lib/efi/efi_app.c | 7 +--
1 file changed, 5 insertion
On 12/4/21 07:56, Simon Glass wrote:
Add a message here so that both paths of memory allocation are reported.
Signed-off-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- Use log_info() instead of printf()
lib/efi/efi_app.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
On 12/4/21 07:56, Simon Glass wrote:
At present only the backspace key is supported in U-Boot, when running as
an EFI app. Add support for arrows, home and end as well, to make the CLI
more friendly.
Signed-off-by: Simon Glass
---
(no changes since v1)
drivers/serial/serial_efi.c | 11 +
On 12/4/21 10:43, Heinrich Schuchardt wrote:
On 12/4/21 16:56, Simon Glass wrote:
When starting the app, locate all block devices and make them available
to U-Boot. This allows listing partitions and accessing files in
filesystems.
EFI also has the concept of 'disks', meaning boot media. For no
On 12/4/21 07:56, Simon Glass wrote:
Add a block driver which handles read/write for EFI block devices. This
driver actually already exists ('efi_block') but is not really suitable
for use as a real U-Boot driver:
- The operations do not provide a udevice
- The code is designed for running as pa
On 12/4/21 07:56, Simon Glass wrote:
At present UCLASS_EFI is used to represent an EFI filesystem among other
%s/UCLASS_EFI/UCLASS_EFI_LOADER/
things. The description of this uclass is "EFI managed devices" which is
pretty vague. The only driver that uses this uclass is in fact not a real
U-B
On 12/4/21 07:56, Simon Glass wrote:
These names are better used for access to devices provided by an EFI
layer. Use EFI_LOADER instead here, since these are only available in
U-Boot's EFI_LOADER layer.
Signed-off-by: Simon Glass
---
Changes in v5:
- Add new patch to resolve EFI/EFI_LOADER con
Signed-off-by: Potin Lai
---
arch/arm/dts/Makefile | 3 +-
arch/arm/dts/ast2600-bletchley.dts | 324 +
2 files changed, 326 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/dts/ast2600-bletchley.dts
diff --git a/arch/arm/dts/Makefile b/arch/arm
From: Ivan Mikhaylov
Add the 'missing-msg' for blobs for more detailed output on missing system
firmware and SEBoot blobs.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 5 +
tools/binman/missing-blob-help | 11 +++
2 files changed,
Hi Michael,
On Thu, Dec 09, 2021 at 05:32:51PM +0100, Michael Opdenacker wrote:
> Greetings,
>
> Documenting the issue and a workaround here in case other people
> encounter it, but if you have tips for fixing the issue in U-Boot, I'm
> interested of course!
>
> I noticed that the SAMA5D3 Xplain
Greetings,
Documenting the issue and a workaround here in case other people
encounter it, but if you have tips for fixing the issue in U-Boot, I'm
interested of course!
I noticed that the SAMA5D3 Xplained board didn't have the watchdog timer
enabled in the Linux DTS.
I submitted a patch to fix th
On Tue, 7 Dec 2021 at 07:11, Masahisa Kojima wrote:
>
> This commit modify efi_tcg2_register() to return the
> appropriate error.
> With this fix, sandbox will not boot because efi_tcg2_register()
> fails due to some missing feature in GetCapabilities.
> So disable sandbox if EFI_TCG2_PROTOCOL is
On Tue, 7 Dec 2021 at 07:11, Masahisa Kojima wrote:
>
> There are functions that calls tcg2_agile_log_append() outside
> of the TCG protocol invocation (e.g tcg2_measure_pe_image).
> These functions must to check that TCG2 protocol is installed.
> If not, measurement shall be skipped.
>
> Signed-o
On Thu, 9 Dec 2021 18:50:06 +0330
Javad Rahimi wrote:
Hi Javad,
thanks for the patch!
> When enabling the LED support for Cubieboard2 (SUN7I)
> the uboot freezes in status_led_init() function.
> It uses a static global variable, while the .BSS is defined in DRAM area
> while that function is c
Heinrich does this approach work for you till we fix the DM-EFI
integration?
At least it tries to cover some cases were the efi protocol is installed
(which means the tpm was there in the beginning), but later on is removed
On Tue, 7 Dec 2021 at 07:11, Masahisa Kojima wrote:
>
> When the TCG2 pr
When enabling the LED support for Cubieboard2 (SUN7I)
the uboot freezes in status_led_init() function.
It uses a static global variable, while the .BSS is defined in DRAM area
while that function is called before DRAM
Signed-off-by: Javad Rahimi
---
drivers/misc/status_led.c | 28 ++
On Thu, 9 Dec 2021 15:51:50 +0330
Javad Rahimi wrote:
Hi,
> On Thu, Dec 9, 2021 at 2:54 PM Andre Przywara wrote:
> Hi Andre,
> >
> > On Thu, 9 Dec 2021 14:38:08 +0330
> > Javad Rahimi wrote:
> >
> > Hi Javad,
> >
> > > On Thu, Dec 9, 2021 at 6:24 AM Javad Rahimi
> > > wrote:
> > > >
> >
On Thu, Dec 09, 2021 at 12:06:50AM +, Andre Przywara wrote:
> Hi Tom,
>
> please pull those two fixes from the sunxi tree.
> This fixes two regressions: eMMC operation on boards with WiFi (so using
> three MMC devices), and a repeated wrong error message in USB gadget
> mode (fastboot, ums).
This is a backport from Marvell U-Boot:
https://github.com/MarvellEmbeddedProcessors/u-boot-marvell
commit 381d029e7a ("fix: serdes: a38x, a39x: Improve USB3 electrical
configuration")
Improves electrical USB3 receiver jitter tolerance test:
- De-Emphasize force, in functional mode the transmitte
The electrical serdes configuration for USB3 expects an array as data
argument. For USB3 the second value is used (see data_arr_idx = USB3 =
1). However, because only one value is inside the array mv_seq_exec is
accessing an invalid element and the serdes is configured wrongly.
This wrong initiali
This patchset improves the USB3 serdes configuration for the Armada 38x
SoC from Marvell. The changes are based on the version from Marvell
found here:
https://github.com/MarvellEmbeddedProcessors/u-boot-marvell
Stefan Eichenberger (2):
arm: mvebu: a38x: serdes: fix serdes config for USB3
arm:
> -Original Message-
> From: Sughosh Ganu
> Sent: 2021年11月25日 15:02
> To: u-boot@lists.denx.de
> Cc: Patrick Delaunay ; Patrice Chotard
> ; Heinrich Schuchardt ;
> Alexander Graf ; Simon Glass ; Bin
> Meng ; Peng Fan ; AKASHI
> Takahiro ; Ilias Apalodimas
> ; Jose Marinho ; Grant
> Likel
On Thu, Dec 9, 2021 at 2:54 PM Andre Przywara wrote:
Hi Andre,
>
> On Thu, 9 Dec 2021 14:38:08 +0330
> Javad Rahimi wrote:
>
> Hi Javad,
>
> > On Thu, Dec 9, 2021 at 6:24 AM Javad Rahimi wrote:
> > >
> > > On Wed, Dec 8, 2021 at 9:13 PM Andre Przywara
> > > wrote:
> > > >
> > > > On Wed, 8 Dec
On Thu, 9 Dec 2021 14:38:08 +0330
Javad Rahimi wrote:
Hi Javad,
> On Thu, Dec 9, 2021 at 6:24 AM Javad Rahimi wrote:
> >
> > On Wed, Dec 8, 2021 at 9:13 PM Andre Przywara
> > wrote:
> > >
> > > On Wed, 8 Dec 2021 20:48:54 +0330
> > > Javad Rahimi wrote:
> > >
> > > > On Wed, Dec 8, 2021
`
On Thu, Dec 9, 2021 at 6:24 AM Javad Rahimi wrote:
>
> On Wed, Dec 8, 2021 at 9:13 PM Andre Przywara wrote:
> >
> > On Wed, 8 Dec 2021 20:48:54 +0330
> > Javad Rahimi wrote:
> >
> > > On Wed, Dec 8, 2021 at 8:33 PM Andre Przywara
> > > wrote:
> > > >
> > > > On Wed, 8 Dec 2021 19:14:22 +033
Calling 'nvme scan' followed by 'nvme detail' crashes U-Boot on Turris
Omnia with the following error:
undefined instruction
pc : [<0a00>] lr : [<7ff80bfc>]
reloc pc : [<8a8c>]lr : [<00840bfc>]
sp : 7fb2b908 ip : 002a fp : 0200
r10: 0400 r9 : 7fb2fe
On Thu, 9 Dec 2021 at 15:06, Jason Liu wrote:
>
>
> > -Original Message-
> > From: Sughosh Ganu
> > Sent: 2021年11月25日 15:02
> > To: u-boot@lists.denx.de
> > Cc: Patrick Delaunay ; Patrice Chotard
> > ; Heinrich Schuchardt ;
> > Alexander Graf ; Simon Glass ; Bin
> > Meng ; Peng Fan ; AKA
On Wed, 8 Dec 2021 at 19:23, Etienne Carriere
wrote:
> Hi Sughosh,
>
>
> On Thu, 25 Nov 2021 at 08:03, Sughosh Ganu
> wrote:
> >
> > In the FWU Multi Bank Update feature, the information about the
> > updatable images is stored as part of the metadata, which is stored on
> > a dedicated partitio
hi Etienne,
On Wed, 8 Dec 2021 at 18:44, Etienne Carriere
wrote:
> On Thu, 25 Nov 2021 at 08:03, Sughosh Ganu
> wrote:
> >
> > With the FWU multi bank update feature enabled, the dfu alt no that is
> > used to identify the partition to be updated is derived at runtime and
> > should match the p
hi Simon,
On Thu, 9 Dec 2021 at 08:02, Simon Glass wrote:
> Hi Sughosh,
>
> On Thu, 25 Nov 2021 at 00:03, Sughosh Ganu
> wrote:
> >
> > In the FWU Multi Bank Update feature, the information about the
> > updatable images is stored as part of the metadata, on a separate
> > partition. Add functi
On Thu, 9 Dec 2021 at 07:02, AKASHI Takahiro
wrote:
> On Wed, Dec 08, 2021 at 01:10:51PM +0530, Sughosh Ganu wrote:
> > hi Patrick,
> >
> > On Tue, 7 Dec 2021 at 21:05, Patrick DELAUNAY <
> patrick.delau...@foss.st.com>
> > wrote:
> >
> > > Hi Sugosh
> > >
> > > On 11/25/21 8:01 AM, Sughosh Ganu
67 matches
Mail list logo
