This series updates binman to handle creation of u-boot.itb image for
RISC-V boards.
Azure results: PASS
https://dev.azure.com/bmeng/GitHub/_build/results?buildId=360&view=results
The following tests were performed:
* booting qemu-riscv{32|64}_spl_defconfig on QEMU virt
* booting sifive_unleashed
It should be FDT, not FTD.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v1)
common/Kconfig.boot | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/Kconfig.boot b/common/Kconfig.boot
index 5a18d62d78..94d82c27dd 100644
--- a/common/Kconfig.boot
It needs a space around '-a'.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v1)
tools/binman/binman.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst
index 1aa2459d50..b3df3a6428 100644
--- a/
This is wrongly referring to Intel ME, which should be ATF.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v1)
tools/binman/etype/atf_bl31.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/binman/etype/atf_bl31.py b/tools/binman/etype/atf_bl3
Currently there are 2 binman test cases using the same 172 number.
It seems that 172_fit_fdt.dts was originally named as 170_, but
commit c0f1ebe9c1b9 ("binman: Allow selecting default FIT configuration")
changed its name to 172_ for no reason. Let's change it back.
Signed-off-by: Bin Meng
Review
Add an entry for RISC-V OpenSBI's 'fw_dynamic' firmware payload.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- drop "size = <16>" in the binman node
tools/binman/entries.rst | 13 +
tools/binman/etype/opensbi.py | 23 +++
This updates the make rules to pass OpenSBI blob to binman.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v1)
Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile b/Makefile
index 404977efa5..3d88559b67 100644
--- a/Makefile
+++ b/Makefile
@@ -1287,6
At present SiFive Unleashed board uses the Makefile to create the FIT,
using USE_SPL_FIT_GENERATOR, which is deprecated as per the Makefile
warning. Update to use binman instead.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3:
- Fix the opensbi entry type in binman.dtsi
a
Generally speaking BINMAN_FDT makes sense for OF_SEPARATE or OF_EMBED.
For the other OF_CONTROL methods, it's quite possible binman node is
not available as binman is invoked during the build phase instead of
runtime. Let's only turn it on for OF_SEPARATE or OF_EMBED by default.
Signed-off-by: Bin
Sort the RISC-V DTS build targets by their Kconfig target names in
alphabetical order.
Signed-off-by: Bin Meng
---
(no changes since v2)
Changes in v2:
- new patch: "riscv: dts: Sort build targets in alphabetical order"
arch/riscv/dts/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deleti
For scenarios like OF_BOARD or OF_PRIOR_STAGE, no device tree blob is
provided in the U-Boot build phase hence the binman node information
is not available. In order to support such use case, a new Kconfig
option BINMAN_STANDALONE_FDT is introduced, to tell the build system
that a device tree blob
By utilizing the newly introduced BINMAN_STANDALONE_FDT option, along
with a new dedicated device tree source file for the QEMU virt target
used for binman only, we can now use binman to generate u-boot.itb.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v2)
Changes in
Use the new BINMAN_STANDALONE_FDT option for AE350 based SPL defconfigs,
so that binman is now used to generate u-boot.itb.
Signed-off-by: Bin Meng
---
Changes in v3:
- new patch: "riscv: ae350: Switch to use binman to generate u-boot.itb"
arch/riscv/dts/ae350_32.dts | 2 ++
arch/ris
Now that we have switched to binman to generate u-boot.itb for all
RISC-V boards, USE_SPL_FIT_GENERATOR is no longer needed and can
be dropped.
Signed-off-by: Bin Meng
---
Changes in v3:
- remove USE_SPL_FIT_GENERATOR in ae350_ defconfigs
Changes in v2:
- new patch: "riscv: Drop USE_SPL_FIT_GE
On 08/05/21 3:36 pm, Vignesh Raghavendra wrote:
> Hi,
>
> On 5/6/21 4:44 PM, Lokesh Vutla wrote:
>> Add support for AM64 SoC identification.
>>
>> Signed-off-by: Lokesh Vutla
>> ---
>> drivers/soc/soc_ti_k3.c | 4
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/soc/soc_ti_k
On Sat, Mar 6, 2021 at 10:06 PM Marek Behun wrote:
>
> On Sat, 6 Mar 2021 21:45:02 -0600
> Adam Ford wrote:
>
> > On Sat, Mar 6, 2021 at 3:49 PM Marek Behun wrote:
> > >
> > > On Sat, 6 Mar 2021 22:38:52 +0100
> > > Pali Rohár wrote:
> > >
> > > > On Saturday 06 March 2021 22:19:22 Marek Behun
On Sun, 9 May 2021 09:14:14 -0500
Adam Ford wrote:
> On Sat, Mar 6, 2021 at 10:06 PM Marek Behun wrote:
> >
> > On Sat, 6 Mar 2021 21:45:02 -0600
> > Adam Ford wrote:
> >
> > > On Sat, Mar 6, 2021 at 3:49 PM Marek Behun wrote:
> > > >
> > > > On Sat, 6 Mar 2021 22:38:52 +0100
> > > > Pali
This patch allows uboot scripts make choices about where to boot from based
on the active mmc boot partition. This allows having two copies of kernel,
filesystems etc, and choosing which to boot from based off of the active
bootloader partition.
Signed-off-by: Reuben Dowle
---
cmd/mmc.c | 18 +++
On Fri, May 07, 2021 at 08:47:28PM +0200, Heinrich Schuchardt wrote:
> On 5/7/21 6:29 AM, AKASHI Takahiro wrote:
> > Heinrich,
> >
> > On Mon, Apr 26, 2021 at 11:44:59AM +0900, AKASHI Takahiro wrote:
> > > Heinrich,
> > >
> > > Do you have any comments?
> > > # not only on this issue, but also ot
Hi Heinrich,
Sorry for the late reply.
On Sat, 8 May 2021 at 23:08, Heinrich Schuchardt wrote:
>
> On 4/28/21 3:16 PM, Heinrich Schuchardt wrote:
> > On 28.04.21 14:19, Masahisa Kojima wrote:
>
> >> /**
> >>* cmp_pe_section() - compare virtual addresses of two PE image sections
> >>*
> If /chosen was missing, chosen_offset would never get updated with the new
> /chosen node. This would cause fdt_setprop_u32 to fail. This patch fixes
> this by setting chosen_offset. In addition, log any errors from setting
> boot-hartid as well.
>
> Fixes: 177c53fe6c6 ("riscv: Move all fdt fixup
On Mon, May 10, 2021 at 09:49:03AM +0900, Masahisa Kojima wrote:
> Hi Heinrich,
>
> Sorry for the late reply.
>
> On Sat, 8 May 2021 at 23:08, Heinrich Schuchardt wrote:
> >
> > On 4/28/21 3:16 PM, Heinrich Schuchardt wrote:
> > > On 28.04.21 14:19, Masahisa Kojima wrote:
> >
> > >> /**
> > >
On Sat, Apr 24, 2021 at 6:05 AM Simon Glass wrote:
>
> This should be 'regwidth', not 'baud'. Fix it.
>
> Signed-off-by: Simon Glass
> ---
>
> cmd/x86/cbsysinfo.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Bin Meng
On Mon, May 10, 2021 at 11:03 AM Bin Meng wrote:
>
> On Sat, Apr 24, 2021 at 6:05 AM Simon Glass wrote:
> >
> > This should be 'regwidth', not 'baud'. Fix it.
> >
> > Signed-off-by: Simon Glass
> > ---
> >
> > cmd/x86/cbsysinfo.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
>
>
On Sat, Apr 24, 2021 at 12:57 PM Simon Glass wrote:
>
> The BIOS version may not be present, e.g. on a Chrome OS build. Add the
> BIOS date as well, so we get some sort of indication of coreboot's
> vintage.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v2:
> - Reorder declaration and use b
Hi Reuben,
On 5/10/21 9:14 AM, Reuben Dowle wrote:
> This patch allows uboot scripts make choices about where to boot from based
> on the active mmc boot partition. This allows having two copies of kernel,
> filesystems etc, and choosing which to boot from based off of the active
> bootloader part
Hi Jaehoon,
>
> boot_ack / boot_partition / partition_access are optional variable, not
> mandatory.
> And it's confused that different variable is used with same command.
>
> I think that it's enough to use "mmc partconf ". Then it's showed which
> partition is used.
>
> If you have to apply t
Modify mmc man-page.
- Change a descritpion about mmc erase command.
- Add whitespace to distinguish.
Signed-off-by: Jaehoon Chung
---
doc/usage/mmc.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/usage/mmc.rst b/doc/usage/mmc.rst
index 57284ed6741e..6457c934c084 10
On Mon, May 10, 2021 at 1:00 PM Jaehoon Chung wrote:
>
> Modify mmc man-page.
> - Change a descritpion about mmc erase command.
typo: description
> - Add whitespace to distinguish.
>
> Signed-off-by: Jaehoon Chung
> ---
> doc/usage/mmc.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion
On Sat, Apr 24, 2021 at 12:57 PM Simon Glass wrote:
>
> Use VENDOR_COREBOOT instead of TARGET_COREBOOT so we can have multiple
> coreboot boards, sharing options. Only SYS_CONFIG_NAME needs to be
> defined TARGET_COREBOOT.
>
> Signed-off-by: Simon Glass
> ---
>
> (no changes since v1)
>
> arch/x
On Sat, Apr 24, 2021 at 12:57 PM Simon Glass wrote:
>
> Add information about memory usage when U-Boot is started from coreboot.
> This is useful when debugging. Also, since coreboot takes a chunk of
> memory in the middle of SDRAM for use by PCI devices, it can help avoid
> overwriting this with
Hi Simon,
On Sat, Apr 24, 2021 at 1:00 PM Simon Glass wrote:
>
> With of-platdata-inst we want to set up a reference to each devices'
> parent device, if there is one. If we find that the device has a parent
> (i.e. is not a root node) but it is not in the list of devices being
> written, then we
On Thu, Apr 29, 2021 at 5:40 PM Bin Meng wrote:
>
> This convers the existing README.virtio to reST, and puts it under
> the develop/driver-model/ directory.
>
> Signed-off-by: Bin Meng
> ---
>
> doc/develop/driver-model/index.rst| 1 +
> .../driver-model/virtio.rst}
On Thu, Apr 29, 2021 at 5:40 PM Bin Meng wrote:
>
> This was missed when VirtIO support was initially brought to U-Boot
> back in 2018. Add an entry for it and list myself as the maintainer.
>
> Signed-off-by: Bin Meng
> ---
>
> MAINTAINERS | 12
> 1 file changed, 12 insertions(+)
>
While doing code-review internally this got nitpicked by 2 reviewers, so
I decided to include this here.
Signed-off-by: Steffen Jaeckel
Reviewed-by: Simon Glass
---
(no changes since v1)
common/autoboot.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/com
In order to prevent using the global errno, replace it with a static
version and create a wrapper function which returns the error value.
Signed-off-by: Steffen Jaeckel
---
(no changes since v1)
include/crypt.h | 3 ++-
lib/crypt/alg-sha256.h | 6 --
lib/crypt/alg-sha512.h |
This patchset introduces support for crypt-style passwords to unlock
the console in autoboot mode.
The implementation of crypt-sha256 and crypt-sha512 originate from
libxcrypt at https://github.com/besser82/libxcrypt.git
Version v4.4.17
Git commit hash 6b110bc
I didn't re-format those two files
Hook into the autoboot flow as an alternative to the existing
mechanisms.
Signed-off-by: Steffen Jaeckel
---
(no changes since v1)
common/Kconfig.boot | 37 ++---
common/autoboot.c | 80 -
2 files changed, 103 insertions(+), 14 dele
Add the basic functionality required to support the standard crypt
format.
The files crypt-sha256.c and crypt-sha512.c originate from libxcrypt and
their formatting is therefor retained.
The integration is done via a crypt_compare() function in crypt.c.
```
libxcrypt $ git describe --long --always
In order to have at least one defconfig that enables all those newly added
values.
Signed-off-by: Steffen Jaeckel
---
(no changes since v1)
configs/bcm963158_ram_defconfig | 8
1 file changed, 8 insertions(+)
diff --git a/configs/bcm963158_ram_defconfig b/configs/bcm963158_ram_defcon
In case a user has to enter a complicated password it is sometimes
desireable to give the user more time than the default timeout.
Enabling this feature will disable the timeout entirely in case the user
presses the key before entering any other character.
Signed-off-by: Steffen Jaeckel
Reviewed
This is a copy of the regular sandbox with crypt-based password entry
enabled.
Signed-off-by: Steffen Jaeckel
---
(no changes since v1)
configs/sandbox_cryptpass_defconfig | 296
1 file changed, 296 insertions(+)
create mode 100644 configs/sandbox_cryptpass_defcon
On Sat, Apr 24, 2021 at 12:56 PM Simon Glass wrote:
>
> At present only bridge devices are bound before relocation, to save space
> in pre-relocation memory. In some cases we do actually want to bind a
> device, e.g. because it provides the console UART. Add a devicetree
> binding to support this.
Hello,
Here is the 3rd version of the series (including some fixes for build
errors) to add SynQuacer/DeveloperBox 96board EE suport on U-Boot.
This series includes not only DeveloperBox support but also some fixes
for the issues which I faced while porting U-Boot on the DeveloperBox.
First 3 pat
Update the highest subordinate bus number after probing the devices
under the bus for setting up the bridge correctly.
The commit 42f3663a3f67 ("pci: Update to use new sequence numbers")
removed this but it is required if a PCIe bridge is under the bus.
Fixes: 42f3663a3f67 ("pci: Update to use new
Without this fix, scsi-scan will cause a synchronous abort
when accessing ops->scan.
Signed-off-by: Masami Hiramatsu
Reviewed-by: Simon Glass
---
drivers/ata/ahci-pci.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/ata/ahci-pci.c b/drivers/ata/ahci-pci.c
index 11ec98b56f..b1d
Commit bbbcb5262839 ("dm: pci: Enable VGA address forwarding on bridges")
sets the VGA bridge bits by checking pplat->class, but if the parent
device is the pci host bus device, it can be skipped. Moreover, it
shouldn't access the pplat because the parent has different plat data.
Without this fix,
When running the efidebug capsule disk-update command, the efi_fmp_raw
protocol installation is failed with 2 (EFI_INVALID_PARAMETER) as
below. This is because the code passes efi_root instaed of handle.
=> efidebug capsule disk-update
EFI: Call: efi_install_multiple_protocol_interfaces( &handle,
Since some SoCs and boards do not hae extra asm/arch/gpio.h,
introduce CONFIG_GPIO_EXTRA_HEADER instead of adding
!define(CONFIG_ARCH_) in asm/gpio.h.
Signed-off-by: Masami Hiramatsu
---
Changes in v3:
- Change the config name to positive and selected by the
opposite CONFIG_AR
Add ECAM based SynQuacer PCIe RC driver. This driver configures the
PCIe RC and filter out a ghost pcie config.
Since the Linux kernel expects "socionext,synquacer-pcie-ecam" device
is configured by firmware (EDK2), it doesn't re-configure in the kernel.
So as same as EDK2, U-Boot needs to configu
From: Jassi Brar
Signed-off-by: Jassi Brar
Signed-off-by: Masami Hiramatsu
---
Changes in v3:
- Rename config name to MMC_SDHCI_F_SDH30.
- Remove unneeded wait in drivers/mmc/sdhci.c.
- Rename probe function to f_sdh30_sdhci_probe.
---
drivers/mmc/Kconfig | 10 ++
drivers/mmc/Ma
From: Jassi Brar
This is a driver for the HSSPI SPI controller on SynQuacer SoC.
The HSSPI has command sequence mode (memory mapped) and
direct mode (FIFO access). The driver will operate it under
the direct mode. And before booting OS, it switch back to the
command sequence mode since that is co
From: Jassi Brar
Add SynQuacer's NETSEC GbE controller driver.
Since this driver will load the firmware from SPI NOR flash,
this depends on CONFIG_SYNQUACER_SPI=y.
Signed-off-by: Jassi Brar
---
drivers/net/Kconfig |8
drivers/net/Makefile |1
drivers/net/sni_netsec.c | 1134
Add device trees for 96boards EE DeveloperBox and basement SynQuacer
SoC dtsi. These files are imported from EDK2
commit 83d38b0b4c0f240d4488c600bbe87cea391f3922
as-is (except for the changes #include path and some macros).
And add U-Boot specific changes in synquacer-sc2a11-developerbox-u-boot.
Add the DeveloperBox 96boards EE support. This board is also
known as Socionext SynQuacer E-Series. It contians one "SC2A11"
SoC, which has 24-cores of arm Cortex-A53, and 4 DDR3 slots,
3 PCIe slots (1 4x port and 2 1x ports which are expanded via
PCIe bridge chip), 2 USB 3.0 ports and 2 USB 2.0 po
Since the EDK2 GenerateCapsule script is out of date and it
doesn't generate the supported version capsule file, the document
should refer the mkeficapsule in tools.
Signed-off-by: Masami Hiramatsu
---
doc/board/emulation/qemu_capsule_update.rst | 11 ++-
1 file changed, 2 insertions(+
Ignore the non-implemented lock device failure on writing mtd
via DFU. Without this fix, DFU write shows an error on such device
even if it succeeded, because dfu->write_medium returns -EOPNOTSUPP.
Signed-off-by: Masami Hiramatsu
Cc: Lukasz Majewski
---
drivers/dfu/dfu_mtd.c |2 ++
1 file c
Enable EFI capsule update support. With the EFI capsule update,
you can update U-Boot, TF-A and OP-TEE. TF-A and OP-TEE are
usually combined as a FIP binary, but if the binary is bigger
than 480KB, you have to modify FIP header, split the OP-TEE
and stores the OP-TEE binary in the different place.
Hi Reuben,
On 5/10/21 1:38 PM, Reuben Dowle wrote:
> Hi Jaehoon,
>
>>
>> boot_ack / boot_partition / partition_access are optional variable, not
>> mandatory.
>> And it's confused that different variable is used with same command.
>>
>> I think that it's enough to use "mmc partconf ". Then it's s
On Mon, Apr 12, 2021 at 08:35:24PM +0530, Sughosh Ganu wrote:
> Add config options EFI_PKEY_DTB_EMBED and EFI_PKEY_FILE which are to
> be used for embedding the public key to be used for capsule
> authentication into the platform's device tree.
>
> The embedding of the public key would take place
On 5/10/21 7:00 AM, Jaehoon Chung wrote:
Modify mmc man-page.
- Change a descritpion about mmc erase command.
- Add whitespace to distinguish.
Signed-off-by: Jaehoon Chung
---
doc/usage/mmc.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/usage/mmc.rst b/doc/usag
+CC Bin Meng
On 5/10/21 8:53 AM, Heinrich Schuchardt wrote:
On 5/10/21 7:00 AM, Jaehoon Chung wrote:
Modify mmc man-page.
- Change a descritpion about mmc erase command.
- Add whitespace to distinguish.
Signed-off-by: Jaehoon Chung
---
doc/usage/mmc.rst | 3 ++-
1 file changed, 2 insertion
On Fri, May 07, 2021 at 09:49:08AM +0800, Sean Anderson wrote:
> Hi Leo,
>
> Are you maintaining RISC-V now? Should I be CC-ing you on my series?
> Can you update MAINTAINERS with this information? Thanks.
>
> --Sean
>
Hi Sean,
Yes, I am now co-maintaining RISC-V tree with Rick.
I will update
It should be FDT, not FTD.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v1)
common/Kconfig.boot | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/Kconfig.boot b/common/Kconfig.boot
index 5a18d62d78..94d82c27dd 100644
--- a/common/Kconfig.boot
This series updates binman to handle creation of u-boot.itb image for
RISC-V boards.
Azure results: PASS
https://dev.azure.com/bmeng/GitHub/_build/results?buildId=363&view=results
The following tests were performed:
* booting qemu-riscv{32|64}_spl_defconfig on QEMU virt
* booting sifive_unleashed
It needs a space around '-a'.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v1)
tools/binman/binman.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst
index 1aa2459d50..b3df3a6428 100644
--- a/
This is wrongly referring to Intel ME, which should be ATF.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v1)
tools/binman/etype/atf_bl31.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/binman/etype/atf_bl31.py b/tools/binman/etype/atf_bl3
Currently there are 2 binman test cases using the same 172 number.
It seems that 172_fit_fdt.dts was originally named as 170_, but
commit c0f1ebe9c1b9 ("binman: Allow selecting default FIT configuration")
changed its name to 172_ for no reason. Let's change it back.
Signed-off-by: Bin Meng
Review
Add an entry for RISC-V OpenSBI's 'fw_dynamic' firmware payload.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
(no changes since v2)
Changes in v2:
- drop "size = <16>" in the binman node
tools/binman/entries.rst | 13 +
tools/binman/etype/opensbi.py | 23 +++
69 matches
Mail list logo
