It doesn't need to consider start byte address.
If ramdisk size is 0x80 and start address is 0x270, then it's
used until 0x02ef, not 0x02f0. But it's detected to overlapt RD
image, when kernel start address is 0x02f0.
Because it's doing wrong calculation about rd_len.
This
> -Original Message-
> From: Tom Rini
> Sent: Friday, October 16, 2020 8:37 PM
> To: Ley Foon Tan
> Cc: Tan, Ley Foon ; ZY - u-boot b...@lists.denx.de>; See, Chin Liang
> Subject: Re: [PATCH] lib: zlib: Use post-increment only in inffast.c
>
> On Fri, Oct 16, 2020 at 04:40:00AM
> From: Pragnesh Patel [mailto:pragnesh.pa...@sifive.com]
> Sent: Tuesday, October 20, 2020 1:33 PM
> To: u-boot@lists.denx.de; atish.pa...@wdc.com; palmerdabb...@google.com;
> bmeng...@gmail.com; paul.walms...@sifive.com
> Cc: anup.pa...@wdc.com; sagar.ka...@sifive.com; Rick Jian-Zhi Chen(陳建志);
Hi Pragnesh
> From: Bin Meng [mailto:bmeng...@gmail.com]
> Sent: Friday, September 11, 2020 2:48 PM
> To: Pragnesh Patel
> Cc: U-Boot Mailing List; Atish Patra; Anup Patel; Sagar Kadam; Rick Jian-Zhi
> Chen(陳建志); Paul Walmsley; Bin Meng; Lukas Auer; Sean Anderson
> Subject: Re: [PATCH 1/3]
On 10/21/20 1:23 AM, Tom Rini wrote:
> On Wed, Oct 21, 2020 at 12:27:45AM +0200, Marek Vasut wrote:
>> On 10/15/20 5:05 PM, Simon Glass wrote:
>>
>> [...]
>>
>> Add another flag to the DM core which could be assigned to drivers and
>> which makes those drivers call their remove callbacks
On Wed, Oct 21, 2020 at 12:27:45AM +0200, Marek Vasut wrote:
> On 10/15/20 5:05 PM, Simon Glass wrote:
>
> [...]
>
> Add another flag to the DM core which could be assigned to drivers and
> which makes those drivers call their remove callbacks last, just before
> booting OS and
On 10/15/20 5:05 PM, Simon Glass wrote:
[...]
Add another flag to the DM core which could be assigned to drivers and
which makes those drivers call their remove callbacks last, just before
booting OS and after all the other drivers finished with their remove
callbacks. This
On 10/12/20 10:31 AM, Marek Vasut wrote:
[...]
>>> Add another flag to the DM core which could be assigned to drivers and
>>> which makes those drivers call their remove callbacks last, just before
>>> booting OS and after all the other drivers finished with their remove
>>> callbacks. This is
Hi Wolfgang,
On Tue, 20 Oct 2020 at 07:26, Wolfgang Denk wrote:
>
> Dear Simon,
>
> In message
> you
> wrote:
> >
> > > At the moment we have some cumbersome constructs like
> > >set_bootargs="setenv bootargs bla ${var}"
> >
> > Yes it is a real pain. The substitution happens on first
Hi Wolfgang,
On Tue, 20 Oct 2020 at 07:17, Wolfgang Denk wrote:
>
> Dear Simon,
>
> In message
> you
> wrote:
> >
> > > You add something unconditionally to common code which very few
> > > people need. U-Boot size is growing all the time because of such
> > > ... features. This may be
Hi Heinrich,
On Mon, 19 Oct 2020 at 08:45, Heinrich Schuchardt wrote:
>
> On 19.10.20 15:55, Simon Glass wrote:
> > This series adds tests to the fixup_silent-linux() function and extends
> > the 'zimage' command to use it.
> >
> > It also adds a new string-substition feature to allow bootargs
Hi Wolfgang,
On Mon, 19 Oct 2020 at 08:45, Wolfgang Denk wrote:
>
> Dear Simon,
>
> In message <20201019135602.3943835-8-...@chromium.org> you wrote:
> ...
> >
> > It is also useful for zimage to use a buffer, since it does not actually
> > put the Linux command line in the bootargs variable.
>
Hi Wolfgang,
On Mon, 19 Oct 2020 at 08:47, Wolfgang Denk wrote:
>
> Dear Simon Glass,
>
> In message <20201019135602.3943835-10-...@chromium.org> you wrote:
> > At present we only support updating the 'bootargs' environment
> > variable. Add another function to update a buffer instead. This will
On Tue, Oct 20, 2020 at 12:01:02PM -0500, Alex G. wrote:
> On 10/20/20 10:54 AM, Tom Rini wrote:
> > On Tue, Oct 20, 2020 at 09:38:52AM -0500, Alex G. wrote:
> > > On 10/20/20 9:32 AM, Tom Rini wrote:
> > > > On Tue, Oct 20, 2020 at 04:29:36PM +0200, Marek Vasut wrote:
> > > > > On 10/20/20 4:07
On Tue, 20 Oct 2020 10:17:07 -0400
Tom Rini tr...@konsulko.com wrote:
...
> > > > Without video console support it is hard and probably impossible to
> > > > debug on real N900.
> > > >
> > > > So do not disable video console support, it would make fixing and
> > > > testing N900 stuff just more
On 10/20/20 10:54 AM, Tom Rini wrote:
On Tue, Oct 20, 2020 at 09:38:52AM -0500, Alex G. wrote:
On 10/20/20 9:32 AM, Tom Rini wrote:
On Tue, Oct 20, 2020 at 04:29:36PM +0200, Marek Vasut wrote:
On 10/20/20 4:07 PM, Tom Rini wrote:
On Tue, Oct 20, 2020 at 11:05:40AM +0200, Marek Vasut wrote:
On Tue, Oct 20, 2020 at 09:38:52AM -0500, Alex G. wrote:
> On 10/20/20 9:32 AM, Tom Rini wrote:
> > On Tue, Oct 20, 2020 at 04:29:36PM +0200, Marek Vasut wrote:
> > > On 10/20/20 4:07 PM, Tom Rini wrote:
> > > > On Tue, Oct 20, 2020 at 11:05:40AM +0200, Marek Vasut wrote:
> > > > > On 10/20/20
From: Siva Durga Prasad Paladugu
This patch adds support for fru commands "fru capture" and "fru display".
The fru capture parses the FRU table present at an address and stores in a
structure for later use. The fru display prints the content of captured
structured in a readable format.
As of
FMC cards are using FRU format for card identification. That's why add
support for this format.
Signed-off-by: Michal Simek
---
board/xilinx/common/board.c | 83 -
1 file changed, 82 insertions(+), 1 deletion(-)
diff --git a/board/xilinx/common/board.c
Idea is to have something what can be used for board bringup from
generic board perspective.
There is a violation compare to spec that FRU ID is ASCII8 instead of
binary format but this is really for having something to pass boot and
boot to OS which has better generating options.
Also time
There is no need to reference files in common folder back. Simply adding
Makefile to this folder does the job because this "common" location is
already wired in main Makefile.
Signed-off-by: Michal Simek
---
board/xilinx/common/Makefile | 7 +++
board/xilinx/versal/Makefile | 1 -
Hi,
the whole series add support for I2C based FRU eeprom board identification.
EEPROMs are referenced by nvmem alias which was suggested by Rob Herring
(dt maintainer). Previous code was using chosen xlnx,eeprom property.
And because no platform is setting up nvmem alias the code is doing
On 10/20/20 4:32 PM, Tom Rini wrote:
> On Tue, Oct 20, 2020 at 04:29:36PM +0200, Marek Vasut wrote:
>> On 10/20/20 4:07 PM, Tom Rini wrote:
>>> On Tue, Oct 20, 2020 at 11:05:40AM +0200, Marek Vasut wrote:
On 10/20/20 2:27 AM, Reuben Dowle wrote:
>>> What assumptions? Any code that assumes
On 10/20/20 9:32 AM, Tom Rini wrote:
On Tue, Oct 20, 2020 at 04:29:36PM +0200, Marek Vasut wrote:
On 10/20/20 4:07 PM, Tom Rini wrote:
On Tue, Oct 20, 2020 at 11:05:40AM +0200, Marek Vasut wrote:
On 10/20/20 2:27 AM, Reuben Dowle wrote:
What assumptions? Any code that assumes 4 byte
On Tue, Oct 20, 2020 at 04:29:36PM +0200, Marek Vasut wrote:
> On 10/20/20 4:07 PM, Tom Rini wrote:
> > On Tue, Oct 20, 2020 at 11:05:40AM +0200, Marek Vasut wrote:
> >> On 10/20/20 2:27 AM, Reuben Dowle wrote:
> > What assumptions? Any code that assumes 4 byte alignment will also work
>
On 10/20/20 4:07 PM, Tom Rini wrote:
> On Tue, Oct 20, 2020 at 11:05:40AM +0200, Marek Vasut wrote:
>> On 10/20/20 2:27 AM, Reuben Dowle wrote:
> What assumptions? Any code that assumes 4 byte alignment will also work
on 8 byte alignment.
>
> Reverting is not the same as assuming
On Tue, Oct 20, 2020 at 11:30:51AM +0200, Pali Rohár wrote:
> Hello!
>
> On Sunday 18 October 2020 21:17:43 Tom Rini wrote:
> > On Sun, Oct 18, 2020 at 10:59:36PM +0200, Pali Rohár wrote:
> > > On Sunday 18 October 2020 22:54:41 Anatolij Gustschin wrote:
> > > > If you need video console support,
On Tue, Oct 20, 2020 at 11:05:40AM +0200, Marek Vasut wrote:
> On 10/20/20 2:27 AM, Reuben Dowle wrote:
> >>> What assumptions? Any code that assumes 4 byte alignment will also work
> >> on 8 byte alignment.
> >>>
> >>> Reverting is not the same as assuming ALIGN(...4) if incoming data is not
> >>
Dear Simon,
In message
you wrote:
>
> > At the moment we have some cumbersome constructs like
> >set_bootargs="setenv bootargs bla ${var}"
>
> Yes it is a real pain. The substitution happens on first parse two, so
> you have to put these commands in separate variables if you are
> building
Dear Simon,
In message
you wrote:
>
> I did wonder about the empty env var thing. IMO it would be nice to
> support empty variables, so we can distinguish between an empty one
> and a missing one.
What exactly is the use case for this that justifies the additional
code needed to implement this
Dear Simon,
In message
you wrote:
>
> > You add something unconditionally to common code which very few
> > people need. U-Boot size is growing all the time because of such
> > ... features. This may be acceptable on the systems you have in
> > mind, but I consider this selfish.
>
> Did you
On 10/20/20 8:47 PM, Tero Kristo wrote:
> On 20/10/2020 14:07, Jaehoon Chung wrote:
>> Dear Tero,
>>
>> On 6/12/20 9:41 PM, Tero Kristo wrote:
>>> These cases are typically fatal and are difficult to debug for random
>>> users. Add checks for detecting overlapping images and abort if overlap
>>>
The following changes since commit 7ec87e4192215815b658c3f8b34e4be010103149:
Merge tag 'u-boot-atmel-2021.01-b' of
https://gitlab.denx.de/u-boot/custodians/u-boot-atmel (2020-10-19
09:29:05 -0400)
are available in the Git repository at:
git://git.denx.de/u-boot-sh.git master
for you to
I am trying to run mtest in U-Boot to verify if my RAM (on-board DDR3
on PowerPC based boards) is working fine. However, mtest is giving
following errors when I run the test:
Hit any key to stop autoboot: 0
=> mtest 0x4 0x4000 0xaabbccdd 0x1
Testing 0004 ... 4000:
Iteration: 1
On 20/10/2020 14:07, Jaehoon Chung wrote:
Dear Tero,
On 6/12/20 9:41 PM, Tero Kristo wrote:
These cases are typically fatal and are difficult to debug for random
users. Add checks for detecting overlapping images and abort if overlap
is detected.
I have a question about your patch.. because
Dear Tero,
On 6/12/20 9:41 PM, Tero Kristo wrote:
> These cases are typically fatal and are difficult to debug for random
> users. Add checks for detecting overlapping images and abort if overlap
> is detected.
I have a question about your patch.. because I have confused...
So i want to clear
The following changes since commit 7ec87e4192215815b658c3f8b34e4be010103149:
Merge tag 'u-boot-atmel-2021.01-b' of
https://gitlab.denx.de/u-boot/custodians/u-boot-atmel (2020-10-19
09:29:05 -0400)
are available in the Git repository at:
git://git.denx.de/u-boot-usb.git master
for you to
On 10/16/20 6:32 PM, Patrick DELAUNAY wrote:
> Hi Marek,
Hi,
[...]
On 10/15/20 2:49 PM, Patrick Delaunay wrote:
> On some board, the ID pin is not connected so the B session must be
> overridden with "u-boot,force_b_session_valid" but the VBus sensing
> must continue to be
Hello!
On Sunday 18 October 2020 21:17:43 Tom Rini wrote:
> On Sun, Oct 18, 2020 at 10:59:36PM +0200, Pali Rohár wrote:
> > On Sunday 18 October 2020 22:54:41 Anatolij Gustschin wrote:
> > > If you need video console support, then please convert to DM_VIDEO.
> >
> > Ok, but I'm waiting until
Hi Stefan,
On Tue, Oct 20 2020, Stefan Roese wrote:
> On 19.10.20 07:24, Baruch Siach wrote:
>> On Sun, Oct 18 2020, Chris Packham wrote:
>>> On Mon, Oct 19, 2020 at 1:59 AM Baruch Siach wrote:
This series adds NAND flash support to Aramda 8k systems. Patches make the
necessary
Hi Stefan,
On Tue, Oct 20 2020, Stefan Roese wrote:
> On 18.10.20 16:11, Baruch Siach wrote:
>> Boot of Armada 8040 rev B0 hangs when U-Boot attempts to initialize the PCIe
>> serdes. Adapt patches from downstream Marvell tree that move serdes
>> initialization to ATF.
>>
>> This series requires
Enable the CMD_MDIO Kconfig option by removing the "is not set"
indication from all the defconfigs for this SoC.
Signed-off-by: Ioana Ciornei
---
configs/ls1088aqds_qspi_SECURE_BOOT_defconfig| 1 -
configs/ls1088aqds_qspi_defconfig| 1 -
On 10/20/20 2:27 AM, Reuben Dowle wrote:
>>> What assumptions? Any code that assumes 4 byte alignment will also work
>> on 8 byte alignment.
>>>
>>> Reverting is not the same as assuming ALIGN(...4) if incoming data is not
>> already aligned to 4 bytes (as was the case when I saw crashes).
>>
>>
Hi Baruch,
Hi Chris,
On 19.10.20 07:24, Baruch Siach wrote:
Hi Chris,
On Sun, Oct 18 2020, Chris Packham wrote:
On Mon, Oct 19, 2020 at 1:59 AM Baruch Siach wrote:
This series adds NAND flash support to Aramda 8k systems. Patches make the
necessary changes to the pxa3xx_nand driver and DT
do_save() function defined in fs.c also supports FAT file system
re-use the same for fatwrite command.
Also fix the FAT test script to match the expected output.
Signed-off-by: Lad Prabhakar
Reviewed-by: Biju Das
---
v1->v2
* Fixed FAT test scripts
* Sandbox test results: 655 passed, 76
Hi Baruch,
On 18.10.20 16:11, Baruch Siach wrote:
Boot of Armada 8040 rev B0 hangs when U-Boot attempts to initialize the PCIe
serdes. Adapt patches from downstream Marvell tree that move serdes
initialization to ATF.
This series requires upstream ATF version 2.1 or newer.
Is there a way to
On 18.10.20 21:43, Marek Behun wrote:
On Sun, 18 Oct 2020 17:11:11 +0300
Baruch Siach wrote:
From: Grzegorz Jaszczyk
Replace all comphy initialization with appropriate smc calls. It will
result with triggering synchronous exception that is handled by Secure
Monitor code in EL3. Then the
There is no reason to have ZYNQ specific Kconfig macro in generic location
to be visible for all other SoCs. That's why move it to Xilinx common
location to be visible only for us.
Also introduce new bool entry ZYNQ_MAC_IN_EEPROM to have also an option to
disable it or enable. This has connection
Hi Meenakshi,
> -Original Message-
> From: U-Boot On Behalf Of
> meenakshi.aggar...@nxp.com
> Sent: Monday, September 7, 2020 6:12 PM
> To: u-boot@lists.denx.de; Priyanka Jain
> Cc: Varun Sethi ; Meenakshi Aggarwal
>
> Subject: [PATCH v3 1/2] armv8: lx2162a: Add Soc changes to support
On Tue, 2020-10-20 at 14:15 +0800, Bin Meng wrote:
> Hi Chunfeng,
>
> On Tue, Oct 20, 2020 at 10:22 AM Chunfeng Yun
> wrote:
> >
> > On Tue, 2020-10-20 at 00:15 +0200, Marek Vasut wrote:
> > > On 10/19/20 2:19 PM, Chunfeng Yun wrote:
> > > > Due to the following to patches:
> > > > 4a1989c0bc77
On 10/20/20 12:20 PM, Y.b. Lu wrote:
> Hi Jaehoon,
>
>> -Original Message-
>> From: Jaehoon Chung
>> Sent: Tuesday, October 20, 2020 5:52 AM
>> To: Y.b. Lu ; u-boot@lists.denx.de; Peng Fan
>>
>> Subject: Re: [PATCH 2/2] mmc: fsl_esdhc: make sure delay chain locked for
>> HS400
>>
>>
From: Siva Durga Prasad Paladugu
This patch adds support for encryption and decryption on a given data
blob using different key sources such as userkey(KUP), device key and
PUF key. Inorder to support this a new zynqmp command(zynqmp aes) has
been introduced.
Command:
zynqmp aes srcaddr ivaddr
On 19/10/20 10:16 pm, Dario Binacchi wrote:
> Add drivers/clk/ti/ folder and move all TI's code in this folder for
> better maintenance.
>
> Signed-off-by: Dario Binacchi
> ---
>
> (no changes since v1)
>
> drivers/clk/Kconfig | 40 +-
>
From: T Karthik Reddy
This patch adds support for SHA3 command. It takes data blob
as input and generates 48 bytes sha3 hash value.
Signed-off-by: T Karthik Reddy
Signed-off-by: Siva Durga Prasad Paladugu
Signed-off-by: Michal Simek
---
Changes in v2:
- fix cmd_tbl
- Add - to help
From: T Karthik Reddy
This patch adds support for RSA command, performs RSA encrypt &
RSA decrypt on data blob of key size.
Signed-off-by: T Karthik Reddy
Signed-off-by: Siva Durga Prasad Paladugu
Signed-off-by: Michal Simek
---
Changes in v2:
- fix cmd_tbl
- Add - in help
By default 48B sha3 hash value is written to srcaddr which is not the best
solution in case of that you want to use data for other operations. That's
why add key_addr optional parameters which enables to write 48B sha3 hash
value to specified address.
Signed-off-by: Michal Simek
Tested-by: Ashok
Hi,
the series is adding support for security features on zynqmp devices.
Thanks,
Michal
Changes in v2:
- Fix cmd_tbl parameters
- Add - in help
- fix cmd_tbl
- Add - in help
- fix cmd_tbl
- Add - to help
- Include to "arm: zynqmp: Add zynqmp specific command for security
features" series
-
On 19/10/20 10:22 pm, Dario Binacchi wrote:
> Enabling the domain clock is performed by the sysc interconnect target
> module driver during the video device probing.
>
> Signed-off-by: Dario Binacchi
>
> ---
>
> (no changes since v3)
>
> Changes in v3:
> - Remove clock domain
Hi Chunfeng,
On Tue, Oct 20, 2020 at 10:22 AM Chunfeng Yun wrote:
>
> On Tue, 2020-10-20 at 00:15 +0200, Marek Vasut wrote:
> > On 10/19/20 2:19 PM, Chunfeng Yun wrote:
> > > Due to the following to patches:
> > > 4a1989c0bc77 ("dm: Don't undefine dev_xxx macros")
> > > 69dae8902b16
On Tue, Oct 20, 2020 at 1:33 PM Pragnesh Patel
wrote:
>
> Signed-off-by: Pragnesh Patel
> ---
> arch/riscv/dts/fu540-c000-u-boot.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Bin Meng
60 matches
Mail list logo