Hi
> I don't want to revert this commit. Is there any issue without this?
Without revert commit 17ea3c86, Some board, like Dragonboard 410c will meet
transfer data timeout error (we used v2018.01):
U-Boot 2018.01 (Nov 26 2020 - 03:31:09 +)
Qualcomm-DragonBoard 410C
DRAM: 986 MiB
MMC:
On Wed, 03 Mar 2021 01:49:53 +0800
Icenowy Zheng wrote:
Hi Icenowy,
many thanks for your research on this. I asked some local compiler
buffs, see below ...
> 在 2021-03-02星期二的 15:19 +，Andre Przywara写道：
> > On Tue, 02 Mar 2021 21:50:49 +0800
> > Icenowy Zheng wrote:
> >
> > Hi Icenowy,
>
On Fri, 26 Feb 2021 00:13:24 +0800
Icenowy Zheng wrote:
> Previously we have known that R40 has a configuration register for its
> rank 1, which allows different configuration than rank 0. Reverse
> engineering of newest libdram of A64 from Allwinner shows that A64 has
> this register too. It's
On Sun, 21 Feb 2021 10:44:47 +0100
Jernej Skrabec wrote:
> Commit 69076dff2284 ("cmd: pxe: add support for FDT overlays") added
> support for loading DT overlay files to PXE boot. However, it needs
> additional environment variable which points to memory location which
> can be used to temporary
On Wed, Mar 17, 2021 at 9:53 PM David Abdurachmanov <
david.abdurachma...@gmail.com> wrote:
> On Tue, Mar 16, 2021 at 6:35 PM Green Wan wrote:
> >
> > From: David Abdurachmanov
> >
> > Add fu740 support to macb ethernet driver
> >
> > Signed-off-by: David Abdurachmanov
> > Signed-off-by: Green
Hi
On 3/17/21 3:44 PM, yuezhang...@sony.com wrote:
> This reverts commit 17ea3c862865c0d704646f67dbf8412f9ff54f59.
>
> In eMMC specification, for the response-with-busy(R1b, R5b)
> command, the DAT0 will driven to LOW as BUSY status, and in
> sdhci specification, the transfer complete bit should
On 3/18/21 8:01 AM, Michael Walle wrote:
> Am 2021-03-17 23:47, schrieb Jaehoon Chung:
>> On 3/17/21 11:01 PM, Michael Walle wrote:
>>> config SYS_FSL_ERRATUM_A011334
>>> bool
>>> +
>>> +config SYS_FSL_ESDHC_UNRELIABLE_PULSE_DETECTION_WORKAROUND
>>
>> How about using QUIRK instead of
On 3/18/21 7:59 AM, Michael Walle wrote:
> Am 2021-03-17 23:49, schrieb Jaehoon Chung:
>> On 3/17/21 11:01 PM, Michael Walle wrote:
>>> Since commit 8ee802f899ef ("mmc: fsl_esdhc: make sure delay chain locked
>>> for HS400") HS400 mode is unreliable on LS1028A SoCs. Some workarounds are
>>>
Hi,
My apologise in advance. I'm looking for the memory map or memory
layout for the NXP i.MX8X AHAB secure boot. I would like to know the start
addresses of each container and header in RAM booting from RAM only and
eMMC boot.
And more specifically the OS container hex address that u-boot
Hello,
Le 10/03/2021 à 19:58, Gunjan Gupta a écrit :
PFA my dts file. I have added the nfc section there as without that U-Boot
was giving a message about nfc being disabled in the dts.
Regarding trying the default config, I can't really do that as that doesn't
support booting from NAND and I
I've recently hit that message in a yocto build. I can't figure out the
exact root cause. On the one hand, I don't know how "big" SPL is. On the
other hand, I can't objdump -h the SPL elf because one wasn't created.
Alex
Am 2021-03-17 23:47, schrieb Jaehoon Chung:
On 3/17/21 11:01 PM, Michael Walle wrote:
config SYS_FSL_ERRATUM_A011334
bool
+
+config SYS_FSL_ESDHC_UNRELIABLE_PULSE_DETECTION_WORKAROUND
How about using QUIRK instead of WORKAROUD
There is already a
Am 2021-03-17 23:49, schrieb Jaehoon Chung:
On 3/17/21 11:01 PM, Michael Walle wrote:
Since commit 8ee802f899ef ("mmc: fsl_esdhc: make sure delay chain
locked
for HS400") HS400 mode is unreliable on LS1028A SoCs. Some workarounds
are
missing for this SoC.
Disable HS400 mode for now.
On 3/17/21 9:55 PM, Tom Rini wrote:
> On Wed, Mar 17, 2021 at 01:13:57PM +0100, Marek Vasut wrote:
>> On 3/15/21 5:07 PM, Tom Rini wrote:
>>> Hey all,
>>>
>>> It's release day, and here's v2021.04-rc4. Not a whole lot of change
>>> since last time in master, and -next has been and is still open.
On 3/17/21 11:01 PM, Michael Walle wrote:
> Since commit 8ee802f899ef ("mmc: fsl_esdhc: make sure delay chain locked
> for HS400") HS400 mode is unreliable on LS1028A SoCs. Some workarounds are
> missing for this SoC.
>
> Disable HS400 mode for now.
>
> Signed-off-by: Michael Walle
It seems
On 3/17/21 11:01 PM, Michael Walle wrote:
> HS400 mode on the LS1028A SoC isn't reliable. The linux driver has a
> workaroung for the pulse width detection. Apply this workaround in
> u-boot, too.
>
> This will make HS400 mode work reliably on the LS1028A SoC.
>
> Signed-off-by: Michael Walle
>
From: Karl Beldan
Signed-off-by: Karl Beldan
---
lib/lz4_wrapper.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/lib/lz4_wrapper.c b/lib/lz4_wrapper.c
index e0f7d3688e..cdbcd05bd4 100644
--- a/lib/lz4_wrapper.c
+++ b/lib/lz4_wrapper.c
@@ -11,9 +11,18 @@
On 3/17/21 7:25 AM, Tom Rini wrote:
> On Wed, Mar 17, 2021 at 06:53:16AM +0900, Jaehoon Chung wrote:
>> Dear Tom,
>>
>> On 1/28/21 8:42 PM, Jaehoon Chung wrote:
>>> It's only one board which is using max_77696_init().
>>> pmic_max77696.c didn't convert from no-DM to DM.
>>> So it's waste to
On 11/30/20 10:12 AM, AKASHI Takahiro wrote:
Capsule data can be loaded into the system either via UpdateCapsule
runtime service or files on a file system (of boot device).
The latter case is called "capsules on disk", and actual updates will
take place at the next boot time.
In this commit, we
On 3/17/21 8:54 PM, Ilias Apalodimas wrote:
On the following patches we allow for an initrd path to be stored in
Boot variables. Specifically we encode in the FIlePathList[] of
the EFI_LOAD_OPTIONS for each Boot variable.
The FilePathList[] array looks like this:
kernel - 0xff -
Document the command line options for efidebug and initrd loading
Signed-off-by: Ilias Apalodimas
---
doc/uefi/uefi.rst | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/doc/uefi/uefi.rst b/doc/uefi/uefi.rst
index b3494c22e073..d92a32016ec0 100644
---
The UEFI spec allows a packed array of UEFI device paths in the
FilePathList[] of an EFI_LOAD_OPTION. The first file path must
describe the loaded image but the rest are OS specific.
Previous patches parse the device path and try to use the second
member of the array as an initrd. So let's modify
Up to now we install EFI_LOAD_FILE2_PROTOCOL to load an initrd
unconditionally. Although we correctly return various EFI exit codes
depending on the file status (i.e EFI_NO_MEDIA, EFI_NOT_FOUND etc), the
kernel loader, only falls back to the cmdline interpreted initrd if the
protocol is not
A following patch introduces a different logic for loading initrd's
based on the EFI_LOAD_FILE2_PROTOCOL.
Since similar logic can be applied in the future for other system files
(i.e DTBs), let's add some helper functions which will retrieve and
parse file paths stored in EFI variables.
On the following patches we allow for an initrd path to be stored in
Boot variables. Specifically we encode in the FIlePathList[] of
the EFI_LOAD_OPTIONS for each Boot variable.
The FilePathList[] array looks like this:
kernel - 0xff - VenMedia(initrd GUID) - initrd1 - 0x01 initrd2 -
Hi!
This is v4 of [1]
Changes since v3:
- Slightly tweaked the efidebug argument parsing following Heinrich's
suggestion. Instead of calculating the file device path initially and
appending the initrd, the 2 two device paths are now calculated
independently and concatenated later,
On Wed, 17 Mar 2021 at 09:51, Dario Binacchi wrote:
>
> The module defines a duplicate uclass driver for UCLASS_SIMPLE_BUS, but
> it is not allowed. This breaks of-platdata and makes the result
> non-deterministic.
>
> The driver does not need to be an uclass driver, so lets remove it. I
> had
These two functions do similar things. When CONFIG_HEXDUMP is enabled,
drop the code in print_buffer() and use the hexdump code instead. This
increases the code size a little, but makes the API similar to Linux.
When CONFIG_HEXDUMP is not enabled, don't do this, since presumably
code size is more
The print_buffer() function is very useful for debugging. Add a version
of this in the log system also.
Signed-off-by: Simon Glass
---
common/log.c| 30 ++
include/log.h | 35 +++
test/log/log_test.c | 27
At present print_buffer() outputs a hex dump but it is not possible to
place this dump in a string. Refactor it into a top-level function which
does the printing and a utility function that dumps a line into a string.
This makes the code more generally useful.
Signed-off-by: Simon Glass
---
These functions are not needed anymore since we now have logic which can
output to the console if logging is disabled. Drop the declarations.
Signed-off-by: Simon Glass
---
include/log.h | 18 --
1 file changed, 18 deletions(-)
diff --git a/include/log.h b/include/log.h
index
If a long hexdump is initated the user may wish to interrupt it. Add
support for this.
Signed-off-by: Simon Glass
---
include/hexdump.h | 6 --
lib/hexdump.c | 13 +
2 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/include/hexdump.h b/include/hexdump.h
index
At present print_hex_dump() only supports either 16- or 32-byte lines.
With U-Boot we want to support any line length up to a maximum of 64.
Update the function to support this, with 0 defaulting to 16, as with
print_buffer().
Signed-off-by: Simon Glass
---
include/hexdump.h | 4 ++--
The current implementation outputs an address as a pointer. Update the
code to use an address instead, respecting the 32/64 nature of the CPU.
Add some initial tests copied from print_test_display_buffer(), just the
ones that can pass with the current implementation.
Note that for this case
At present with print_buffer() U-Boot shows four spaces between the hex
and ASCII data. Two seems enough and matches print_hex_dump(). Change it.
Signed-off-by: Simon Glass
---
lib/display_options.c | 2 +-
test/cmd/mem_search.c | 26 +-
test/dm/rtc.c | 6
Move the comments to the header file so people can find the function info
without digging in the implementation. Fix up the code style and add an
enum for the first arg.
Signed-off-by: Simon Glass
---
include/hexdump.h | 75 -
lib/hexdump.c | 78
Add a test for this function, to cover the various features. Expand the
expect_str length to take acount of the ~300-bytes lines generated in one
case.
Signed-off-by: Simon Glass
---
include/test/test.h | 4 +--
test/print_ut.c | 82 +
2 files
This test predates the test framework in U-Boot. It uses #define DEBUG and
assert() to check the result. Update it to use the framework so it can
report failure constitent with other tests.
Signed-off-by: Simon Glass
---
include/test/suites.h | 1 +
test/cmd_ut.c | 2 +
If a line of more than 256 bytes is generated, the test will fail but the
reason is not clear. Add a check for this condition and print a helpful
message.
Signed-off-by: Simon Glass
---
test/ut.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/test/ut.c
If the console output buffer is exhausted, characters are silently dropped
from the end. Detect this condition and report an error when reading back
the characters.
Signed-off-by: Simon Glass
---
common/console.c | 18 +++
include/asm-generic/global_data.h | 16
At present we have two ways of showing a hex dump. Once has been in U-Boot
since the dawn of time and the other was recently added from Linux.
They both have their own unique features.
This series makes a few changes to bring them closer together. It also
adds support for logging a buffer, which
On Sat, Mar 6, 2021 at 10:04 PM Adam Ford wrote:
>
> secureworld_exit() is only used in one file, so make it static
> to that file and remove it from sys_proto.h. This
> may help with some further optimization in the future.
>
> Signed-off-by: Adam Ford
>
Lokesh,
Is this patch ok as-is, or do
On Tue, Mar 16, 2021 at 01:33:57PM +0100, Michal Simek wrote:
> The commit 12bfb2e05fc2 ("dm: spi: prevent setting a speed of 0 Hz")
> changes default value from 0 to SPI_DEFAULT_SPEED_HZ but spi_post_probe()
> hasn't been updated in the same way. It should be also update to be aligned
> with
When `usb start` is called on the terminal, the dwc2 driver will try
to start every USB device as host first, even if it is explicitly
configured as peripheral in the device tree (dr_mode = "peripheral").
So to avoid an unwanted 15 seconds delay when initializing the usb
(one second per channel =
From: João Loureiro
When `usb start` is called on the terminal, the dwc2 driver will try
to start every USB device as host first, even if it is explicitly
configured as peripheral in the device tree (dr_mode = "peripheral").
So to avoid an unwanted 15 seconds delay when initializing the usb
On 3/17/21 4:19 PM, João Loureiro wrote:
When `usb start` is called on the terminal, the dwc2 driver will try to start every USB
device as host first, even if it is explicitly configured as peripheral in the device
tree (`dr_mode = "peripheral"`).
So to avoid am unwanted 15 seconds delay when
When `usb start` is called on the terminal, the dwc2 driver will try to start
every USB device as host first, even if it is explicitly configured as
peripheral in the device tree (`dr_mode = "peripheral"`).
So to avoid am unwanted 15 seconds delay when initializing the usb (one second
per
Some devices, when configured in bootstrap to 'no cpu' mode require PHY
manual reset to get them operational and responding to reading their ID
registers.
Without this step - the PHYLIB probing will fail.
In more details - the bootstrap configuration from switch must be read.
The value of CONFIG
The mv88e61xx driver need to be adjusted to handle situation when
switch MDIO addresses are switched by offset (0x10 in this case).
Signed-off-by: Lukasz Majewski
---
drivers/net/phy/mv88e61xx.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git
The mv88e6020 is accessed in a direct way (i.e. with direct read and
write to mdio bus). The only necessary indirection is required when
accessing its PHY registers.
Signed-off-by: Lukasz Majewski
---
drivers/net/phy/mv88e61xx.c | 15 ++-
1 file changed, 10 insertions(+), 5
Those automatically created structures can have random value.
However, mv88e61xx driver assumes that those are zeroed.
Signed-off-by: Lukasz Majewski
---
drivers/net/phy/mv88e61xx.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/net/phy/mv88e61xx.c
After this change PHY ports are able to pass packets between them (and
also to CPU port).
The Kconfig variable - CONFIG_MV88E61XX_PHY_PORTS - is used to get the
PHY ports of the switch and generate proper mask.
Signed-off-by: Lukasz Majewski
---
drivers/net/phy/mv88e61xx.c | 9 +++--
1
Some Marvell switch devices are dual chip ones, like mv88e6020, which
use direct MDIO addressing to access its ports' registers. Such approach
allows connecting two such devices in a single MDIO bus with simple
addressing scheme.
Signed-off-by: Lukasz Majewski
---
drivers/net/phy/mv88e61xx.c |
This patch set provides support for mv88e6020 switch. It is a dual chip
device, with direct access to port register on SMI bus. However, PHYs
are accessed indirectly.
Lukasz Majewski (6):
net: mv88e61xx: Add support for checking addressing mode
net: mv88e61xx: Configure PHY ports to also
Add CPU info support for RZ/G2 SoC's.
Signed-off-by: Biju Das
---
V1-->V2
* Added support to make CPU info based on tfa is available only
when CONFIG_RZ_G2 is enabled.
---
arch/arm/mach-rmobile/Kconfig.64 | 5 +++
arch/arm/mach-rmobile/Makefile | 1 +
Now that it is working reliable on the LS1028A SoC, reenable support for
it.
Signed-off-by: Michael Walle
---
configs/kontron_sl28_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/kontron_sl28_defconfig b/configs/kontron_sl28_defconfig
index
Since commit 8ee802f899ef ("mmc: fsl_esdhc: make sure delay chain locked
for HS400") HS400 mode is unreliable on LS1028A SoCs. Some workarounds are
missing for this SoC.
Disable HS400 mode for now.
Signed-off-by: Michael Walle
---
configs/kontron_sl28_defconfig | 2 +-
1 file changed, 1
HS400 mode on the LS1028A SoC isn't reliable. The linux driver has a
workaroung for the pulse width detection. Apply this workaround in
u-boot, too.
This will make HS400 mode work reliably on the LS1028A SoC.
Signed-off-by: Michael Walle
---
arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 1 +
LS1028A SoCs are restricted in what divider values are allowed for HS400
mode. This is basically a port from the corresponding linux driver.
Signed-off-by: Michael Walle
---
arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 1 +
drivers/mmc/Kconfig | 3 +++
This patchset fixes HS400 mode on LS1028A SoC which is broken since commit
8ee802f899ef ("mmc: fsl_esdhc: make sure delay chain locked for HS400").
Well, before it might just have worked by accident.
=> run bootcmd_mmc0
fsl_esdhc: delay chain lock timeout
Select HS400 failed -110
unable to select
On Tue, Mar 16, 2021 at 6:35 PM Green Wan wrote:
>
> From: David Abdurachmanov
>
> Add fu740 support to macb ethernet driver
>
> Signed-off-by: David Abdurachmanov
> Signed-off-by: Green Wan
> Reviewed-by: Ramon Fried
> ---
> drivers/net/macb.c | 8 +++-
> 1 file changed, 7
On Wed, Mar 17, 2021 at 9:37 AM Fabio Estevam wrote:
>
> Hi Trevor,
>
> On Wed, Mar 17, 2021 at 10:22 AM Trevor Woerner wrote:
>
> > However, I am interested in preserving the olimex board (i.e.
> > configs/mx23_olinuxino_defconfig). So I could take a look at that one first
> > unless, Marek,
When `usb start` is called, the dwc2 driver will try to start every
USB device as host first, even if it is explicitly configured as
peripheral in the device tree, as the documentation explains (`dr_mode
= "peripheral"`).
So to avoid an unwanted 15 seconds delay when initializing the usb
(one
Hi Trevor,
On Wed, Mar 17, 2021 at 10:22 AM Trevor Woerner wrote:
> However, I am interested in preserving the olimex board (i.e.
> configs/mx23_olinuxino_defconfig). So I could take a look at that one first
> unless, Marek, you would like to take a look?
I have recently converted imx23-evk to
On 3/17/21 2:24 PM, João Loureiro wrote:
When `usb start` is called, the dwc2 driver will try to start every
USB device as host first, even if it is explicitly configured as
peripheral in the device tree, as the documentation explains (`dr_mode
= "peripheral"`).
So to avoid an unwanted 15
On 3/17/21 2:21 PM, Trevor Woerner wrote:
On Wed 2021-03-17 @ 08:55:59 AM, Tom Rini wrote:
On Wed, Mar 17, 2021 at 01:13:57PM +0100, Marek Vasut wrote:
On 3/15/21 5:07 PM, Tom Rini wrote:
Hey all,
It's release day, and here's v2021.04-rc4. Not a whole lot of change
since last time in
On 17/03/21 12:31PM, Michal Simek wrote:
> From: T Karthik Reddy
>
> Add spi memory operations to relocate manually when
> CONFIG_NEEDS_MANUAL_RELOC is enabled.
>
> Signed-off-by: T Karthik Reddy
> Acked-by: Ashok Reddy Soma
> Signed-off-by: Michal Simek
Reviewed-by: Pratyush Yadav
--
On Wed, Mar 17, 2021 at 09:21:45AM -0400, Trevor Woerner wrote:
> On Wed 2021-03-17 @ 08:55:59 AM, Tom Rini wrote:
> > On Wed, Mar 17, 2021 at 01:13:57PM +0100, Marek Vasut wrote:
> > > On 3/15/21 5:07 PM, Tom Rini wrote:
> > > > Hey all,
> > > >
> > > > It's release day, and here's v2021.04-rc4.
On Wed 2021-03-17 @ 08:55:59 AM, Tom Rini wrote:
> On Wed, Mar 17, 2021 at 01:13:57PM +0100, Marek Vasut wrote:
> > On 3/15/21 5:07 PM, Tom Rini wrote:
> > > Hey all,
> > >
> > > It's release day, and here's v2021.04-rc4. Not a whole lot of change
> > > since last time in master, and -next has
On Wed, Mar 17, 2021 at 01:13:57PM +0100, Marek Vasut wrote:
> On 3/15/21 5:07 PM, Tom Rini wrote:
> > Hey all,
> >
> > It's release day, and here's v2021.04-rc4. Not a whole lot of change
> > since last time in master, and -next has been and is still open. I just
> > want to repeat a few
On 3/15/21 5:07 PM, Tom Rini wrote:
Hey all,
It's release day, and here's v2021.04-rc4. Not a whole lot of change
since last time in master, and -next has been and is still open. I just
want to repeat a few things from -rc3:
- We've moved from "gitlab.denx.de" (and also "git.denx.de") to
On Mon 2021-03-15 @ 12:07:44 PM, Tom Rini wrote:
> - Once v2021.04 is released I will be pushing a large number of board
> removals for things that will be then 2 years past their "migrate this
> by ... or it might be removed" date which is also around 3 years total
> of notice.
FWIW I'm
On 3/17/21 12:51 PM, João Loureiro wrote:
When `usb start` is called, the dwc2 driver will try to start every
USB device as host first, even if it is explicitly configured as
peripheral in the device tree, as the documentation explains (`dr_mode
= "peripheral"`).
So to avoid an unwanted 15
On 3/11/21 11:55 PM, Robert Hancock wrote:
> The code was trying to disable PCS auto-negotiation when a fixed-link node
> is present and enable it otherwise. However, the PCS registers were being
> written before the PCSSEL bit was set in the network configuration
> register, and it appears
From: T Karthik Reddy
Add spi memory operations to relocate manually when
CONFIG_NEEDS_MANUAL_RELOC is enabled.
Signed-off-by: T Karthik Reddy
Acked-by: Ashok Reddy Soma
Signed-off-by: Michal Simek
---
Changes in v2:
- Check if mem_ops is defined before relocation - reported-by
Pratyush
From: Matthias Brugger
When no string is present in a table, next_ptr points to the same
location as eos. When calculating the string table length, we would only
reserve one \0. By spec a SMBIOS table has to end with two \0\0 when no
strings a present.
Signed-off-by: Matthias Brugger
---
Reviewed-by: Ashok Reddy Soma
> -Original Message-
> From: Michal Simek
> Sent: Monday, March 15, 2021 2:38 PM
> To: Robert Hancock ; Michal Simek
> ; T Karthik Reddy ; Ashok Reddy
> Soma
> Cc: joe.hershber...@ni.com; rfried@gmail.com; u-boot@lists.denx.de
> Subject: Re: [PATCH]
On 3/17/21 10:12 AM, Pratyush Yadav wrote:
> On 17/03/21 09:19AM, Michal Simek wrote:
>> From: T Karthik Reddy
>>
>> Add spi memory operations to relocate manually when
>> CONFIG_NEEDS_MANUAL_RELOC is enabled.
>>
>> Signed-off-by: T Karthik Reddy
>> Acked-by: Ashok Reddy Soma
>>
On 17/03/21 09:19AM, Michal Simek wrote:
> From: T Karthik Reddy
>
> Add spi memory operations to relocate manually when
> CONFIG_NEEDS_MANUAL_RELOC is enabled.
>
> Signed-off-by: T Karthik Reddy
> Acked-by: Ashok Reddy Soma
> Signed-off-by: Michal Simek
> ---
>
> drivers/spi/spi-uclass.c
On Wed, Mar 17, 2021 at 11:10:58AM +0800, Bin Meng wrote:
> In preparation to add SiFive Unmatched board support, let's rename
> the existing fu540 board to unleashed.
>
> Signed-off-by: Bin Meng
>
> ---
>
> Changes in v2:
> - fix a typo in the commit message
> - rename fu540.rst
>
>
From: T Karthik Reddy
Add spi memory operations to relocate manually when
CONFIG_NEEDS_MANUAL_RELOC is enabled.
Signed-off-by: T Karthik Reddy
Acked-by: Ashok Reddy Soma
Signed-off-by: Michal Simek
---
drivers/spi/spi-uclass.c | 9 +
1 file changed, 9 insertions(+)
diff --git
From: T Karthik Reddy
Use __func__ instead for function name in debug.
Use Linux style u32 instead of uint32_t.
Signed-off-by: T Karthik Reddy
Acked-by: Ashok Reddy Soma
Signed-off-by: Michal Simek
---
drivers/spi/xilinx_spi.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
On 3/15/21 8:26 AM, Simon Glass wrote:
Much of the content here is useful only for development. Move it under
that section.
If I apply only this patch:
doc/arch/x86.rst:712:unknown document: ../uefi/u-boot_on_efi
I cannot find any change to x86.rst in the cover letter of your series.
To
On 3/14/21 8:05 PM, Ilias Apalodimas wrote:
A following patch introduces a different logic for loading initrd's
based on the EFI_LOAD_FILE2_PROTOCOL.
Since similar logic can be applied in the future for other system files
(i.e DTBs), let's add some helper functions which will retrieve and
parse
Reviewed-by: Andy Wu
Best Regards
Andy Wu
> -Original Message-
> From: U-Boot On Behalf Of
> yuezhang...@sony.com
> Sent: Wednesday, March 17, 2021 2:45 PM
> To: u-boot@lists.denx.de
> Cc: peng@nxp.com; pa...@antoniou-consulting.com
> Subject: [PATCH] Revert "mmc: sdhci: set to
This reverts commit 17ea3c862865c0d704646f67dbf8412f9ff54f59.
In eMMC specification, for the response-with-busy(R1b, R5b)
command, the DAT0 will driven to LOW as BUSY status, and in
sdhci specification, the transfer complete bit should be wait
for BUSY status de-assert.
All response-with-busy
86 matches
Mail list logo
