Hi,
I would also like to add OpenSSL library into U-Boot. Can you help me on this?
Kind regards,
Daniel Selvan D.
--
P Please consider the environment before printing this email.
Hello,
Am 18.11.19 um 22:15 schrieb Simon Goldschmidt:
> Am 18.11.2019 um 19:08 schrieb Wolfgang Grandegger:
>> Hello,
>>
>> I'm trying to understand what is necessary to get mainline U-Boot
>> booting from the eMMC of an Arria10 board, which is significantly
>> different to the Cyclone 5.
>
>
On Fri, Nov 29, 2019 at 06:46:40AM +, Priyanka Jain wrote:
>
>
> >-Original Message-
> >From: U-Boot-Custodians On
> >Behalf Of Heinrich Schuchardt
> >Sent: Tuesday, November 26, 2019 4:46 AM
> >To: u-boot-custodi...@lists.denx.de; u-boot-board-
> >maintain...@lists.denx.de; U-Boot
>-Original Message-
>From: U-Boot-Custodians On
>Behalf Of Heinrich Schuchardt
>Sent: Tuesday, November 26, 2019 4:46 AM
>To: u-boot-custodi...@lists.denx.de; u-boot-board-
>maintain...@lists.denx.de; U-Boot Mailing List
>Subject: [U-Boot-Custodians] [RFC] Eliminate boards not using
On Thu, Nov 28, 2019 at 10:40:38AM +0100, Marek Vasut wrote:
> On 11/28/19 7:22 AM, Heinrich Schuchardt wrote:
> > On 11/26/19 6:07 PM, Marek Vasut wrote:
> >> On 11/26/19 5:52 PM, Tom Rini wrote:
> >>> On Tue, Nov 26, 2019 at 05:47:48PM +0100, Marek Vasut wrote:
> On 11/26/19 5:26 PM, Tom
On Thu, Nov 28, 2019 at 12:52 PM Igor Opaniuk wrote:
>
> Hi all,
>
> U-boot imx-specific bootaux command doesn't work properly
> with the old legacy binary format if the DCACHE is enabled (I've
> tested only executing from OCRAM) in the mainline U-boot.
>
> Interesting thing is that invocation of
Hi all,
U-boot imx-specific bootaux command doesn't work properly
with the old legacy binary format if the DCACHE is enabled (I've
tested only executing from OCRAM) in the mainline U-boot.
Interesting thing is that invocation of `dcache flush` before bootaux
doesn't help, but only full disabling
On 11/28/19 7:22 AM, Heinrich Schuchardt wrote:
> On 11/26/19 6:07 PM, Marek Vasut wrote:
>> On 11/26/19 5:52 PM, Tom Rini wrote:
>>> On Tue, Nov 26, 2019 at 05:47:48PM +0100, Marek Vasut wrote:
On 11/26/19 5:26 PM, Tom Rini wrote:
> On Tue, Nov 26, 2019 at 09:11:51AM +0100, Marek Vasut
On 11/26/19 6:07 PM, Marek Vasut wrote:
On 11/26/19 5:52 PM, Tom Rini wrote:
On Tue, Nov 26, 2019 at 05:47:48PM +0100, Marek Vasut wrote:
On 11/26/19 5:26 PM, Tom Rini wrote:
On Tue, Nov 26, 2019 at 09:11:51AM +0100, Marek Vasut wrote:
On 11/26/19 12:16 AM, Heinrich Schuchardt wrote:
Dear
Hi Anand,
On 2019/11/25 下午1:06, Anand Moon wrote:
Hi Kever,
As per Rockchip RK3399 TRM V1.4 Part1 RK3399 have
dual-core Cortex-A72 and a quad-core Cortex-A53 +
Cortex-M0 for power management firmware.
U-Boot use the default primary core which is power on enabled Cortex-A53 0,
and other
On 11/26/19 5:52 PM, Tom Rini wrote:
> On Tue, Nov 26, 2019 at 05:47:48PM +0100, Marek Vasut wrote:
>> On 11/26/19 5:26 PM, Tom Rini wrote:
>>> On Tue, Nov 26, 2019 at 09:11:51AM +0100, Marek Vasut wrote:
On 11/26/19 12:16 AM, Heinrich Schuchardt wrote:
> Dear maintainers,
Hi,
On Tue, Nov 26, 2019 at 05:31:26PM +0100, Lukasz Majewski wrote:
> Hi Tom,
>
> > On Tue, Nov 26, 2019 at 09:11:51AM +0100, Marek Vasut wrote:
> > > On 11/26/19 12:16 AM, Heinrich Schuchardt wrote:
> > > > Dear maintainers,
> > >
> > > Hi,
> > >
> > > > we have been trying to move to the
On Tue, Nov 26, 2019 at 05:47:48PM +0100, Marek Vasut wrote:
> On 11/26/19 5:26 PM, Tom Rini wrote:
> > On Tue, Nov 26, 2019 at 09:11:51AM +0100, Marek Vasut wrote:
> >> On 11/26/19 12:16 AM, Heinrich Schuchardt wrote:
> >>> Dear maintainers,
> >>
> >> Hi,
> >>
> >>> we have been trying to move to
On 11/26/19 5:26 PM, Tom Rini wrote:
> On Tue, Nov 26, 2019 at 09:11:51AM +0100, Marek Vasut wrote:
>> On 11/26/19 12:16 AM, Heinrich Schuchardt wrote:
>>> Dear maintainers,
>>
>> Hi,
>>
>>> we have been trying to move to the driver model for several years now.
>>> Starting in 2018 we have added
Hi Tom,
> On Tue, Nov 26, 2019 at 09:11:51AM +0100, Marek Vasut wrote:
> > On 11/26/19 12:16 AM, Heinrich Schuchardt wrote:
> > > Dear maintainers,
> >
> > Hi,
> >
> > > we have been trying to move to the driver model for several years
> > > now. Starting in 2018 we have added warnings to
On Tue, Nov 26, 2019 at 09:11:51AM +0100, Marek Vasut wrote:
> On 11/26/19 12:16 AM, Heinrich Schuchardt wrote:
> > Dear maintainers,
>
> Hi,
>
> > we have been trying to move to the driver model for several years now.
> > Starting in 2018 we have added warnings to the Makefile that boards not
>
On 11/26/19 12:16 AM, Heinrich Schuchardt wrote:
> Dear maintainers,
Hi,
> we have been trying to move to the driver model for several years now.
> Starting in 2018 we have added warnings to the Makefile that boards not
> supporting the driver model will be eliminated. Still 24 % of the
>
Hi Kever,
As per Rockchip RK3399 TRM V1.4 Part1 RK3399 have
dual-core Cortex-A72 and a quad-core Cortex-A53 +
Cortex-M0 for power management firmware.
So can this feature be enabled for all RK3399 SBC.
or is this meant for specific RK3399 family of processor.
-Anand
>-Original Message-
>From: U-Boot On Behalf Of Florinel Iordache
>Sent: Tuesday, November 19, 2019 3:58 PM
>To: u-boot@lists.denx.de
>Subject: [U-Boot] [u-boot][PATCH v2] drivers/fsl-mc: Support DPSPARSER object
>and apply spb command
>
>Add support for DPSPARSE
Add support for DPSPARSER object (create/destroy, open/close, apply spb)
required to configure Soft Parser by using MC. Also add uboot command to
apply Soft Parser Blob with command: fsl_mc apply spb
Signed-off-by: Florinel Iordache
---
drivers/net/fsl-mc/Kconfig | 12 ++
Am 18.11.2019 um 19:08 schrieb Wolfgang Grandegger:
Hello,
I'm trying to understand what is necessary to get mainline U-Boot
booting from the eMMC of an Arria10 board, which is significantly
different to the Cyclone 5.
Unfortunately, my playground here is limited to Cyclone 5, but from the
Hello,
I'm trying to understand what is necessary to get mainline U-Boot
booting from the eMMC of an Arria10 board, which is significantly
different to the Cyclone 5.
I'm playing with U-Boot v2019.10! I find some related documentation at
[1]. Section "Arria 10 SoC - Boot from SD Card " seems to
Hi Simon,
On Sun, Nov 17, 2019 at 11:46 PM Simon Glass wrote:
>
> Hi Bin,
>
> On Sun, 17 Nov 2019 at 07:07, Bin Meng wrote:
> >
> > Hi Simon,
> >
> > On Wed, Nov 6, 2019 at 7:12 AM Tom Rini wrote:
> > >
> > > On Tue, Nov 05, 2019 at 05:23:51AM -0700, Simon Glass wrote:
> > >
> > > > Hi Tom,
>
> -Original Message-
> From: Jagdish Gediya
> Sent: 2019年11月18日 12:50
> To: Wen He ; u-boot@lists.denx.de;
> u-b...@linux.nxdi.nxp.com
> Cc: Wen He
> Subject: RE: [u-boot] [v4] armv8: ls1028ardb: enable DisplayPort Power
> support
>
> Hi Wen,
>
> > -Original Message-
> >
Hi Wen,
> -Original Message-
> From: u-boot-boun...@linux.nxdi.nxp.com boun...@linux.nxdi.nxp.com> On Behalf Of Wen He
> Sent: Wednesday, November 6, 2019 1:20 PM
> To: u-boot@lists.denx.de; u-b...@linux.nxdi.nxp.com
> Cc: Wen He
> Subject: [u-boot] [v4] armv8: ls1028ardb: enable
Hi Bin,
On Sun, 17 Nov 2019 at 07:07, Bin Meng wrote:
>
> Hi Simon,
>
> On Wed, Nov 6, 2019 at 7:12 AM Tom Rini wrote:
> >
> > On Tue, Nov 05, 2019 at 05:23:51AM -0700, Simon Glass wrote:
> >
> > > Hi Tom,
> > >
> > > Passing run here:
> > >
> > >
Hi Simon,
On Wed, Nov 6, 2019 at 7:12 AM Tom Rini wrote:
>
> On Tue, Nov 05, 2019 at 05:23:51AM -0700, Simon Glass wrote:
>
> > Hi Tom,
> >
> > Passing run here:
> >
> > https://gitlab.denx.de/u-boot/custodians/u-boot-dm/pipelines/1210
> >
> >
> > The following changes since commit
Hello Tom,
I tried to trigger a travis build for patches I want to post, see:
https://travis-ci.org/hsdenx/u-boot-test/builds/611740123
I see now 2 problems with travis builds:
- "NXP ARM32" and "32bit sun8i" take too long, I splitted them into
2 jobs locally, see patches:
On Wed, Oct 30, 2019 at 02:11:28PM -0500, Adam Ford wrote:
> On Wed, Oct 30, 2019 at 12:13 PM Tom Rini wrote:
> >
> > Hey all,
> >
> > It's a few days past release day, and here finally is v2020.01-rc1. The
> > delay was over hoping to be able to pull in one more big clean up series
> > that we
On Wed, Oct 30, 2019 at 12:13 PM Tom Rini wrote:
>
> Hey all,
>
> It's a few days past release day, and here finally is v2020.01-rc1. The
> delay was over hoping to be able to pull in one more big clean up series
> that we need, and I want to take, but needs a little more work. Doing
> that has
On 21.10.19 12:15, Kever Yang wrote:
>
>
> On 2019/10/21 下午6:06, Soeren Moch wrote:
>> > Since we move the ATF bl31 entry for 64bit CPUs to 0x4, we need to
>> > limit the SPL size in 0x4(start from 0) so that we don't need to do
>> > the relocate for ATF loading.
>> > Note that there
On 2019/10/21 下午6:06, Soeren Moch wrote:
> Since we move the ATF bl31 entry for 64bit CPUs to 0x4, we need to
> limit the SPL size in 0x4(start from 0) so that we don't need to do
> the relocate for ATF loading.
> Note that there will be separate BSS, STACK and MALLOC heap, so the size
> Since we move the ATF bl31 entry for 64bit CPUs to 0x4, we need to
> limit the SPL size in 0x4(start from 0) so that we don't need to do
> the relocate for ATF loading.
> Note that there will be separate BSS, STACK and MALLOC heap, so the size
> 0x4(256KB) should be enough for SPL
On 18.10.2019 09:20, Priyanka Jain wrote:
>
>
>> -Original Message-
>> From: u-boot-boun...@linux.nxdi.nxp.com > boun...@linux.nxdi.nxp.com> On Behalf Of Laurentiu Tudor
>> Sent: Thursday, October 17, 2019 2:52 PM
>> To: u-boot@lists.denx.de; Prabhakar X
>> Subject: [u-boot] [PATCH
>-Original Message-
>From: u-boot-boun...@linux.nxdi.nxp.com boun...@linux.nxdi.nxp.com> On Behalf Of Laurentiu Tudor
>Sent: Thursday, October 17, 2019 2:52 PM
>To: u-boot@lists.denx.de; Prabhakar X
>Subject: [u-boot] [PATCH 4/6] armv8: fsl-layerscape: add missing SATA3 and
>SATA4 base
>-Original Message-
>From: u-boot-boun...@linux.nxdi.nxp.com boun...@linux.nxdi.nxp.com> On Behalf Of Laurentiu Tudor
>Sent: Thursday, October 17, 2019 2:52 PM
>To: u-boot@lists.denx.de; Prabhakar X
>Subject: [u-boot] [PATCH 5/6] armv8: lx2160a: add icid setup for platform
>devices
>
> > From: Atish Patra [mailto:atish.pa...@wdc.com]
> > Sent: Thursday, October 10, 2019 1:34 AM
> > To: u-boot@lists.denx.de
> > Cc: Atish Patra; Marek Vasut; Rick Jian-Zhi Chen(陳建志); David
> > Abdurachmanov; paul.walms...@sifive.com
> > Subject: [U-Boot PATCH v2] RISC-V: Align boot image header
The released Linux boot image header in v5.3 is different from the
one present in U-Boot. Align the header with the new version. The
changes in Linux are backward compatible. Previous U-Boot releases
with older header will continue to work as well. As v5.3 kernel is
the first one to support image
On 07/10/19 22:26, Pierre-Jean Texier wrote:
> Hi Stefano,
>
> Le 07/10/2019 à 21:58, Stefano Babic a écrit :
>> Hi Pierre-Jen,
>>
>> On 07/10/19 20:44, Pierre-Jean Texier wrote:
>>> Stefano, Peng,
>>>
>>> I just compiled a fresh U-Boot with u-boot-imx/next and It looks
>>> like commit 34f2feb
Hi Stefano,
Le 07/10/2019 à 21:58, Stefano Babic a écrit :
Hi Pierre-Jen,
On 07/10/19 20:44, Pierre-Jean Texier wrote:
Stefano, Peng,
I just compiled a fresh U-Boot with u-boot-imx/next and It looks
like commit 34f2feb ("imx: mmc_env: update runtime SD/MMC boot env
device") [1]
breaks my
Hi Pierre-Jen,
On 07/10/19 20:44, Pierre-Jean Texier wrote:
> Stefano, Peng,
>
> I just compiled a fresh U-Boot with u-boot-imx/next and It looks
> like commit 34f2feb ("imx: mmc_env: update runtime SD/MMC boot env
> device") [1]
> breaks my WaRP7 (but the same for the Pico-Pi i.MX7, tested by
Stefano, Peng,
I just compiled a fresh U-Boot with u-boot-imx/next and It looks
like commit 34f2feb ("imx: mmc_env: update runtime SD/MMC boot env
device") [1]
breaks my WaRP7 (but the same for the Pico-Pi i.MX7, tested by Joris in
CC),
see logs after:
U-Boot 2019.10-rc4-00232-gd03193d (Oct
Applied this series to u-boot-atmel/next, thanks !
On 27.09.2019 16:08, Tudor Ambarus - M18064 wrote:
> From: Tudor Ambarus
>
> Add support for sam9x60 SOC, sam9x60ek board, dts, NAND and QSPI.
> Add defconfigs for MMC, NAND and QSPI.
>
> v3:
> - Enable MII utility commands and phy in qspi &
Cc'ing the SABRELITE maintainers:
$ ./scripts/get_maintainer.pl -f hw/misc/imx6_ccm.c
Peter Maydell (odd fixer:SABRELITE / i.MX6)
Jean-Christophe Dubois (reviewer:SABRELITE / i.MX6)
qemu-...@nongnu.org (open list:SABRELITE / i.MX6)
On 10/3/19 1:54 PM, Bin Meng wrote:
+QEMU developers ML
On
+QEMU developers ML
On Thu, Oct 3, 2019 at 7:37 PM Waseem ALKurdi
wrote:
>
> Dear all,
>
> I'm trying to get mainline U-Boot to boot on mainline QEMU 4.1.0 for the
> 'sabrelite' board, using the configuration 'mx6qsabrelite_defconfig'.
>
> It's not booting at all. Actually, not a single U-Boot
Dear all,
I'm trying to get mainline U-Boot to boot on mainline QEMU 4.1.0 for the
'sabrelite' board, using the configuration 'mx6qsabrelite_defconfig'.
It's not booting at all. Actually, not a single U-Boot build for an i.MX board
would boot, with the exception of 'imx25-pdk'.
I'm compiling
Hi Bin,
On Wed, Oct 2, 2019 at 6:33 PM Bin Meng wrote:
>
> On Wed, Oct 2, 2019 at 1:01 AM Sagar Shrikant Kadam
> wrote:
> >
> > This patch adds a DM based driver model for gpio controller present in
> > FU540-C000 SoC on HiFive Unleashed A00 board. This SoC has one GPIO
> > bank and 16 GPIO
On Wed, Oct 2, 2019 at 1:01 AM Sagar Shrikant Kadam
wrote:
>
> This patch adds a DM based driver model for gpio controller present in
> FU540-C000 SoC on HiFive Unleashed A00 board. This SoC has one GPIO
> bank and 16 GPIO lines in total, out of which GPIO0 to GPIO9 and
> GPIO15 are routed to the
Enable the DM based GPIO driver for FU540-C000 SoC.
Signed-off-by: Sagar Shrikant Kadam
Reviewed-by: Bin Meng
Tested-by: Bin Meng
---
board/sifive/fu540/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/board/sifive/fu540/Kconfig b/board/sifive/fu540/Kconfig
index
This patch adds a DM based driver model for gpio controller present in
FU540-C000 SoC on HiFive Unleashed A00 board. This SoC has one GPIO
bank and 16 GPIO lines in total, out of which GPIO0 to GPIO9 and
GPIO15 are routed to the J1 header on the board.
This implementation is ported from linux
U-Boot currently is missing GPIO support for FU540-C000 SoC which is
mounted on HiFive Unleashed A00 board. This patch is intended to add DM
based GPIO controller driver in order to access GPIO pins within the SoC
using GPIO command in U-Boot. More details on the GPIO controller within
the SoC can
On 27/09/2019 18:05, Tom Rini wrote:
> Hey all,
>
> I'm currently kicking test.py to use Python 3 instead of Python 2.7 and
> seeing places where it would (seemingly) be nice to be able to say that
> we have Python 3.6 as our minimum version. To do this however we'll
> have to tell people
> Regards,
> Matthias
>
>>
>> -Thanks
>>
>> ___
>> U-Boot mailing list
>> U-Boot@lists.denx.de
>> https://lists.denx.de/listinfo/u-boot
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
On 2019-09-27, Heinrich Schuchardt wrote:
> On 9/27/19 6:36 PM, Peter Robinson wrote:
>>> I'm currently kicking test.py to use Python 3 instead of Python 2.7 and
>>> seeing places where it would (seemingly) be nice to be able to say that
>>> we have Python 3.6 as our minimum version. To do this
On 9/27/19 6:36 PM, Peter Robinson wrote:
>>
>> I'm currently kicking test.py to use Python 3 instead of Python 2.7 and
>> seeing places where it would (seemingly) be nice to be able to say that
>> we have Python 3.6 as our minimum version. To do this however we'll
>> have to tell people using
From: Tudor Ambarus
Cope with the offsets defined at:
https://www.at91.com/linux4sam/pub/Linux4SAM/SambaSubsections/demo_nandflash_map_lnx4sam6x.png
The environment starts at 0x14 and it's of size 0x2.
The device tree starts at 0x18 and it's of size 0x8.
The zImage starts at
From: Tudor Ambarus
The sam9x60 qspi controller uses 2 clocks, one for the peripheral register
access, the other for the qspi core and phy. Both are mandatory.
Enable the qspi node together with the SST26VF064B qspi nor flash
memory. Booting from the QSPI NOR flash is now possible.
From: Sandeep Sheriker Mallikarjun
add device tree files for sam9x60ek board with below changes.
- Add initial device nodes (pmc, pinctrl, sdhc, dbgu & pit)
- Add the reg property for the pinctrl node.
- Add the "u-boot,dm-pre-reloc" property to determine which nodes
are used by the
From: Tudor Ambarus
Boot from nand flash.
Signed-off-by: Tudor Ambarus
---
board/atmel/sam9x60ek/MAINTAINERS | 1 +
configs/sam9x60ek_nandflash_defconfig | 53 +++
2 files changed, 54 insertions(+)
create mode 100644 configs/sam9x60ek_nandflash_defconfig
From: Tudor Ambarus
Boot from QSPI nor flash.
The at91bootstrap, u-boot, u-boot env redundant, u-boot env,
device tree and kernel will reside in the QSPI nor flash.
The rootfs will reside in the NAND flash.
Signed-off-by: Tudor Ambarus
---
board/atmel/sam9x60ek/MAINTAINERS | 1
From: Nicolas Ferre
Add Ethernet controller to dtsi file and enable it on sam9x60ek
platform connected with rmii.
Signed-off-by: Nicolas Ferre
---
arch/arm/dts/sam9x60.dtsi | 31 +++
arch/arm/dts/sam9x60ek.dts | 5 +
2 files changed, 36 insertions(+)
diff
From: Tudor Ambarus
The Special Function Registers (SFR) are present in sam9x5 and
sam9x60 too, rename sama5_sfr to at91_sfr.h.
Signed-off-by: Tudor Ambarus
---
arch/arm/mach-at91/armv7/sama5d4_devices.c | 2 +-
arch/arm/mach-at91/atmel_sfr.c | 2
From: Tudor Ambarus
- EBI Chip Select Register is now in SFR,
- the pins are set to default values,
- timings are matching MT29F4G08BABWP's nand flash requirements.
Signed-off-by: Tudor Ambarus
---
board/atmel/sam9x60ek/sam9x60ek.c | 61 +++
From: Nicolas Ferre
Add this new compatibility string for matching sam9x60 product
macb.
Signed-off-by: Nicolas Ferre
---
drivers/net/macb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/macb.c b/drivers/net/macb.c
index c99cf663a416..e0f7b2350b20 100644
---
From: Sandeep Sheriker Mallikarjun
Add new Microchip sam9x60 SoC based on an ARM926.
Signed-off-by: Sandeep Sheriker Mallikarjun
[tudor.amba...@microchip.com: fix SFR definition]
Signed-off-by: Tudor Ambarus
---
arch/arm/mach-at91/Kconfig | 4 +
From: Tudor Ambarus
sama5's SFR has at offset 0x04 the DDR Configuration Register,
while sam9x60's SFR contains the EBI Chip Select Register. Add
a union to reconcile both boards.
Signed-off-by: Tudor Ambarus
---
arch/arm/mach-at91/include/mach/at91_sfr.h | 48 --
From: Sandeep Sheriker Mallikarjun
add sam9x60ek_mmc_defconfig and for now only supports booting from
sdcard.
Signed-off-by: Sandeep Sheriker Mallikarjun
Signed-off-by: Nicolas Ferre
[nicolas.fe...@microchip.com: split patch, add Ethernet controller,
phy and tools]
From: Sandeep Sheriker Mallikarjun
Add new compatibility string for matching sam9x60 product.
Signed-off-by: Sandeep Sheriker Mallikarjun
---
drivers/mmc/atmel_sdhci.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mmc/atmel_sdhci.c b/drivers/mmc/atmel_sdhci.c
index
From: Sandeep Sheriker Mallikarjun
Add new board SAM9X60-EK using the ARM926 SAM9X60 SoC.
Signed-off-by: Sandeep Sheriker Mallikarjun
[tudor.amba...@microchip.com:
- fix number of DRAM banks:
One DDR2-SDRAM (W972GG6KB 2 Gbit = 16 Mbit x 16 x 8 banks]
- drop SPL related macros
- drop memtest
From: Tudor Ambarus
Add support for sam9x60 SOC, sam9x60ek board, dts, NAND and QSPI.
Add defconfigs for MMC, NAND and QSPI.
v3:
- Enable MII utility commands and phy in qspi & nand defconfigs
- Add sam9x60-sdhci and sam9x60-macb compatibility strings
- nandflash_defconfig: Fix rootfs partition
Hi Bin,
On Thu, Sep 26, 2019 at 7:26 AM Bin Meng wrote:
>
> Hi Sagar,
>
> On Thu, Sep 26, 2019 at 1:54 AM Sagar Kadam wrote:
> >
> > Hi Bin,
> >
> > On Wed, Sep 18, 2019 at 1:23 PM Bin Meng wrote:
> > >
> > > Hi Sagar,
> > >
> > > On Tue, Sep 10, 2019 at 11:44 PM Sagar Shrikant Kadam
> > >
Hi Sagar,
On Thu, Sep 26, 2019 at 1:54 AM Sagar Kadam wrote:
>
> Hi Bin,
>
> On Wed, Sep 18, 2019 at 1:23 PM Bin Meng wrote:
> >
> > Hi Sagar,
> >
> > On Tue, Sep 10, 2019 at 11:44 PM Sagar Shrikant Kadam
> > wrote:
> > >
> > > U-Boot currently is missing GPIO support for FU540-C000 SoC which
Hi Bin,
On Wed, Sep 18, 2019 at 3:09 PM Bin Meng wrote:
>
> Hi Sagar,
>
> On Tue, Sep 10, 2019 at 11:44 PM Sagar Shrikant Kadam
> wrote:
> >
> > This patch adds a DM based driver model for gpio controller present in
> > FU540-C000 SoC on HiFive Unleashed A00 board. This SoC has one GPIO
> >
Hi Bin,
On Wed, Sep 18, 2019 at 1:23 PM Bin Meng wrote:
>
> Hi Sagar,
>
> On Tue, Sep 10, 2019 at 11:44 PM Sagar Shrikant Kadam
> wrote:
> >
> > U-Boot currently is missing GPIO support for FU540-C000 SoC which is
> > mounted on HiFive Unleashed A00 board. This patch is intended to add DM
> >
68/
Background: I think you need to change the config to CONFIG_NR_DRAM_BANKS=2
Happy to hear back from you.
Regards,
Matthias
>
> -Thanks
>
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> https://lists.denx.de/listinfo/u
hi
I have added the IDE support and I am able to operate with pATA
harddrives, but microdrives are not recognized ...
any help to what and where I have to investigate?
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
With top of the tree(tot) uboot, and tot firmware, uboot command bdinfo
shows the dram bank size as 0x3b40 which is <1G, but the
rpi4 board has 4G of ram.
However with kernel8.img in the firmware, linux kernel shows in
/proc/meminfo
cat /proc/meminfo
MemTotal:3999784 kB
MemFree:
Hi Sagar,
On Tue, Sep 10, 2019 at 11:44 PM Sagar Shrikant Kadam
wrote:
>
> This patch adds a DM based driver model for gpio controller present in
> FU540-C000 SoC on HiFive Unleashed A00 board. This SoC has one GPIO
> bank and 16 GPIO lines in total, out of which GPIO0 to GPIO9 and
> GPIO15 are
On Tue, Sep 10, 2019 at 11:44 PM Sagar Shrikant Kadam
wrote:
>
> Enable the DM based GPIO driver for FU540-C000 SoC.
>
> Signed-off-by: Sagar Shrikant Kadam
> ---
> board/sifive/fu540/Kconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Bin Meng
Tested-by: Bin Meng
Hi Sagar,
On Tue, Sep 10, 2019 at 11:44 PM Sagar Shrikant Kadam
wrote:
>
> U-Boot currently is missing GPIO support for FU540-C000 SoC which is
> mounted on HiFive Unleashed A00 board. This patch is intended to add DM
> based GPIO controller driver in order to access GPIO pins within the SoC
>
Hi Carlo,
On 16.09.19 02:06, Carlo Pisani wrote:
hi
I am trying to use the board "dht-walnut", and I get this on the
attempt to tftpboot
PHY speed read failed, assuming 10bT
PHY duplex read failed, assuming half-duplex
Using ppc_4xx_eth0 device
The ppc405GP board is connected to a router
On Sat, Sep 14, 2019 at 01:44:28PM +0530, Jagan Teki wrote:
> On Sat, Sep 14, 2019 at 1:38 PM Marek Vasut wrote:
> >
> > On 9/14/19 9:58 AM, Heinrich Schuchardt wrote:
> > > For many sub-systems we already require the driver model to be used. Yet
> > > there is still a handful of boards that do
hi
I am trying to use the board "dht-walnut", and I get this on the
attempt to tftpboot
PHY speed read failed, assuming 10bT
PHY duplex read failed, assuming half-duplex
Using ppc_4xx_eth0 device
The ppc405GP board is connected to a router whose ethernet port is
rated 100bT/full-duplex, but on
Hi, can you help me to solve problem with u-boot. I have tegra30 board like
(180-61852-1606-c00) it’s looks like cardhu one. But when I build(cardhu board)
u-boot and run it, I have error when I want to select emmc card.
Error:
Card did not respond to voltage select! ,
mmc_init: -95,
On Sat, Sep 14, 2019 at 1:38 PM Marek Vasut wrote:
>
> On 9/14/19 9:58 AM, Heinrich Schuchardt wrote:
> > For many sub-systems we already require the driver model to be used. Yet
> > there is still a handful of boards that do not have CONFIG_DM enabled.
> >
> > We should make CONFIG_DM compulsory
On 9/14/19 9:58 AM, Heinrich Schuchardt wrote:
> For many sub-systems we already require the driver model to be used. Yet
> there is still a handful of boards that do not have CONFIG_DM enabled.
>
> We should make CONFIG_DM compulsory with release v2020.01
>
> Signed-off-by: Heinrich Schuchardt
On 09/09/2019 11:35, Sachin Mehrotra wrote:
> Dear Concern,
>
> I am working for u-boot for rpi4, may I know do we have updated working
> version for Raspberry Pi 4.
> I was testing the version https://gitlab.denx.de/u-boot/u-boot with
> rpi4<https://gitlab.denx.de/u-boot
+Moving to normal mailing list as the -dm one isn't really used.
+Marek Vasut do you think we could delete it or disable subscriptions?
On Thu, 12 Sep 2019 at 07:22, Matt Sykes wrote:
>
> I am new to this and having a play to see how it all works, and have a board
> up and running (UBoot,
Enable the DM based GPIO driver for FU540-C000 SoC.
Signed-off-by: Sagar Shrikant Kadam
---
board/sifive/fu540/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/board/sifive/fu540/Kconfig b/board/sifive/fu540/Kconfig
index 5d65080..5ca2147 100644
--- a/board/sifive/fu540/Kconfig
This patch adds a DM based driver model for gpio controller present in
FU540-C000 SoC on HiFive Unleashed A00 board. This SoC has one GPIO
bank and 16 GPIO lines in total, out of which GPIO0 to GPIO9 and
GPIO15 are routed to the J1 header on the board.
This implementation is ported from linux
U-Boot currently is missing GPIO support for FU540-C000 SoC which is
mounted on HiFive Unleashed A00 board. This patch is intended to add DM
based GPIO controller driver in order to access GPIO pins within the SoC
using GPIO command in U-Boot. More details on the GPIO controller within
the SoC can
On Tue, Sep 10, 2019 at 7:54 AM Tom Rini wrote:
>
> On Tue, Sep 10, 2019 at 10:29:04AM +0200, Wolfgang Denk wrote:
> > Dear Tom,
> >
> > In message <20190909210130.GU6927@bill-the-cat> you wrote:
> > >
> > > On Wed, Sep 04, 2019 at 01:30:02PM -0500, Joe Hershberger wrote:
> > ...
> > > > I would
On Tue, Sep 10, 2019 at 10:29:04AM +0200, Wolfgang Denk wrote:
> Dear Tom,
>
> In message <20190909210130.GU6927@bill-the-cat> you wrote:
> >
> > On Wed, Sep 04, 2019 at 01:30:02PM -0500, Joe Hershberger wrote:
> ...
> > > I would gladly volunteer for this role if Wolfgang would co-maintain
> >
Dear Tom,
In message <20190909210130.GU6927@bill-the-cat> you wrote:
>
> On Wed, Sep 04, 2019 at 01:30:02PM -0500, Joe Hershberger wrote:
...
> > I would gladly volunteer for this role if Wolfgang would co-maintain
> > to keep me in line. He seems to have an uncanny ability to keep all
> > the
On Wed, Sep 04, 2019 at 01:30:02PM -0500, Joe Hershberger wrote:
> On Wed, Sep 4, 2019 at 1:01 PM Tom Rini wrote:
> >
> > On Tue, Sep 03, 2019 at 10:04:42AM +0200, Wolfgang Denk wrote:
> > > Dear Tom,
> > >
> > > In message Heiko Schocher
> > > wrote:
> > > >
> > > > I am just testing U-Boot
Dear Concern,
I am working for u-boot for rpi4, may I know do we have updated working version
for Raspberry Pi 4.
I was testing the version https://gitlab.denx.de/u-boot/u-boot with
rpi4<https://gitlab.denx.de/u-boot/u-boot%20with%20rpi4> but getting error in
file arch/arm/cpu/armv8/cp
On Tue, Sep 03, 2019 at 06:03:40PM -0500, Joe Hershberger wrote:
> On Tue, Sep 3, 2019 at 3:05 AM Wolfgang Denk wrote:
> >
> > Dear Tom,
> >
> > In message Heiko Schocher
> > wrote:
> > >
> > > I am just testing U-Boot Environment flags and they do not work anymore
> > > with
> > > current
ething like qemu-x86 that is less
> of a special case build than sandbox is? In fact, since I know we
> have the QEMU targets in for "real" uses and not just testing,
> and while I worry about adding in more complex logic, we might want to
> rework the "build and run test.py in QEMU" parts of CI to first make
> use of scripts/kconfig/merge_config.sh to turn ON a whole bunch of
> testing related options.
> --
> Tom
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> https://lists.denx.de/listinfo/u-boot
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
On Tue, Sep 03, 2019 at 10:04:42AM +0200, Wolfgang Denk wrote:
> Dear Tom,
>
> In message Heiko Schocher
> wrote:
> >
> > I am just testing U-Boot Environment flags and they do not work anymore with
> > current mainline U-Boot ...
> ...
> > reason is your commit:
> >
> > commit
Hello Joe,
Am 04.09.2019 um 01:03 schrieb Joe Hershberger:
On Tue, Sep 3, 2019 at 3:05 AM Wolfgang Denk wrote:
Dear Tom,
In message Heiko Schocher wrote:
I am just testing U-Boot Environment flags and they do not work anymore with
current mainline U-Boot ...
...
reason is your commit:
1 - 100 of 14785 matches
Mail list logo
