On Fri, Nov 20, 2020 at 06:31:52PM -0500, Tom Rini wrote:
> On Fri, Nov 20, 2020 at 11:56:27PM +0100, Patrick Wildt wrote:
> > Am Wed, Oct 07, 2020 at 03:26:38PM +0200 schrieb Heinrich Schuchardt:
> > > On 07.10.20 11:04, Patrick Wildt wrote:
> > > > With DM enabled the ethernet code will receive
Hi Heinrich,
Thank you for the review. I increased the max size to 64 characters.
The size, in the end, is the size of the salt plus the size of the
password the human user would type. In most places I have seen salt used,
it is only a few characters (modern Linux password databases use
On Fri, Nov 20, 2020 at 11:56:27PM +0100, Patrick Wildt wrote:
> Am Wed, Oct 07, 2020 at 03:26:38PM +0200 schrieb Heinrich Schuchardt:
> > On 07.10.20 11:04, Patrick Wildt wrote:
> > > With DM enabled the ethernet code will receive a packet, call
> > > the push method that's set by the EFI network
Hi Stefan,
I have a patch (
https://patchwork.ozlabs.org/project/uboot/patch/20201120180524.30251-1-jp933...@xl-irv-13.lvn.broadcom.net/
) under review that adds optional SALT to AUTOBOOT_STOP_STR_SHA256 without
breaking backward compatibility. As I see that you were involved with the
Am Wed, Oct 07, 2020 at 03:26:38PM +0200 schrieb Heinrich Schuchardt:
> On 07.10.20 11:04, Patrick Wildt wrote:
> > With DM enabled the ethernet code will receive a packet, call
> > the push method that's set by the EFI network implementation
> > and then free the packet. Unfortunately the push
From: Joel Peshkin
Adds an optional SALT value to AUTOBOOT_STOP_STR_SHA256. If a string
followed by a ":" is prepended to the sha256, the portion to the left
of the colon will be used as a salt and the password will be appended
to the salt before the sha256 is computed and compared.
On 11/20/20 2:41 AM, Joel Peshkin wrote:
From: Joel Peshkin
Adds an optional SALT value to AUTOBOOT_STOP_STR_SHA256. If a string
followed by a ":" is prepended to the sha256, the portion to the left
of the colon will be used as a salt and the password will be appended
to the salt before the
The sequence number assigned for USB subsystem in a uclass is dependent on
the order of occurrence in the device tree. If the dr_mode of USB3SS0
controller is varied then the sequence number of USB3SS1 controller also
changes. If aliases are added then sequence numbers are assigned using the
alias
USB3SS0 controller is to be used as a host in U-boot. Fix it by changing
the dr_mode to host.
Signed-off-by: Aswath Govindraju
---
arch/arm/dts/k3-am654-base-board-u-boot.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/dts/k3-am654-base-board-u-boot.dtsi
It has been observed that setting SERDES0 lane mux to USB prevents USB 2.0
operation on USB0. Setting SERDES0 lane mux to non-USB when USB0 is used in
USB 2.0 only mode solves this issue. However, for USB3.0+2.0 operation this
issue is not present.
Implement this workaround by writing 1 to
The following series of patches
- adds support for host mode to USB3SS0 controller
- adds aliases for USB subsystems
- adds a workaround to use USB0 in USB 2.0 only mode
Aswath Govindraju (3):
board: ti: am65x: Set SERDES0 mux to PCIe to use USB 2.0 interface
dts: am654-base-board-uboot:
On Fri, Nov 20, 2020 at 02:35:33PM +0100, Michal Simek wrote:
>
>
> On 20. 11. 20 14:25, Michael Walle wrote:
> > Am 2020-11-20 14:16, schrieb Michal Simek:
> >> On 20. 11. 20 12:27, Michael Walle wrote:
> >>> Am 2020-11-20 12:15, schrieb Michal Simek:
> On 20. 11. 20 11:48, Michael Walle
Le 20/11/2020 à 02:35, Tom Rini a écrit :
On Tue, Nov 03, 2020 at 12:11:20PM +0100, Richard Genoud wrote:
This will prevent a double free error if sqfs_close() is called twice.
Signed-off-by: Richard Genoud
This change causes the test.py squashfs tests to fail. I am unsure if
the problem
Convert README to reStructuredText format.
Signed-off-by: Oliver Graute
---
board/advantech/imx8qm_rom7720_a1/README | 61 --
doc/board/advantech/imx8qm-rom7720-a1.rst | 75 +++
doc/board/advantech/index.rst | 9 +++
3 files changed, 84
Hi Anand,
Am 19.11.20 um 18:53 schrieb Anand Moon:
Hi Otto,
On Thu, 19 Nov 2020 at 21:23, Otto Meier wrote:
Hi,
I have extended the previous post.
with these modifications i get:
U-Boot 2021.01-rc2-00047-g9324c9a823-dirty (Nov 19 2020 - 15:33:00
+0100) odroid-c2
Model: Hardkernel
Am 2020-11-20 14:35, schrieb Michal Simek:
On 20. 11. 20 14:25, Michael Walle wrote:
Am 2020-11-20 14:16, schrieb Michal Simek:
On 20. 11. 20 12:27, Michael Walle wrote:
Am 2020-11-20 12:15, schrieb Michal Simek:
[..]
Please get this reviewed by people who are using current blX code.
What
Hi, Andy
On 11/19/20 10:21 PM, Andy Shevchenko wrote:
> Update Tom's address
>
> On Thu, Nov 19, 2020 at 9:26 PM Andy Shevchenko
> wrote:
>> It seems nobody tested the debug() option in spin_lock_irqsave().
>> Currently, when #define DEBUG, it spoils the compiler with
>>
>> In file included from
Hi Tom,
please pull these patches to your tree. CI builds look good.
Especially fru fixes are needed but enabling microblaze GC with other
fixes are also good.
Thanks,
Michal
The following changes since commit b80680633dc954d32f81f3afacd3d1f2f3d290b0:
Merge branch '2020-11-18-assorted-fixes'
On 20. 11. 20 14:25, Michael Walle wrote:
> Am 2020-11-20 14:16, schrieb Michal Simek:
>> On 20. 11. 20 12:27, Michael Walle wrote:
>>> Am 2020-11-20 12:15, schrieb Michal Simek:
On 20. 11. 20 11:48, Michael Walle wrote:
> Am 2020-11-20 11:14, schrieb Michal Simek:
>> Hi,
>>
The debug string printing the device name, framebuffer address and of node
is using %lu as format for the framebuffer address, which is not so nice.
Change it to %lx.
Signed-off-by: Arnaud Patard
Index: u-boot/drivers/video/rockchip/rk_vop.c
This patchset add support for the rk3399 eDP. It has been tested on the pinebook
pro and Google Kevin chromeos devices.
The changes have been written by studying the linux code, since I didn't find
any
manual for theses part of the RK3399 SoC.
On the linux kernel side, on recent kernels, it
According to linux commit "drm/rockchip: analogix_dp: add rk3399 eDP
support" (82872e42bb1501dd9e60ca430f4bae45a469aa64), rk3288 and rk3399
eDP IPs are nearly the same, the difference is in the grf register
(SOC_CON6 versus SOC_CON20). So, change the code to use the right
register on each IP.
The
In order to ensure that the VOP registers are in correct state,
add missing support for the VOP reset lines found in the device-tree
Signed-off-by: Arnaud Patard
Index: u-boot/drivers/video/rockchip/rk_vop.c
===
---
In order to ensure that the eDP registers are in correct state,
add missing support for the eDP reset lines found in the device-tree.
Signed-off-by: Arnaud Patard
Index: u-boot/drivers/video/rockchip/rk_edp.c
===
---
When booting with EFI and graphics, the memory used for framebuffer
has to be reserved, otherwise it may leads to kernel memory
overwrite.
Signed-off-by: Arnaud Patard
Index: u-boot/drivers/video/rockchip/rk_vop.c
===
---
In the code, the default polarity is set to positive/positive,
which is neither normal polarity or inverted polarity. It's
only the hardware default. This leads to booting linux with
wrong polarity setting.
Update the code to use PWM_DUTY_POSTIVE | PWM_INACTIVE_NEGATIVE
by default instead.
- uboot rockchip edp code is looking for a rockchip,panel property
for the edp dts node, so add it.
Signed-off-by: Arnaud Patard
Index: u-boot/arch/arm/dts/rk3399-pinebook-pro-u-boot.dtsi
===
---
The linux code is setting polarity configuration to 3 but
uboot code is setting it to 1. Change the configuration to match the
linux configuration
Signed-off-by: Arnaud Patard
Index: u-boot/arch/arm/include/asm/arch-rockchip/edp_rk3288.h
The current code is using an hard coded enum and the of node reg value of
endpoint to find out if the endpoint is mipi/hdmi/lvds/edp/dp. The order
is different between rk3288, rk3399 vop little, rk3399 vop big.
A possible solution would be to make sure that the rk3288.dtsi and
rk3399.dtsi files
Am 2020-11-20 14:16, schrieb Michal Simek:
On 20. 11. 20 12:27, Michael Walle wrote:
Am 2020-11-20 12:15, schrieb Michal Simek:
On 20. 11. 20 11:48, Michael Walle wrote:
Am 2020-11-20 11:14, schrieb Michal Simek:
Hi,
On 18. 11. 20 17:45, Michael Walle wrote:
Newer TF-A versions provide a
On 10/03/20, Stefano Babic wrote:
> On 19.12.19 15:27, Oliver Graute wrote:
> > Fix broken fsl_esdhc_imx conversion
> >
> > Signed-off-by: Oliver Graute
> > Cc: Stefano Babic
> > Cc: Fabio Estevam
> > Cc: Peng Fan
> > Cc: Simon Glass
> > Cc: Ye Li
> > Cc: uboot-imx
> > ---
> >
On 20. 11. 20 12:27, Michael Walle wrote:
> Am 2020-11-20 12:15, schrieb Michal Simek:
>> On 20. 11. 20 11:48, Michael Walle wrote:
>>> Am 2020-11-20 11:14, schrieb Michal Simek:
Hi,
On 18. 11. 20 17:45, Michael Walle wrote:
> Newer TF-A versions provide a new image loading
Hi,
When trying to boot rpi_4_32b_defconfig of U-Boot 2020.10 (or master)
using a USB flash drive, U-Boot hangs early at:
U-Boot 2020.10 (Nov 20 2020 - 10:25:26 +0100)
DRAM: 3.9 GiB
The weird thing is that at this point U-Boot does not access USB/SD card
at all, still it matters if it got
Am 2020-11-20 11:48, schrieb Michael Walle:
Am 2020-11-20 11:14, schrieb Michal Simek:
Hi,
On 18. 11. 20 17:45, Michael Walle wrote:
Newer TF-A versions provide a new image loading protocol. This is
used on
(newer?) NXP's SoCs. Normally, the bootflow is bl1 -> bl2 -> bl31 ->
u-boot. With
Am 2020-11-20 12:15, schrieb Michal Simek:
On 20. 11. 20 11:48, Michael Walle wrote:
Am 2020-11-20 11:14, schrieb Michal Simek:
Hi,
On 18. 11. 20 17:45, Michael Walle wrote:
Newer TF-A versions provide a new image loading protocol. This is
used on
(newer?) NXP's SoCs. Normally, the bootflow
Update build instructions and image formats based on HSM rearch. A new
DM image is added into the build, which gets executed right after R5
SPL finishes its job.
Signed-off-by: Tero Kristo
---
board/ti/j721e/README | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git
From: Dave Gerlach
Add platform clock and powerdomain data for J721e and J7200. This data
is used by the corresponding drivers to register all the required device
clocks and powerdomains.
Signed-off-by: Dave Gerlach
---
arch/arm/mach-k3/Makefile | 2 +-
From: Dave Gerlach
Sysfw is not going to provide access to power management features in the
new architecture, so SPL must implement these itself. Enable all the raw
register access based clock + power domain drivers.
Signed-off-by: Dave Gerlach
---
configs/j7200_evm_r5_defconfig | 14
Sysfw is not going to provide access to power management features in the
new architecture, so SPL must implement these itself. Enable all the raw
register access based clock + power domain drivers.
Signed-off-by: Tero Kristo
---
configs/j721e_evm_r5_defconfig | 12 ++--
1 file changed,
Add callback routines for parsing the firmware info from FIT image, and
use the data to boot up ATF and the MCU R5 firmware.
Signed-off-by: Tero Kristo
---
arch/arm/mach-k3/common.c | 80 +
arch/arm/mach-k3/common.h | 1 +
arch/arm/mach-k3/security.c |
Copy the contents of the board config loaded from sysfw.itb into an
EXTBOOT shared memory buffer that gets passed to sciserver. This only
needs to be done if EXTBOOT area has not been populated by ROM code yet.
Signed-off-by: Tero Kristo
---
arch/arm/mach-k3/sysfw-loader.c | 98
From: Dave Gerlach
Only start-up the non-linux remote cores if we are running in legacy
boot mode. HSM rearch is not yet supporting this.
Signed-off-by: Dave Gerlach
Signed-off-by: Tero Kristo
---
arch/arm/mach-k3/common.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff
Normally, power domains are handled via TI-SCI in K3 SoCs. However,
SPL is not going to have access to sysfw resources, so it must control
them directly. Add driver for supporting this.
Signed-off-by: Tero Kristo
---
drivers/power/domain/Kconfig | 7 +
drivers/power/domain/Makefile
Add support for TI K3 SoC PLLs. This clock type supports
enabling/disabling/setting and querying the clock rate for the PLL. The
euclidean library routine is used to calculate divider/multiplier rates
for the PLLs.
Signed-off-by: Tero Kristo
---
drivers/clk/Kconfig | 12 ++
Add DM (device manager) firmware image to the fit image that is loaded by
R5 SPL. This is needed with the HSM rearch where the firmware allocation
has been changed slightly.
Signed-off-by: Tero Kristo
---
arch/arm/mach-k3/config.mk | 4
tools/k3_fit_atf.sh| 19 ++-
If the raw PM support is built in, we are operating in the split
firmware approach mode where RM and PM support is not available. In this
case, skip the board config for these two.
Signed-off-by: Tero Kristo
---
arch/arm/mach-k3/sysfw-loader.c | 4
1 file changed, 4 insertions(+)
diff
Add support command for debugging K3 power domains. This is useful with
the HSM rearch setup, where power domains are directly controlled by SPL
instead of going through the TI SCI layer. The debugging support is only
available in the u-boot codebase though, so the raw register access
power domain
If a clock provider is not ready for assigning default rates/parents
during its probe, it may return -EPROBE_DEFER directly from xlate.
Handle this special case properly by skipping the entry and adjusting the
return value to pass. The defaults will be handled properly in post probe
phase then.
Clock rates are cached within the individual clock nodes, and right now
if one changes a clock rate somewhere in the middle of the tree, none
of its child clocks notice the change. To fix this, clear up all the
cached rates for us and our child clocks.
Signed-off-by: Tero Kristo
---
Add driver to support TI K3 generation SoC clocks. This driver registers
the clocks provided via platform data, and adds support for controlling
the clocks via DT handles.
Signed-off-by: Tero Kristo
---
drivers/clk/Kconfig | 10 ++
drivers/clk/Makefile | 1 +
drivers/clk/clk-k3.c | 340
Add new clk subcommand "clk setfreq", for setting up a clock rate
directly from u-boot cmdline. This is handy for any debugging purposes
towards clocks.
Acked-by: Lukasz Majewski
Signed-off-by: Tero Kristo
---
cmd/clk.c | 49 +++--
1 file changed, 47
Some clocks are not associated to a DM node, so just parsing the DM is not
enough. This is especially true for root clocks, which typically don't have
any parents. Instead, fetch every registered UCLASS_CLK instance, and dump
these out.
Signed-off-by: Tero Kristo
---
cmd/clk.c | 27
Set rate should return the new clock rate on success, and negative error
value on failure. Fix this, as currently set_rate returns 0 on success.
Signed-off-by: Tero Kristo
---
drivers/clk/clk-ti-sci.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Bail out early if device returned for the parent clock is null.
This avoids warning prints like this when doing clk dump:
dev_get_uclass_priv: null device
Signed-off-by: Tero Kristo
---
drivers/clk/clk-uclass.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/clk-uclass.c
Current driver only supports registering fixed rate clocks from DT. Add
new API which makes it possible to register fixed rate clocks directly
from e.g. platform specific clock drivers.
Reviewed-by: Peng Fan
Signed-off-by: Tero Kristo
---
drivers/clk/clk_fixed_rate.c | 45
With the sysfw rearch, sysfw PM calls are no longer available from SPL
level. To properly support this, remove the is_on checks and the reset
assertion from the R5 remoteproc driver as these are not supported.
Attempting to access unavailable services will cause the device to hang.
Signed-off-by:
clk_set_rate returns the new clock rate for the clock, not 0 in success.
Fix the error checks to reflect proper API usage.
Signed-off-by: Tero Kristo
---
drivers/ram/k3-j721e/k3-j721e-ddrss.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
On J7 family of SoCs (J721E and J7200), sysfw is being split to be run
under two cores, TIFS portion on DMSC core, and DM firmware under MCU
R5. As MCU R5 is also used to run one phase of the bootloader, we must
prevent access from here towards sysfw services. To support this, add
new config
Copy the best rational approximation calculation routines from Linux.
Typical usecase for these routines is to calculate the M/N divider
values for PLLs to reach a specific clock rate.
This is based on linux kernel commit:
"lib/math/rational.c: fix possible incorrect result from rational
From: Lokesh Vutla
board_fit_image_post_process() passes only start and size of the image,
but type of the image is not passed. So pass fit and node_offset, to
derive information about image to be processed.
Signed-off-by: Lokesh Vutla
---
arch/arm/mach-k3/security.c | 3 ++-
Hi,
Version 2 of this series has the review comments fixed received so far.
Added Lukasz also to delivery, as the series contains quite a few clock
driver patches in it.
Main changes in v2:
- Added new patch at #3 for the new config option (K3_DM_FW)
- Squashed the defconfig patches into one
-
On 20. 11. 20 11:48, Michael Walle wrote:
> Am 2020-11-20 11:14, schrieb Michal Simek:
>> Hi,
>>
>> On 18. 11. 20 17:45, Michael Walle wrote:
>>> Newer TF-A versions provide a new image loading protocol. This is
>>> used on
>>> (newer?) NXP's SoCs. Normally, the bootflow is bl1 -> bl2 -> bl31
Dear Rasmus,
In message <2edc1fb5-e723-fbd6-56da-bc0dea282...@prevas.dk> you wrote:
>
> >> set CONFIG_ENV_IS_NOWHERE, I'd get what I have now. The only problem
> >
> > Can't you see that this is not logical? If the environment is
> > nowhere, then how can you add something to it?
>
> That's
Am 2020-11-20 11:14, schrieb Michal Simek:
Hi,
On 18. 11. 20 17:45, Michael Walle wrote:
Newer TF-A versions provide a new image loading protocol. This is used
on
(newer?) NXP's SoCs. Normally, the bootflow is bl1 -> bl2 -> bl31 ->
u-boot. With this series it is possible that U-Boot SPL loads
When setting aside a GPT partition for holding the U-Boot environment,
having a partition type GUID [1] indicating "Linux filesystem" (as
most tools default to) is somewhat misleading - and there's no other
well-known type GUID that is better suited. So to have a canonical
value to put into the
The previous patch made the table look bad. Fix it, and leave some
space for a future element being a bit longer than the current
maximum.
Signed-off-by: Rasmus Villemoes
---
doc/README.gpt | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git
There's no reason to require an appropriately sized output parameter
for the string, that's error-prone should the table ever grow an
element with a longer string. We can just return the const char*
pointer directly.
Update the only caller accordingly, and get rid of pointless ifdeffery
in the
Adding the GUID to README.gpt and hooking it up in code turned out to
require two other, mostly janitorial, patches, the first and last
here.
I've tested that "part list host 0" does show the
type: u-boot-env
for a test image I generated with one partition's type guid set to the
value
On 20/11/2020 11.13, Wolfgang Denk wrote:
> Dear Rasmus,
>
> In message <76615995-6700-1b3e-b598-4913e9882...@prevas.dk> you wrote:
>>
>> Sure. So would you be ok with some /config/extra-environment node which
>> gets appended after the normal environment has been loaded? Then if I
>
> In
Dear Simon,
In message
you wrote:
>
> Some years ago I did a series to allow the environment to come from a
> text file, thus avoiding the \0 stuff.
"env import -t" does that, you know?
> Now binman has a 'u-boot-env'
> entry type, allowing creating an environment from a text file, with
>
Dear Tom,
In message <20201117182353.GB5340@bill-the-cat> you wrote:
>
> Adding in Marek as well since I believe he's been doing things with
> append-only environment, and it would be good to make sure we have
> something that fits everyones needs, and doesn't break what people are
> already
Hi,
On 18. 11. 20 17:45, Michael Walle wrote:
> Newer TF-A versions provide a new image loading protocol. This is used on
> (newer?) NXP's SoCs. Normally, the bootflow is bl1 -> bl2 -> bl31 ->
> u-boot. With this series it is possible that U-Boot SPL loads the bl31
> directly and thus replacing
Dear Rasmus,
In message <76615995-6700-1b3e-b598-4913e9882...@prevas.dk> you wrote:
>
> >> The default environment is something which is NOT INTENDED for
> >> regular use. it is what you will fall back to in case (and ONLY in
> >> that case) when your regular persistent environment cannot be
út 10. 11. 2020 v 13:21 odesílatel Michal Simek
napsal:
>
> Hi,
>
> I am sending 3 more patches for fru code. Especially the second patch is
> important because it ensures that data in .data section is not overwritten
> based on parsed structures.
>
> Thanks,
> Michal
>
>
> Michal Simek (3):
>
út 10. 11. 2020 v 13:16 odesílatel Michal Simek
napsal:
>
> TPMs are becoming popular that's why enable drivers and command for it.
>
> Signed-off-by: Michal Simek
> ---
>
> configs/xilinx_zynqmp_virt_defconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git
út 10. 11. 2020 v 13:16 odesílatel Michal Simek
napsal:
>
> There is no reason to have these macros. But record offsets of missing
> register in the structure for future use.
>
> Signed-off-by: Michal Simek
> ---
>
> arch/arm/mach-zynqmp/include/mach/hardware.h | 6 ++
> 1 file changed, 2
po 9. 11. 2020 v 15:46 odesílatel Michal Simek napsal:
>
> There is no need for GD to be used and priv variable is unused.
>
> Signed-off-by: Michal Simek
> ---
>
> drivers/tpm/tpm2_tis_spi.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/tpm/tpm2_tis_spi.c
po 16. 11. 2020 v 16:02 odesílatel Michal Simek
napsal:
>
> Hi,
>
> I looked at microblaze configs and clean up some things. All changes were
> done in connection to detect nor flash based on information taken from DT.
>
> Thanks
> Michal
>
> Changes in v2:
> - Rework the whole patch because
st 4. 11. 2020 v 14:55 odesílatel Michal Simek napsal:
>
> GCC's garbage collector works for Microblaze for quite a long time but none
> has enabled it.
> The same change has be done for example by commit fac4790491f6 ("arc:
> Eliminate unused code and data with GCC's garbage collector").
>
>
On 19/11/2020 19:59, Priit Laes wrote:
> On Thu, Nov 19, 2020 at 10:54:42AM +, Andre Przywara wrote:
>> So far we did not support the BootROM based FEL USB debug mode on the
>> 64-bit builds for Allwinner SoCs: The BootROM is using AArch32, but the
>> SPL runs in AArch64.
>> Returning back to
> -Original Message-
> From: Lim, Elly Siew Chin
> Sent: Tuesday, November 10, 2020 2:44 PM
> To: u-boot@lists.denx.de
> Cc: Marek Vasut ; Tan, Ley Foon
> ; See, Chin Liang ;
> Simon Goldschmidt ; Chee, Tien Fong
> ; Westergreen, Dalon
> ; Simon Glass ; Gan,
> Yau Wai ; Lim, Elly Siew
On Thu, 2020-11-19 at 18:48 +0100, Nicolas Saenz Julienne wrote:
> The Raspberry Pi Foundation released the new Compute Module 4which we
> want to detect, so we can enable Ethernet on it and know the correct
> device tree file name.
>
> Note that this sets the Ethernet option to true since the
On 17/11/2020 19.27, Tom Rini wrote:
> On Tue, Nov 17, 2020 at 11:05:36AM +0100, Rasmus Villemoes wrote:
>
>> Hi,
>>
>> Would it make sense to choose a canonical "Partition type GUID" [1] for
>> partitions used to store a U-Boot environment?
>>
>> The partition type is mostly informational, but
On Fri, 2020-11-20 at 07:15 +0100, Stefan Roese wrote:
> Hi Bin,
> Hi Nicolas,
>
> On 20.11.20 01:31, Bin Meng wrote:
> > +Stefan
> >
> > On Fri, Nov 20, 2020 at 1:49 AM Nicolas Saenz Julienne
> > wrote:
> > > So far we've been content with passing physical addresses when
> > > configuring
Update management of "--rm_memory" sandbox's option and force
this option when U-Boot is loaded by SPL in os_spl_to_uboot()
and remove the ram file after reading in main() as described
in option help message: "Remove memory file after reading".
This patch avoids that the file
85 matches
Mail list logo
