Please ignore this. I just noticed it will probably not work for
ax25-ae350, since it will try to load a DTB from u-boot binary.
I'll send a v3 shortly fixing this
Regards
/Ilias
On Thu, 30 Sept 2021 at 09:41, Ilias Apalodimas
wrote:
>
> At some point back in 2018 prior_stage_fdt_address and
The previous patches removed OF_PRIOR_STAGE from the last consumers of the
Kconfig option. Cleanup any references to it in documentation, code and
configuration options.
Signed-off-by: Ilias Apalodimas
Reviewed-by: Simon Glass
---
Changes since v1, v2:
- none
dts/Kconfig | 11
On 30/09/21 02:32PM, tkuw584...@gmail.com wrote:
> From: Takahiro Kuwano
>
> The current S25FS512S support has following issues that need to be fixed.
>
> - Non-uniform sectors by factory default. The setting needs to be
> checked and assign erase hook as needed.
> - Page size is
At some point back in 2018 prior_stage_fdt_address and OF_PRIOR_STAGE got
introduced, in order to support a DTB handed over by an earlier stage boo
loader. However we have another option in the Kconfig (OF_BOARD) which has
identical semantics.
So let's remove the option in an effort to simplify
The previous patches removed OF_PRIOR_STAGE from the last consumers of the
Kconfig option. Cleanup any references to it in documentation, code and
configuration options.
Signed-off-by: Ilias Apalodimas
Reviewed-by: Simon Glass
---
Changes since v1:
- none
dts/Kconfig | 11
At some point back in 2018 prior_stage_fdt_address and OF_PRIOR_STAGE got
introduced, in order to support a DTB handed over by an earlier stage boo
loader. However we have another option in the Kconfig (OF_BOARD) which has
identical semantics.
On RISC-V some of the platforms pick up the DTB
On 9/30/21 8:23 AM, François Ozog wrote:
Le jeu. 30 sept. 2021 à 07:12, Bin Meng mailto:bmeng...@gmail.com>> a écrit :
Hi Heinrich,
On Thu, Sep 9, 2021 at 7:16 PM Heinrich Schuchardt
mailto:xypron.g...@gmx.de>> wrote:
>
> Hello Simon,
>
> The EBBR
Le jeu. 30 sept. 2021 à 07:12, Bin Meng a écrit :
> Hi Heinrich,
>
> On Thu, Sep 9, 2021 at 7:16 PM Heinrich Schuchardt
> wrote:
> >
> > Hello Simon,
> >
> > The EBBR specification requires that the UEFI SystemReset() runtime
> > service is available to the operating system.
> >
> > Up to now
Le jeu. 30 sept. 2021 à 08:38, Bin Meng a écrit :
> On Thu, Sep 30, 2021 at 2:23 PM François Ozog
> wrote:
>
>>
>>
>> Le jeu. 30 sept. 2021 à 07:12, Bin Meng a écrit :
>>
>>> Hi Heinrich,
>>>
>>> On Thu, Sep 9, 2021 at 7:16 PM Heinrich Schuchardt
>>> wrote:
>>> >
>>> > Hello Simon,
>>> >
>>>
Am 2021-09-30 08:56, schrieb Heinrich Schuchardt:
On 9/30/21 8:23 AM, François Ozog wrote:
[..]
Is U-Boot's UEFI loader implementation supposed to be the
recommended
UEFI firmware on ARM and RISC-V on a production / deployment
system?
For Arm: yes, that is SystemReady spec.
For
On Thu, 30 Sept 2021 at 09:38, Bin Meng wrote:
>
> On Thu, Sep 30, 2021 at 2:23 PM François Ozog
> wrote:
>>
>>
>>
>> Le jeu. 30 sept. 2021 à 07:12, Bin Meng a écrit :
>>>
>>> Hi Heinrich,
>>>
>>> On Thu, Sep 9, 2021 at 7:16 PM Heinrich Schuchardt
>>> wrote:
>>> >
>>> > Hello Simon,
>>> >
At some point back in 2018 prior_stage_fdt_address and OF_PRIOR_STAGE got
introduced, in order to support a DTB handed over by an earlier stage boot
loader. However we have another option in the Kconfig (OF_BOARD) which has
identical semantics.
On RISC-V some of the platforms pick up the DTB
At some point back in 2018 prior_stage_fdt_address and OF_PRIOR_STAGE got
introduced, in order to support a DTB handed over by an earlier stage boo
loader. However we have another option in the Kconfig (OF_BOARD) which has
identical semantics.
So let's remove the option in an effort to simplify
On Thu, Sep 30, 2021 at 2:23 PM François Ozog
wrote:
>
>
> Le jeu. 30 sept. 2021 à 07:12, Bin Meng a écrit :
>
>> Hi Heinrich,
>>
>> On Thu, Sep 9, 2021 at 7:16 PM Heinrich Schuchardt
>> wrote:
>> >
>> > Hello Simon,
>> >
>> > The EBBR specification requires that the UEFI SystemReset() runtime
On Thu, Sep 30, 2021 at 12:12 AM Matthias Brugger wrote:
> On 29/09/2021 23:05, Ricardo Salveti wrote:
> > On Wed, Sep 29, 2021 at 1:49 PM Matthias Brugger wrote:
> >> On 29/09/2021 14:19, Mauro Salvini wrote:
> >>> Hi Matthias,
> >>>
> >>> On 29/09/21 13:41, Matthias Brugger wrote:
> Hi
Am 30. September 2021 11:53:47 MESZ schrieb Michael Walle :
>Am 2021-09-30 08:56, schrieb Heinrich Schuchardt:
>> On 9/30/21 8:23 AM, François Ozog wrote:
>[..]
>>> Is U-Boot's UEFI loader implementation supposed to be the
>>> recommended
>>> UEFI firmware on ARM and RISC-V on a
> From: Simon Glass
> Date: Wed, 29 Sep 2021 22:08:49 -0600
Hi Simon,
> Hi Heinrich,
>
> On Fri, 10 Sept 2021 at 08:19, Heinrich Schuchardt wrote:
> >
> >
> >
> > On 9/9/21 10:00 PM, Simon Glass wrote:
> > > Hi Heinrich,
> > >
> > > On Thu, 9 Sept 2021 at 05:29, Heinrich Schuchardt
> > >
On Thu, 30 Sept 2021 at 14:07, Michael Walle wrote:
> Am 2021-09-30 12:50, schrieb Heinrich Schuchardt:
> > Am 30. September 2021 11:53:47 MESZ schrieb Michael Walle
> > :
> >> Am 2021-09-30 08:56, schrieb Heinrich Schuchardt:
> >>> On 9/30/21 8:23 AM, François Ozog wrote:
> >> [..]
>
Am 2021-09-30 12:50, schrieb Heinrich Schuchardt:
Am 30. September 2021 11:53:47 MESZ schrieb Michael Walle
:
Am 2021-09-30 08:56, schrieb Heinrich Schuchardt:
On 9/30/21 8:23 AM, François Ozog wrote:
[..]
Is U-Boot's UEFI loader implementation supposed to be the
recommended
UEFI
From: TekkamanV
Signed-off-by: TekkamanV
---
common/Kconfig.boot | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/Kconfig.boot b/common/Kconfig.boot
index 902a5b8fbe..4f29cc2d56 100644
--- a/common/Kconfig.boot
+++ b/common/Kconfig.boot
@@ -343,7 +343,7 @@ config
From: Tekkaman Ninja
This patchset is trying to enable some configs in the Kconfig for RISC-V:
SYS_MALLOC_LEN
SYS_CLK_FREQ
They are very common config for some developement board. By these patch,
we can reduce the #define in the include/configs/*.h, and config them in
the menuconfig.
TekkamanV
On 9/30/21 13:13, Mark Kettenis wrote:
From: Simon Glass
Date: Wed, 29 Sep 2021 22:08:49 -0600
Hi Simon,
Hi Heinrich,
On Fri, 10 Sept 2021 at 08:19, Heinrich Schuchardt wrote:
On 9/9/21 10:00 PM, Simon Glass wrote:
Hi Heinrich,
On Thu, 9 Sept 2021 at 05:29, Heinrich Schuchardt
> From: François Ozog
> Date: Thu, 30 Sep 2021 08:23:34 +0200
>
> Le jeu. 30 sept. 2021 à 07:12, Bin Meng a écrit :
>
> > Hi Heinrich,
> >
> > On Thu, Sep 9, 2021 at 7:16 PM Heinrich Schuchardt
> > wrote:
> > >
> > > Hello Simon,
> > >
> > > The EBBR specification requires that the UEFI
From: TekkamanV
This patch add memcpy_fromio and memcpy_toio definitions for some device
drivers which has these definitions, like cadence_qspi_apb.c
Signed-off-by: TekkamanV
---
arch/riscv/include/asm/io.h | 4
1 file changed, 4 insertions(+)
diff --git a/arch/riscv/include/asm/io.h
On 9/30/21 13:31, Mark Kettenis wrote:
From: François Ozog
Date: Thu, 30 Sep 2021 08:23:34 +0200
Le jeu. 30 sept. 2021 à 07:12, Bin Meng a écrit :
Hi Heinrich,
On Thu, Sep 9, 2021 at 7:16 PM Heinrich Schuchardt
wrote:
Hello Simon,
The EBBR specification requires that the UEFI
Hi Stefano,
On 29.09.21 16:42, Frieder Schrempf wrote:
> From: Frieder Schrempf
>
> This a patchset to upstream the support for the SL i.MX6UL, SL i.MX6ULL and
> SL i.MX8MM families of SoMs and matching evaluation boards by Kontron
> Electronics.
>
> The first patch adds the i.MX6UL/ULL
Hi Tom,
I want to clean my queue for next version that's why please merge these
patches to your tree.
Thanks,
Michal
The following changes since commit 67ae2897235e516d8fa9ab3f296a1caf40f6ebee:
Merge tag 'rpi-next-2021.10.2' of
https://source.denx.de/u-boot/custodians/u-boot-raspberrypi
From: "yanhong.wang"
Signed-off-by: yanhong.wang
---
drivers/mtd/spi/spi-nor-ids.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
index 4aef1ddd6e..35fa347c44 100644
--- a/drivers/mtd/spi/spi-nor-ids.c
+++
On Wed, Sep 29, 2021 at 10:08:46PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Sat, 4 Sept 2021 at 09:08, Tom Rini wrote:
> >
> > On Sun, Aug 08, 2021 at 12:20:27PM -0600, Simon Glass wrote:
> >
> > > This converts the following to Kconfig:
> > >CONFIG_POWER_I2C
> > >CONFIG_POWER_LEGACY
>
> From: Ilias Apalodimas
> Date: Thu, 30 Sep 2021 09:46:30 +0300
>
> On Thu, 30 Sept 2021 at 09:38, Bin Meng wrote:
>
> > Does any board that ships EDK II with UEFI + DTB?
>
> The Socionext SynQuacer box is the only board I know off, that works
> with EDK2 and can use either DT or ACPI.
The
From: "yanhong.wang"
Signed-off-by: yanhong.wang
---
drivers/mtd/spi/spi-nor-ids.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c
index 4aef1ddd6e..35fa347c44 100644
--- a/drivers/mtd/spi/spi-nor-ids.c
+++
Hi Frieder,
On 30.09.21 15:16, Frieder Schrempf wrote:
Hi Stefano,
On 29.09.21 16:42, Frieder Schrempf wrote:
From: Frieder Schrempf
This a patchset to upstream the support for the SL i.MX6UL, SL i.MX6ULL and
SL i.MX8MM families of SoMs and matching evaluation boards by Kontron
Electronics.
From: TekkamanV
Signed-off-by: TekkamanV
---
Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Kconfig b/Kconfig
index a6c42b902f..7f63929c60 100644
--- a/Kconfig
+++ b/Kconfig
@@ -249,7 +249,7 @@ config SYS_MALLOC_F_LEN
config SYS_MALLOC_LEN
hex "Define
On 9/30/21 14:07, Michael Walle wrote:
Am 2021-09-30 12:50, schrieb Heinrich Schuchardt:
Am 30. September 2021 11:53:47 MESZ schrieb Michael Walle
:
Am 2021-09-30 08:56, schrieb Heinrich Schuchardt:
On 9/30/21 8:23 AM, François Ozog wrote:
[..]
Is U-Boot's UEFI loader implementation
[adding Vladimir, because he showed interest in this, too]
Am 2021-09-30 15:56, schrieb François Ozog:
On Thu, 30 Sept 2021 at 14:07, Michael Walle wrote:
Am 2021-09-30 12:50, schrieb Heinrich Schuchardt:
Am 30. September 2021 11:53:47 MESZ schrieb Michael Walle
:
Am 2021-09-30 08:56,
Hey all,
Due to the combination of the Let's Encrypt root certificate change and
the CI images not ending up with a new enough ca-certificates package,
CI is currently failing. It looks like the best fix for this, sadly, is
to rebuild the CI images, so I'll be doing that, uploading to Docker and
From: Frieder Schrempf
Currently 'sf update' supports only offsets that are aligned to the
erase block size of the serial flash. Unaligned offsets result in
something like:
=> sf update ${kernel_addr_r} 0x400 ${filesize}
device 0 offset 0x400, size 0x11f758
SPI flash failed in erase step
In
On Thu, 30 Sep 2021 08:06:42 PDT (-0700), markhimelst...@riscv.org wrote:
Palmer,
Thank you for your input.
Our strong intention is to not change specs once frozen. I speak for the
committees here and say that, in our opinion, declaring something frozen
sets a very high bar for making any
Hi Sean,
On 9/30/21 12:15 PM, Sean Anderson wrote:
>
>
>
> On 9/30/21 9:47 AM, Ariel D'Alessandro wrote:
>> strlcat() is truncating the destination string to the size of the source
>> string. Fix size argument in strlcat() to match the size of destination
>> buffer.
>>
>> Bug was introduced in
On Thu, 30 Sept 2021 at 17:12, Michael Walle wrote:
> [adding Vladimir, because he showed interest in this, too]
>
> Am 2021-09-30 15:56, schrieb François Ozog:
> > On Thu, 30 Sept 2021 at 14:07, Michael Walle wrote:
> >
> >> Am 2021-09-30 12:50, schrieb Heinrich Schuchardt:
> >>> Am 30.
Am 2021-09-30 17:47, schrieb François Ozog:
On Thu, 30 Sept 2021 at 17:12, Michael Walle wrote:
[adding Vladimir, because he showed interest in this, too]
Am 2021-09-30 15:56, schrieb François Ozog:
On Thu, 30 Sept 2021 at 14:07, Michael Walle
wrote:
Am 2021-09-30 12:50, schrieb
The following is the extension lifecycle. It includes the official names
going forward for each phase. We are trying to resolve any confusion naming
and numbering and are still in progress of this evolution:
On 9/30/21 9:47 AM, Ariel D'Alessandro wrote:
strlcat() is truncating the destination string to the size of the source
string. Fix size argument in strlcat() to match the size of destination
buffer.
Bug was introduced in the following commit:
commit 69a752983171c2983fc1f29c7cfa1844f41e5d8b
From: Keerthy
The driver enables IPU support. Basically enables the clocks,
timers, watchdog timers and bare minimal MMU and supports
loading the firmware from mmc.
Signed-off-by: Keerthy
[Amjad: fix compile warnings]
Signed-off-by: Amjad Ouled-Ameur
---
(no changes since v1)
MAINTAINERS
From: Keerthy
Add remoteproc resource handling helpers. These functions
are primarily to parse the resource table and to handle
different types of resources. Carveout, devmem, trace &
vring resources are handled.
Signed-off-by: Keerthy
[Amjad: fix redefinition of "struct resource_table" and
From: Frieder Schrempf
This doesn't include any functional changes, but simplifies the
existing code a bit and prepares for the following patch that
implements unaligned writes.
Signed-off-by: Frieder Schrempf
---
drivers/dfu/dfu_sf.c | 13 ++---
1 file changed, 6 insertions(+), 7
From: Keerthy
Add support for ipu early boot.
Signed-off-by: Keerthy
Signed-off-by: Amjad Ouled-Ameur
---
(no changes since v1)
arch/arm/dts/am57xx-idk-common-u-boot.dtsi | 1 +
arch/arm/dts/dra7-evm-u-boot.dtsi | 1 +
arch/arm/dts/dra71-evm-u-boot.dtsi | 1 +
From: Keerthy
Add support for ipu early boot.
Signed-off-by: Keerthy
Signed-off-by: Amjad Ouled-Ameur
---
(no changes since v1)
MAINTAINERS | 1 +
arch/arm/dts/am57xx-beagle-x15-revb1-u-boot.dtsi | 7 +++
On Wed, Sep 29, 2021 at 10:08:58PM -0600, Simon Glass wrote:
> Hi Pali,
>
> On Sun, 12 Sept 2021 at 15:30, Pali Rohár wrote:
> >
> > On Tuesday 20 July 2021 12:32:46 Simon Glass wrote:
> > > On Sat, 10 Jul 2021 at 05:10, Pali Rohár wrote:
> > > >
> > > > OEM_REVISION is 32-bit unsigned number.
strlcat() is truncating the destination string to the size of the source
string. Fix size argument in strlcat() to match the size of destination
buffer.
Bug was introduced in the following commit:
commit 69a752983171c2983fc1f29c7cfa1844f41e5d8b
Author: Sean Anderson
fastboot: Fix possible
Palmer,
Thank you for your input.
Our strong intention is to not change specs once frozen. I speak for the
committees here and say that, in our opinion, declaring something frozen
sets a very high bar for making any changes and is sufficient to allow code
supporting an extension to be
Some boards use ddr3, not ddr4, so we need to check ddr3 firmware.
Signed-off-by: Ariel D'Alessandro
---
tools/imx8m_image.sh | 7 +++
1 file changed, 7 insertions(+)
diff --git a/tools/imx8m_image.sh b/tools/imx8m_image.sh
index ba601044435..4ab3116ee00 100755
--- a/tools/imx8m_image.sh
On Tue, 28 Sep 2021 10:01:40 +0200
Stefan Agner wrote:
> The current code invalidates the range after the read buffer since the
> buffer pointer gets incremented in the read loop. Use a temporary
> pointer to make sure we have a pristine pointer to invalidate the
> correct memory range after
From: Keerthy
Add all the ipu early boot related nodes
Signed-off-by: Keerthy
Signed-off-by: Amjad Ouled-Ameur
---
(no changes since v1)
MAINTAINERS | 1 +
arch/arm/dts/dra7-ipu-common-early-boot.dtsi | 113 +++
2 files changed, 114
From: Keerthy
Add a reset driver to bring IPs out of reset.
Signed-off-by: Keerthy
[Amjad: reset_ops structure member "free" has been renamed to "rfree",
use the latter instead]
Signed-off-by: Amjad Ouled-Ameur
---
(no changes since v1)
MAINTAINERS| 1 +
From: Keerthy
Add ipu and the associated nodes.
Signed-off-by: Keerthy
Signed-off-by: Amjad Ouled-Ameur
---
(no changes since v1)
arch/arm/dts/dra7.dtsi | 45 +-
1 file changed, 44 insertions(+), 1 deletion(-)
diff --git a/arch/arm/dts/dra7.dtsi
From: Keerthy
Enable fs_loader compilation at SPL Level.
Signed-off-by: Keerthy
[Amjad: fix compilation failures for J721e platform]
Signed-off-by: Amjad Ouled-Ameur
---
(no changes since v1)
arch/arm/mach-k3/common.c | 10 +++---
configs/j721e_evm_r5_defconfig| 1 +
From: Keerthy
Add find_next_zero_area to fetch the next zero area in the map.
Signed-off-by: Keerthy
Signed-off-by: Amjad Ouled-Ameur
---
(no changes since v1)
include/linux/bitmap.h | 26 ++
1 file changed, 26 insertions(+)
diff --git a/include/linux/bitmap.h
Am 2021-09-30 18:19, schrieb Frieder Schrempf:
In order to support unaligned updates, we simply read the first full
block and check only the requested part of the block for changes. If
necessary, the block is erased, the first (unchanged) part of the block
is written back together with the
On Thu, 30 Sept 2021 at 18:25, Michael Walle wrote:
> Am 2021-09-30 17:47, schrieb François Ozog:
> > On Thu, 30 Sept 2021 at 17:12, Michael Walle wrote:
> >
> >> [adding Vladimir, because he showed interest in this, too]
> >>
> >> Am 2021-09-30 15:56, schrieb François Ozog:
> >>> On Thu, 30
Hello!
Could you test or review this patch series?
It is a big improvement for kwboot as it allows to transfer u-boot over
uart into mvebu platforms much faster.
On Friday 24 September 2021 23:06:37 Marek Behún wrote:
> From: Marek Behún
>
> Hello Stefan and others,
>
> here's v3 of series
On Mon, Sep 27, 2021 at 05:42:39PM +0200, Wolfgang Denk wrote:
> Signed-off-by: Wolfgang Denk
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Mon, Sep 27, 2021 at 05:42:36PM +0200, Wolfgang Denk wrote:
> Signed-off-by: Wolfgang Denk
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Mon, Sep 27, 2021 at 05:42:37PM +0200, Wolfgang Denk wrote:
> Signed-off-by: Wolfgang Denk
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
On Mon, Sep 27, 2021 at 05:42:38PM +0200, Wolfgang Denk wrote:
> Signed-off-by: Wolfgang Denk
> Reviewed-by: Simon Glass
Applied to u-boot/next, thanks!
--
Tom
signature.asc
Description: PGP signature
This patchset enables support for loading and starting IPU firmware,
the following have been implemented:
- Enable fs_loader compilation at SPL Level, that is necessary in order
to load IPU firmware from /boot partition.
- Define necessary related IPU dts nodes.
- Add necessary
From: Keerthy
First check the presence of the ipu firmware in the boot partition.
If present enable the ipu and the related clocks & then move
on to load the firmware and eventually start remoteproc IPU1/IPU2.
do_enable_clocks by default puts the clock domains into auto
which does not work well
On 30.09.21 18:35, Michael Walle wrote:
> Am 2021-09-30 18:19, schrieb Frieder Schrempf:
>> In order to support unaligned updates, we simply read the first full
>> block and check only the requested part of the block for changes. If
>> necessary, the block is erased, the first (unchanged) part of
Hi,
I am trying to build one configuration blob which should be included in
SPL. And still I didn't find the right way how to do it.
I need to build C file just as object and run objcopy -O binary.
I can be done with host gcc or target gcc. Both of them are little
endian that's why it shouldn't
From: Frieder Schrempf
Currently using an offset that is not aligned to the erase block size
of the flash results in incorrect data on the device. To support this
use case, we prevent the first cycle to write beyond the erase block
border and return the actual bytes written to the calling
From: Frieder Schrempf
This doesn't include any functional changes, but allows us to use the
size parameter to report the actual written bytes back to the caller.
This is useful in cases of unaligned writes to serial flash where the
first write covers only a part of the buffer (until the next
On Thu, Sep 30, 2021 at 11:34:11AM -0400, Tom Rini wrote:
> Hey all,
>
> Due to the combination of the Let's Encrypt root certificate change and
> the CI images not ending up with a new enough ca-certificates package,
> CI is currently failing. It looks like the best fix for this, sadly, is
>
On Thu, Sep 30, 2021 at 04:50:11PM +0200, Michal Simek wrote:
> Hi Tom,
>
> I want to clean my queue for next version that's why please merge these
> patches to your tree.
>
> Thanks,
> Michal
>
>
> The following changes since commit 67ae2897235e516d8fa9ab3f296a1caf40f6ebee:
>
> Merge tag
With SystemReady, DT from distros are ignored.
Err? Is this really true, I know about some incompatible changes
to the device tree which prevents you from using usb (or even a
kernel panic) with the imx8mm and I know that on the ls1028a
flexspi wont work if the devicetree doesn't match the
On Thu, 30 Sep 2021 10:38:02 PDT (-0700), markhimelst...@riscv.org wrote:
The following is the extension lifecycle. It includes the official names
going forward for each phase. We are trying to resolve any confusion naming
and numbering and are still in progress of this evolution:
Am 2021-09-30 19:17, schrieb Frieder Schrempf:
On 30.09.21 18:35, Michael Walle wrote:
Am 2021-09-30 18:19, schrieb Frieder Schrempf:
In order to support unaligned updates, we simply read the first full
block and check only the requested part of the block for changes. If
necessary, the block
Am 2021-09-30 18:19, schrieb Frieder Schrempf:
From: Frieder Schrempf
Currently 'sf update' supports only offsets that are aligned to the
erase block size of the serial flash. Unaligned offsets result in
something like:
=> sf update ${kernel_addr_r} 0x400 ${filesize}
device 0 offset 0x400,
Le ven. 1 oct. 2021 à 00:00, Michael Walle a écrit :
> > With SystemReady, DT from distros are ignored.
>
> Err? Is this really true, I know about some incompatible changes
> to the device tree which prevents you from using usb (or even a
> kernel panic) with the imx8mm
Am 2021-10-01 00:20, schrieb François Ozog:
Le ven. 1 oct. 2021 à 00:00, Michael Walle a
écrit :
With SystemReady, DT from distros are ignored.
Err? Is this really true, I know about some incompatible
changes
to the device tree which prevents you from using usb (or even a
kernel panic)
Hi Pali,
On 30.09.21 20:14, Pali Rohár wrote:
Hello!
Could you test or review this patch series?
It's on my list.
It is a big improvement for kwboot as it allows to transfer u-boot over
uart into mvebu platforms much faster.
Very much appreciated. I'll try to find some time today to
The purpose of this RPC is to reignite the discussion about how UEFI
subystem would best be integrated into U-Boot device model.
In the past, I poposed a couple of patch series, the latest one[1],
while Heinrich revealed his idea[2], and the approach taken here is
something between them, with a
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
---
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
---
disk/part.c | 3 ++-
1 file changed, 2 insertions(+), 1
Now that all the block device drivers have enable a probe hook, we will
call blk_create_partitions() 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 | 15 +++
1 file
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
UCLASS_PARTITION device will be created as a child node of
UCLASS_BLK device.
Signed-off-by: AKASHI Takahiro
---
drivers/block/blk-uclass.c | 111 +
include/blk.h | 9 +++
include/dm/uclass-id.h | 1 +
3 files changed, 121 insertions(+)
Now that all the block device drivers have enable a probe hook, we will
call blk_create_partitions() 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 | 15 +++
1 file
In most of all usages, we can avoid using blk_desc which is expected
to be data private to the device not be accessed outside device drivers.
Signed-off-by: AKASHI Takahiro
---
lib/efi_loader/efi_disk.c | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff
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
Hi Frieder,
On Thu, 30 Sept 2021 at 10:20, Frieder Schrempf wrote:
>
> From: Frieder Schrempf
>
> Currently 'sf update' supports only offsets that are aligned to the
> erase block size of the serial flash. Unaligned offsets result in
> something like:
>
> => sf update ${kernel_addr_r} 0x400
Adding the callback function, efi_disk_delete(), in block devices's
pre_remove hook will allows for automatically deleting efi_disk objects
per block device.
This will eliminate any improper efi_disk objects which hold a link to
non-existing udevice structures when associated block devices are
Signed-off-by: AKASHI Takahiro
---
lib/efi_driver/efi_block_device.c | 6 ++
lib/efi_loader/efi_device_path.c | 29 +
lib/efi_loader/efi_disk.c | 12 +++-
3 files changed, 46 insertions(+), 1 deletion(-)
diff --git
Signed-off-by: AKASHI Takahiro
---
lib/efi_driver/efi_block_device.c | 6 ++
lib/efi_loader/efi_device_path.c | 29 +
lib/efi_loader/efi_disk.c | 12 +++-
3 files changed, 46 insertions(+), 1 deletion(-)
diff --git
This function is expected to be called, in particular from dm's pre_remove
hook, when associated block devices no longer exist.
Signed-off-by: AKASHI Takahiro
---
include/efi_loader.h | 2 ++
lib/efi_loader/efi_disk.c | 54 +++
2 files changed, 56
This function is expected to be called, in particular from dm's pre_remove
hook, when associated block devices no longer exist.
Signed-off-by: AKASHI Takahiro
---
include/efi_loader.h | 2 ++
lib/efi_loader/efi_disk.c | 54 +++
2 files changed, 56
Adding the callback function, efi_disk_delete(), in block devices's
pre_remove hook will allows for automatically deleting efi_disk objects
per block device.
This will eliminate any improper efi_disk objects which hold a link to
non-existing udevice structures when associated block devices are
This function is a counterpart of efi_add_handle() and will be used
in order to remove an efi_disk object in a later patch.
Signed-off-by: AKASHI Takahiro
---
include/efi_loader.h | 2 ++
lib/efi_loader/efi_boottime.c | 8
2 files changed, 10 insertions(+)
diff --git
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
---
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
---
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
---
1 - 100 of 126 matches
Mail list logo
