Dear Simon,
In message
you wrote:
>
> > I think this is the wrong way to address a problem.
> >
> > Instead, zimage should use bootargs as well.
>
> OK I can add that. But for testing purposes it is still good to be
> able to have the feature in a function that can be called without
> going thro
Signed-off-by: Ran Wang
---
drivers/usb/dwc3/dwc3-generic.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc3/dwc3-generic.c b/drivers/usb/dwc3/dwc3-generic.c
index d949083..66c878a 100644
--- a/drivers/usb/dwc3/dwc3-generic.c
+++ b/drivers/usb/dwc3/dwc3-generic.c
@@ -449,6 +44
Enable support for one of USB gadget function: ums. Also enable related
dependency items.
Signed-off-by: Ran Wang
---
configs/ls1088aqds_defconfig | 5 +
configs/ls1088aqds_qspi_defconfig| 5 +
configs/ls1088aqds_sdcard_ifc_defconfig | 5 +
configs/ls1088aqds_sdc
Some SoC such as Layerscape serials which don't require PHY related
programming in dwc3-generic.c. In this case (CONFIG_PHY is not set), the
dwc3_setup_phy() will return -ENOTSUPP, causing the whole init fail.
That should be avoided.
Signed-off-by: Ran Wang
---
drivers/usb/dwc3/dwc3-generic.c |
Benefit is, besides host mode, now user can choose device mode with
setting of dr_mode = “peripheral”;
Signed-off-by: Ran Wang
---
arch/arm/dts/fsl-ls1088a.dtsi | 40 ++--
1 file changed, 30 insertions(+), 10 deletions(-)
diff --git a/arch/arm/dts/fsl-ls1088a
Enable the undefined length INCR burst type and set INCRx. Different
platforms may has the different burst size type. In order to get best
performance, we need to tune the burst size to one special value,
instead of the default value.
Refer to Linux commit (“usb: dwc3: Enable undefined length INCR
Some NXP Layerscape platforms are required to disable receiver detection in
P3 for correct detection of USB devices. If GUSB3PIPECTL(DISRXDETINP3)
is set, Core will change PHY power state to P2 and then perform
receiver detection. After receiver detection, Core will change
PHY power state to P3. Sa
Hello,
The purpose of this patch set is to switch from driver xhci-fsl to
dwc3-generic for DWC3 IP on Layerscape platforms. Whith this change, now
user can enable USB device mode by merely updating property 'dr_mode'
accordingly.
I also port some DWC3's errata workaorund from driver
xhci-fsl (by
Register Global frame length adjustment is used to do frame length
adjustment for SOF/ITP counter which is running on the ref_clk. Allow
updating it could help on avoiding potential USB 2.0 devices time-out over
a longer run.
Refer to Linux commit db2be4e9e30c (“usb: dwc3: Add frame length adjustm
The following changes since commit 3d19a7ee8ca7af01f75ff24622ea3c9840cd5bca:
test: Fix sandbox tests failing to build (2020-10-17 09:03:22 -0400)
are available in the Git repository at:
https://gitlab.denx.de/u-boot/custodians/u-boot-efi.git
tags/efi-2021-01-rc1-2
for you to fetch changes u
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 patch
> -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 +080
> 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] riscv:
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 la
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 aft
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 is
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 ne
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 pars
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 accep
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 to
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 PM
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 c
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:
O
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 2:27
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 now
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 b/boa
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 should
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 -
board/xil
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 nothing
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 alignment
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
> o
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 A
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 t
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 se
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
>>> is
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 fetc
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
FA
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 I
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 wha
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 fet
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 handl
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 othe
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 cha
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 u
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 -
configs/ls1088aqds_sdcard_qspi
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).
>>
>> Ca
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 f
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 skipped
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 d
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 Secu
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 t
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 L
59 matches
Mail list logo
