Hi,
-Original Message-
From: Marek Vasut [mailto:ma...@denx.de]
Sent: Tuesday, May 21, 2019 6:14 PM
To: Siva Durga Prasad Paladugu ; Jean-Jacques Hiblot
; lu...@denx.de
Cc: Marcel Ziswiler ; u-boot@lists.denx.de; Miquel
Raynal ; Stefan Roese ; Tom Rini
; Ryder Lee ; Heinrich
Hi Tom, Peng, Fabio,
> On Wed, May 22, 2019 at 01:38:44AM +, Peng Fan wrote:
> > Hi Fabio,
> >
> > > Subject: Re: Cannot boot mx6qsabred with 2019.07-rc2
> > >
> > > Hi Peng,
> > >
> > > On Thu, May 16, 2019 at 11:29 PM Peng Fan
> > > wrote:
> > > > You could enable DEBUG in SPL, and
Wolfgang,
Thank you for your comments.
On Fri, May 17, 2019 at 10:47:56AM +0200, Wolfgang Denk wrote:
> Dear Akashi Takahiro,
>
> In message <20190517001206.gx11...@linaro.org> you wrote:
> >
> > > Who: usually the responsible custodians
> >
> > "Custodians" don't always mean sub-system
As VIDEO_IMX_HDP_LOAD is supported on LS1028A, this patch adds
ARCH_LS1028A dependency for VIDEO_IMX_HDP_LOAD.
Signed-off-by: Alison Wang
---
drivers/video/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
index
Certain drivers want to attach private data corresponding to each
power domain. This data might be specific be to the drvier. So add
a priv entry into the power_domain structure.
Signed-off-by: Lokesh Vutla
---
include/power-domain.h | 15 ++-
1 file changed, 2 insertions(+), 13
TISCI protocol supports for enabling the device either with exclusive
permissions for the requesting host or with sharing across the hosts.
There are certain devices which are exclusive to Linux context and
there are certain devices that are shared across different host contexts.
So add support
From: Andreas Dannenberg
Add and expose a new processor shutdown API that wraps the two TISCI
messages involved in initiating a core shutdown. The API will first
queue a message to have the DMSC wait for a certain processor boot
status to happen followed by a message to trigger the actual
TISCI protocol supports for enabling the device either with exclusive
permissions for the requesting host or with sharing across the hosts.
There are certain devices which are exclusive to Linux context and
there are certain devices that are shared across different host contexts.
So add support
Update the power-domain-cells to 2 and add the permissions
to each node. Mark all the nodes accessed by r5 as shared
in r5 dts.
Signed-off-by: Lokesh Vutla
---
arch/arm/dts/k3-am65-wakeup.dtsi | 2 +-
arch/arm/dts/k3-am65.dtsi| 1 +
From: Andreas Dannenberg
Rather than simply parking the R5 core in WFE after starting up ATF
on A53 instead use SYSFW API to properly shut down the R5 CPU cores
as well as associated timer resources that were pre-allocated. This
allows software further downstream to properly and gracefully bring
Sysfw provides an option for requesting exclusive access for a
device using the flags MSG_FLAG_DEVICE_EXCLUSIVE. If this flag is
not used, the device is meant to be shared across hosts. Once a device
is requested from a host with this flag set, any request to this
device from a different host will
Sysfw provides an option for requesting exclusive access for a
device using the flags MSG_FLAG_DEVICE_EXCLUSIVE. If this flag is
not used, the device is meant to be shared across hosts. Once a device
is requested from a host with this flag set, any request to this
device from a different host will
On 21/05/19 11:27 PM, Lokesh Vutla wrote:
> 'rproc init' does the probe and initialization of all the available
> remoteproc devices in the system. This doesn't allow the flexibility
> to initialize the remote cores needed as per use case. In order
> to provide flexibility, update 'rproc init'
TISCI protocol supports for enabling the device either with exclusive
permissions for the requesting host or with sharing across the hosts.
There are certain devices which are exclusive to Linux context and
there are certain devices that are shared across different host contexts.
So add support
From: Andreas Dannenberg
Rather than simply parking the R5 core in WFE after starting up ATF
on A53 instead use SYSFW API to properly shut down the R5 CPU cores
as well as associated timer resources that were pre-allocated. This
allows software further downstream to properly and gracefully bring
'rproc init' does the probe and initialization of all the available
remoteproc devices in the system. This doesn't allow the flexibility
to initialize the remote cores needed as per use case. In order
to provide flexibility, update 'rproc init' command to accept one
more parameter with rproc id
Update the power-domain-cells to 2 and add the permissions
to each node. Mark all the nodes accessed by r5 as shared
in r5 dts.
Signed-off-by: Lokesh Vutla
---
arch/arm/dts/k3-am65-wakeup.dtsi | 2 +-
arch/arm/dts/k3-am65.dtsi| 1 +
Certain drivers want to attach private data corresponding to each
power domain. This data might be specific be to the drvier. So add
a priv entry into the power_domain structure.
Signed-off-by: Lokesh Vutla
---
include/power-domain.h | 15 ++-
1 file changed, 2 insertions(+), 13
TISCI protocol supports for enabling the device either with exclusive
permissions for the requesting host or with sharing across the hosts.
There are certain devices which are exclusive to Linux context and
there are certain devices that are shared across different host contexts.
So add support
From: Andreas Dannenberg
Add and expose a new processor shutdown API that wraps the two TISCI
messages involved in initiating a core shutdown. The API will first
queue a message to have the DMSC wait for a certain processor boot
status to happen followed by a message to trigger the actual
Sysfw provides an option for requesting exclusive access for a
device using the flags MSG_FLAG_DEVICE_EXCLUSIVE. If this flag is
not used, the device is meant to be shared across hosts. Once a device
is requested from a host with this flag set, any request to this
device from a different host will
Sysfw provides an option for requesting exclusive access for a
device using the flags MSG_FLAG_DEVICE_EXCLUSIVE. If this flag is
not used, the device is meant to be shared across hosts. Once a device
is requested from a host with this flag set, any request to this
device from a different host will
Hi Lukasz,
> -Original Message-
> From: Lukasz Majewski [mailto:lu...@denx.de]
> Sent: 2019年5月21日 16:33
> To: Peng Fan
> Cc: Marek Vasut ; Marek Vasut ;
> Simon Glass ; u-boot@lists.denx.de; Tien Fong Chee
> ; York Sun ; dl-uboot-imx
>
> Subject: Re: [U-Boot] [PATCH 4/6] spl: mmc:
Alex,
It seems to me that the current efi_runtime_detach() has
two meanings:
* changes relating to the transition to virtual address mode
* changes relating to exiting boot services
In the current implementation, efi_runtime_detach() is
called from efi_set_virtual_address_map() as those two
Simon,
> Subject: RE: [PATCH 4/6] spl: mmc: support loading i.MX container format file
>
> Hi Simon,
>
> > Subject: Re: [PATCH 4/6] spl: mmc: support loading i.MX container
> > format file
> >
> > Hi Peng,
> >
> > On Tue, 7 May 2019 at 06:52, Peng Fan wrote:
> > >
> > > i.MX8 only support AHAB
Change sata node status to enable sata.
Signed-off-by: Peng Ma
---
arch/arm/dts/fsl-lx2160a-qds.dts | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/arch/arm/dts/fsl-lx2160a-qds.dts b/arch/arm/dts/fsl-lx2160a-qds.dts
index 6192156..77cf2ce 100644
---
On Wed, May 22, 2019 at 01:38:44AM +, Peng Fan wrote:
> Hi Fabio,
>
> > Subject: Re: Cannot boot mx6qsabred with 2019.07-rc2
> >
> > Hi Peng,
> >
> > On Thu, May 16, 2019 at 11:29 PM Peng Fan wrote:
> >
> > > You could enable DEBUG in SPL, and disable SPL_SDP because of size will
> >
Hi Simon:
Simon Glass 于2019年5月22日周三 上午8:28写道：
> Hi Andy,
>
> On Tue, 21 May 2019 at 00:51, Andy Yan wrote:
> >
> > Hi Simon:
> >
> > On 2019/5/20 下午11:35, Simon Glass wrote:
> > > Hi Andy,
> > >
> > > On Mon, 20 May 2019 at 00:34, Andy Yan
> wrote:
> > >> Hi Simon:
> > >>
> > >> On 2019/5/19
Hi Andre:
Andre Przywara 于2019年5月20日周一 下午11:59写道：
> On Mon, 20 May 2019 14:34:01 +0800
> Andy Yan wrote:
>
> Hi,
>
> > On 2019/5/19 上午12:26, Simon Glass wrote:
> > > Hi Andy,
> > >
> > > Instead of this could you:
> > >
> > > - move ATF?
> >
> > All rockchip based arm64 ATF run from the start
Hi Fabio,
> Subject: Re: Cannot boot mx6qsabred with 2019.07-rc2
>
> Hi Peng,
>
> On Thu, May 16, 2019 at 11:29 PM Peng Fan wrote:
>
> > You could enable DEBUG in SPL, and disable SPL_SDP because of size will
> exceeds.
> > Then see what happends.
> > I have no idea, then. My board is REV C4,
Hi Andreas,
On Tue, 21 May 2019 at 15:01, Andreas Dannenberg wrote:
>
> Hi Simon (Glass),
>
> On Sat, May 18, 2019 at 10:08:19AM -0600, Simon Glass wrote:
> > Hi Andreas,
> >
> > On Mon, 6 May 2019 at 22:49, Andreas Dannenberg wrote:
> > >
> > > Hi Simon,
> > >
> > > On Mon, May 06, 2019 at
Hi Eugeniu,
On Fri, 17 May 2019 at 08:46, Eugeniu Rosca wrote:
>
> 'Bootloader Control Block' (BCB) is a well established term/acronym in
> the Android namespace which refers to a location in a dedicated raw
> (i.e. FS-unaware) flash (e.g. eMMC) partition, usually called "misc",
> which is used
On Tue, 21 May 2019 at 11:19, Patrick Delaunay wrote:
>
> Add a test to check the management of the U-boot relocation properties
> for device tree SPL generation (fdtgrep result) and platdata:
> - 'dm-pre-proper' and 'dm-tpl' not included in SPL
> - 'dm-pre-reloc' and 'dm-spl' included in SPL
>
>
Hi Patrick,
On Tue, 21 May 2019 at 10:07, Patrick DELAUNAY wrote:
>
> Hi Simon,
>
> I will reply for the serie
>
> > Hi Patrick,
> >
> > On Mon, 20 May 2019 at 07:00, Patrick Delaunay
> > wrote:
> > >
> > >
> > > Hi,
> > >
> > > I create this v2 serie with:
> > >
> > > 1/ documentation update
Hi Lukasz,
On Tue, 21 May 2019 at 08:48, Lukasz Majewski wrote:
>
> Hi Simon,
>
> > Hi Lukasz,
> >
> > On Sun, 19 May 2019 at 15:03, Lukasz Majewski wrote:
> > >
> > > Hi Simon,
> > >
> > > > Hi Lukasz,
> > > >
> > > > On Sat, 18 May 2019 at 15:28, Lukasz Majewski
> > > > wrote:
> > > > >
> >
Hi Andy,
On Tue, 21 May 2019 at 00:51, Andy Yan wrote:
>
> Hi Simon:
>
> On 2019/5/20 下午11:35, Simon Glass wrote:
> > Hi Andy,
> >
> > On Mon, 20 May 2019 at 00:34, Andy Yan wrote:
> >> Hi Simon:
> >>
> >> On 2019/5/19 上午12:26, Simon Glass wrote:
> >>> Hi Andy,
> >>>
> >>> Instead of this could
On Tue, 2019-05-21 at 20:39 +0530, Sekhar Nori wrote:
> U-Boot README recommends initializing SDRAM in board_init_f(). DA850
> was doing it as part of board_init_r() (through call to
> spl_board_init()
> which calls arch_cpu_init() which calls da850_ddr_setup())
>
> This worked fine till commit
On Tue, 2019-05-21 at 20:39 +0530, Sekhar Nori wrote:
> commit 21af33ed0319 ("ARM: davinci: omapl138_lcdk: Enable DM_MMC")
> wanted to enable DM_MMC only for U-Boot and not for SPL.
>
> But CONFIG_DM_MMC is defined for SPL build too. Because of this
> MMC device was not getting registered for SPL
Hi Sekhar
On Tue, 2019-05-21 at 20:39 +0530, Sekhar Nori wrote:
> Hi,
>
> Here is a set of patches that fixes MMC/SD boot breakage introduced
> after 2018.09 release.
>
> This was tested with MMC/SD boot on OMAP-L138 LCDK. I still need to
> do SPI and NAND boot on this board.
>
I have tested
On 5/21/19 12:32 PM, Patrick DELAUNAY wrote:
Hi Stephen,
For information after the remarksSimon's remark,
I simplify the test, so this part is no more needed
See http://patchwork.ozlabs.org/patch/1102938/
But I will answer with my status and my tests done on the python code.
On 5/20/19
Hi Simon (Glass),
On Sat, May 18, 2019 at 10:08:19AM -0600, Simon Glass wrote:
> Hi Andreas,
>
> On Mon, 6 May 2019 at 22:49, Andreas Dannenberg wrote:
> >
> > Hi Simon,
> >
> > On Mon, May 06, 2019 at 09:51:56PM -0600, Simon Glass wrote:
> > > Hi Andreas,
> > >
> > > On Fri, 3 May 2019 at
Hi Eugeniu,
On Tue, 21 May 2019 at 11:32, Eugeniu Rosca wrote:
>
> Hi Simon,
>
> On Tue, May 21, 2019 at 10:43:04AM -0600, Simon Glass wrote:
> > On Mon, 20 May 2019 at 01:23, Eugeniu Rosca wrote:
> [..]
> > > I can identify two Android-dedicated README files, but none of them
> > > seems to be
On 5/21/19 10:03 PM, Simon Goldschmidt wrote:
> commit 1b898ffc040b ("gpio: dwapb_gpio: convert to livetree") introduced
> a bug in that dev->node of the gpio chip was accidentally set to the
> of_node of its bank subnode.
>
> What it meant to do was assign subdev->node, not dev->node.
>
> While
On 5/21/19 10:10 PM, Tom Rini wrote:
> On Tue, May 21, 2019 at 10:01:42PM +0200, Marek Vasut wrote:
>> On 5/21/19 9:59 PM, Tom Rini wrote:
>>> On Tue, May 21, 2019 at 09:54:33PM +0200, Marek Vasut wrote:
On 5/21/19 9:53 PM, Tom Rini wrote:
> On Tue, May 21, 2019 at 09:32:29PM +0200, Marek
On Tue, May 21, 2019 at 10:01:42PM +0200, Marek Vasut wrote:
> On 5/21/19 9:59 PM, Tom Rini wrote:
> > On Tue, May 21, 2019 at 09:54:33PM +0200, Marek Vasut wrote:
> >> On 5/21/19 9:53 PM, Tom Rini wrote:
> >>> On Tue, May 21, 2019 at 09:32:29PM +0200, Marek Vasut wrote:
> On 5/21/19 6:56 PM,
commit 1b898ffc040b ("gpio: dwapb_gpio: convert to livetree") introduced
a bug in that dev->node of the gpio chip was accidentally set to the
of_node of its bank subnode.
What it meant to do was assign subdev->node, not dev->node.
While this doesn't affect too many use cases, iterating over the
On 5/21/19 9:59 PM, Tom Rini wrote:
> On Tue, May 21, 2019 at 09:54:33PM +0200, Marek Vasut wrote:
>> On 5/21/19 9:53 PM, Tom Rini wrote:
>>> On Tue, May 21, 2019 at 09:32:29PM +0200, Marek Vasut wrote:
On 5/21/19 6:56 PM, Jagan Teki wrote:
> On Tue, May 21, 2019 at 10:14 PM Simon Glass
On Tue, May 21, 2019 at 09:54:33PM +0200, Marek Vasut wrote:
> On 5/21/19 9:53 PM, Tom Rini wrote:
> > On Tue, May 21, 2019 at 09:32:29PM +0200, Marek Vasut wrote:
> >> On 5/21/19 6:56 PM, Jagan Teki wrote:
> >>> On Tue, May 21, 2019 at 10:14 PM Simon Glass wrote:
>
> Hi,
>
>
On 5/21/19 9:53 PM, Tom Rini wrote:
> On Tue, May 21, 2019 at 09:32:29PM +0200, Marek Vasut wrote:
>> On 5/21/19 6:56 PM, Jagan Teki wrote:
>>> On Tue, May 21, 2019 at 10:14 PM Simon Glass wrote:
Hi,
(moved from thread "U-Boot PXA support")
We have of-platdata, which
On Tue, May 21, 2019 at 09:32:29PM +0200, Marek Vasut wrote:
> On 5/21/19 6:56 PM, Jagan Teki wrote:
> > On Tue, May 21, 2019 at 10:14 PM Simon Glass wrote:
> >>
> >> Hi,
> >>
> >> (moved from thread "U-Boot PXA support")
> >>
> >> We have of-platdata, which produces C data from the DT, for
On 5/21/19 6:56 PM, Jagan Teki wrote:
> On Tue, May 21, 2019 at 10:14 PM Simon Glass wrote:
>>
>> Hi,
>>
>> (moved from thread "U-Boot PXA support")
>>
>> We have of-platdata, which produces C data from the DT, for linking
>> into U-Boot. It saves libfdt and DT space. But we still have the DM
>>
On 5/21/19 6:43 PM, Simon Glass wrote:
> Hi,
>
> (moved from thread "U-Boot PXA support")
>
> We have of-platdata, which produces C data from the DT, for linking
> into U-Boot. It saves libfdt and DT space. But we still have the DM
> overhead.
>
> We have binman which can insert values into the
Hi Tom,
On Fri, May 17, 2019 at 07:24:48AM -0400, Tom Rini wrote:
> On Thu, May 16, 2019 at 03:54:43PM -0500, Andreas Dannenberg wrote:
>
> > This series provides an alternative solution to the previously posted
> > series titled "System Firmware Loader for TI K3 family SoCs" [1] using
> > the
Hi TF,
On Tue, May 21, 2019 at 05:40:19AM +, Chee, Tien Fong wrote:
> > + fs_loader0: fs_loader@0 {
> > + u-boot,dm-pre-reloc;
> > + compatible = "u-boot,fs-loader";
>
> Why not using phandlepart = < 1>, this would help to avoid mmc init
> duplication in a few places
Hi TF,
On Tue, May 21, 2019 at 05:21:15AM +, Chee, Tien Fong wrote:
> On Thu, 2019-05-16 at 15:54 -0500, Andreas Dannenberg wrote:
> > + if (mmc_dev < 0) {
> > + pr_err("%s: Getting MMC device index failed (%d)\n",
> > __func__,
> > + mmc_dev);
> > +
Hi TF,
first, thanks for taking time to continue having the discussion around
this patch series.
On Tue, May 21, 2019 at 05:40:59AM +, Chee, Tien Fong wrote:
> On Thu, 2019-05-16 at 15:54 -0500, Andreas Dannenberg wrote:
> > To give us more flexibility using the FS loader eliminate the need
Hi Stephen,
For information after the remarksSimon's remark,
I simplify the test, so this part is no more needed
See http://patchwork.ozlabs.org/patch/1102938/
But I will answer with my status and my tests done on the python code.
>
> On 5/20/19 7:00 AM, Patrick Delaunay wrote:
> > Only used
Hi Simon,
On Tue, May 21, 2019 at 10:43:04AM -0600, Simon Glass wrote:
> On Mon, 20 May 2019 at 01:23, Eugeniu Rosca wrote:
[..]
> > I can identify two Android-dedicated README files, but none of them
> > seems to be suitable for the new command:
> > - doc/README.android-fastboot
> > -
Add documentation for the pre-reloc property in SPL and TPL device-tree:
- u-boot,dm-pre-proper
- u-boot,dm-pre-reloc
- u-boot,dm-spl
- u-boot,dm-tpl
Signed-off-by: Patrick Delaunay
Reviewed-by: Simon Glass
---
Changes in v3:
- rebase on u-boot-dm/sandbox-working
Changes in v2:
- rebase on
Hi,
I create this serie with:
1/ documentation update for previous patch
[U-Boot,v2] dm: remove pre reloc properties in SPL and TPL device tree
http://patchwork.ozlabs.org/patch/1081155/
PS: Code is already merged in commit commit c7a88dae997f ("dm: remove
pre reloc properties
Add a test to check the management of the U-boot relocation properties
for device tree SPL generation (fdtgrep result) and platdata:
- 'dm-pre-proper' and 'dm-tpl' not included in SPL
- 'dm-pre-reloc' and 'dm-spl' included in SPL
Signed-off-by: Patrick Delaunay
---
Changes in v3:
- simplify
This add missing parts for previous commit 06f94461a9f4
("fdt: Allow indicating a node is for U-Boot proper only")
At present it is not possible to specify that a node should be used before
relocation (in U-Boot proper) without it also ending up in SPL and TPL
device trees. Add a new
On Tue, May 21, 2019 at 10:14 PM Simon Glass wrote:
>
> Hi,
>
> (moved from thread "U-Boot PXA support")
>
> We have of-platdata, which produces C data from the DT, for linking
> into U-Boot. It saves libfdt and DT space. But we still have the DM
> overhead.
>
> We have binman which can insert
Hi Eugeniu,
On Tue, May 21, 2019 at 2:20 PM Eugeniu Rosca wrote:
>
> Hi Sam,
>
> On Mon, May 20, 2019 at 06:16:38PM +0300, Sam Protsenko wrote:
> > Hi Eugeniu,
> >
> > On Mon, May 20, 2019 at 10:23 AM Eugeniu Rosca
> > wrote:
> [..]
> > > Igor, Sam, what's your view on the above? Would you
Hi,
(moved from thread "U-Boot PXA support")
We have of-platdata, which produces C data from the DT, for linking
into U-Boot. It saves libfdt and DT space. But we still have the DM
overhead.
We have binman which can insert values into the binary after
link-time. This is barely used at present,
On Mon, 20 May 2019 at 23:50, Heinrich Schuchardt wrote:
>
> Compiling the display command leads to an error
>
> undefined reference to `display_set'
>
> No implementation of display_set() exists in U-Boot.
>
> Eliminate the `display` command as well as the accompanying files.
>
>
Hi Eugeniu,
On Mon, 20 May 2019 at 01:23, Eugeniu Rosca wrote:
>
> Hi Simon
> cc: Sam, Igor, feel free to correct/augment anything of below
>
> On Sat, May 18, 2019 at 10:33:02AM -0600, Simon Glass wrote:
> > Hi Eugeniu,
> >
> > On Fri, 17 May 2019 at 08:46, Eugeniu Rosca wrote:
> > >
> > >
Hi,
On Tue, 21 May 2019 at 08:50, Tom Rini wrote:
>
> On Tue, May 21, 2019 at 04:34:19PM +0200, Marek Vasut wrote:
> > On 5/21/19 4:29 PM, Marcel Ziswiler wrote:
> > > On Tue, 2019-05-21 at 14:49 +0200, Marek Vasut wrote:
> > >> On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
> > >>> On Tue,
Hi Thierry,
On Tue, 21 May 2019 at 04:21, Thierry Reding wrote:
>
> On Mon, May 20, 2019 at 02:51:08PM -0600, Simon Glass wrote:
> > Hi Thierry,
> >
> > On Mon, 20 May 2019 at 10:05, Thierry Reding
> > wrote:
> > >
> > > From: Thierry Reding
> > >
> > > Free the memory allocated to store the
Hi,
Is there a particular reason why fit_check_sign can only verify an
image using a DTB, rather than just the x509 public cert? Or is it just
that nobody has added the option so far? It would be useful to verify
images offline.
Thanks!
--
Kind regards,
Luca Boccassi
signature.asc
On 5/20/19 7:00 AM, Patrick Delaunay wrote:
Only used for spl compilation which include the device tree
(with platdata or embedded device tree).
For U-boot, test use config.dtb, by default :
"build_dir + '/arch/sandbox/dts/test.dtb'"
Signed-off-by: Patrick Delaunay
---
I need to force o_dt
Hi Simon,
I will reply for the serie
> Hi Patrick,
>
> On Mon, 20 May 2019 at 07:00, Patrick Delaunay
> wrote:
> >
> >
> > Hi,
> >
> > I create this v2 serie with:
> >
> > 1/ documentation update for previous patch
> >[U-Boot,v2] dm: remove pre reloc properties in SPL and TPL device tree
The recently-added ZYNQMP_SPL_PM_CFG_OBJ_FILE option allows SPL to load a
PMUFW configuration object from a binary blob. However the configuration
object is produced by Xilinx proprietary tools as a C source file and no
tool exists to easily convert it to a binary blob in an embedded Linux
build
Hi,
here's a minor improvement to 2/2 over v4. 1/1 is unchanged.
This patchset aims at solving a long-standing issue in the ZynqMP users
community: loading a PMU firmware configuration object when U-Boot SPL is
used.
The Platform Management Unit (PMU) needs a configuration object (cfg obj)
to
Optionally allow U-Boot to load a configuration object into the Power
Management Unit (PMU) firmware on Xilinx ZynqMP.
The configuration object is required by the PMU FW to enable most SoC
peripherals. So far the only way to boot using U-Boot SPL was to hard-code
the configuration object in the
On Tue, May 21, 2019 at 08:23:23AM +0200, Mario Six wrote:
> Hi Tom,
>
> The following changes since commit d494cdb97e18a30214d0414376d4eacdf82224fe:
>
> mpc83xx: Add gazerbeam board (2019-05-21 08:03:38 +0200)
>
> are available in the Git repository at:
>
>
On Tue, May 21, 2019 at 01:28:19AM +, Peng Fan wrote:
> Hi Tom,
>
> Please pull mmc-5-20 for v2019.07, this is to avoid break i.MX53 boot.
>
> Thanks,
> Peng
>
> The following changes since commit e14d9ca4919e5bc987fc628135104f2b2c91af90:
>
> Merge git://git.denx.de/u-boot-x86
On Mon, May 20, 2019 at 04:39:25PM +0200, Anatolij Gustschin wrote:
> Hi Tom,
>
> please pull video updates for v2019.07-rc3. cx9020 DM_VIDEO migration and
> splash source patches have been submitted to the list before merge window
> for v2019.07 closed, so I'm including them with some video
On Mon, May 20, 2019 at 10:45:06PM +0530, Jagan Teki wrote:
> Hi Tom,
>
> Please pull this PR.
>
> Summary:
> - H6 WDT reset fix (Clément)
> - H6 SPL_TEXT_BASE fixes (Clément, Jonas)
> - NPI-M1+ emac enablment (Emmanuel)
>
> The following changes since commit
Change comments for struct efi_open_protocol_info_item and
struct efi_handler to Sphinx format.
Signed-off-by: Heinrich Schuchardt
---
include/efi_loader.h | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/include/efi_loader.h b/include/efi_loader.h
index
Since commit 226cddbe32f0 ("efi_loader: check device path in
InstallMultipleProtocolInterfaces") iPXE fails to access the network.
LocateDevicePath() returns EFI_SUCCESS even if a shorter path is found as a
partial match. It returns the remaining path. So to be sure that we found a
complete match
Implement the SetTime() runtime service.
Extend the real time clock selftest to check setting the clock.
Signed-off-by: Heinrich Schuchardt
---
v2
fix reference to unknown parameter for CONFIG_DM_RTC=n
---
lib/efi_loader/efi_runtime.c| 73 -
On Tue, May 21, 2019 at 10:09 AM Sekhar Nori wrote:
>
> U-Boot README recommends initializing SDRAM in board_init_f(). DA850
> was doing it as part of board_init_r() (through call to spl_board_init()
> which calls arch_cpu_init() which calls da850_ddr_setup())
>
> This worked fine till commit
This commit enabled support for fitImage on mccmon6 when we
switch to DT/DTS (including falcon mode).
Signed-off-by: Lukasz Majewski
---
board/liebherr/mccmon6/spl.c | 7 ++
configs/mccmon6_nor_defconfig | 8 +-
configs/mccmon6_sd_defconfig | 6 -
include/configs/mccmon6.h
The mccmon6 has been used a "mixed" approach between SPL and
U-Boot proper sources.
This commit decoupes SPL and u-boot proper, which allows clear
distinction between those two code bases and facilitates
conversion to DM/DTS on this particular board.
Signed-off-by: Lukasz Majewski
---
After this change the SPL size has been reduced from 38K to 34K.
Signed-off-by: Lukasz Majewski
---
configs/mccmon6_nor_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/configs/mccmon6_nor_defconfig b/configs/mccmon6_nor_defconfig
index 62e957c0cf..ffb1025a13 100644
---
This commit adds falcon boot support (by also copying args necessary for
booting) to the SPL NOR memory driver.
After this change it is possible to use the falcon boot in the same way
as on NAND memories. The necessary configs (i.e. CONFIG_CMD_SPL_NOR_OFS)
are now defined in Kconfig.
This commit converts mccmon6's u-boot proper (in a single commit to avoid
build breaks) to use solely DM/DTS.
The DTS description of the mccmon6 has been ported from Linux kernel
(v4.20, SHA1: 8fe28cb58bcb235034b64cbbb7550a8a43fd88be)
Signed-off-by: Lukasz Majewski
---
arch/arm/dts/Makefile
This patch series converts mccmon6 to use Driver Model and Device
Tree in U-Boot proper.
As the SPL is size constrained (and most notably the device has a strict
boot time requirements) for this board (and uses falcon boot)
- its conversion to DM/DTB will be added with separate patch series.
The
commit 21af33ed0319 ("ARM: davinci: omapl138_lcdk: Enable DM_MMC")
wanted to enable DM_MMC only for U-Boot and not for SPL.
But CONFIG_DM_MMC is defined for SPL build too. Because of this
MMC device was not getting registered for SPL causing MMC/SD
boot breakage.
Instead use
U-Boot README recommends initializing SDRAM in board_init_f(). DA850
was doing it as part of board_init_r() (through call to spl_board_init()
which calls arch_cpu_init() which calls da850_ddr_setup())
This worked fine till commit 15b8c7505819 ("davinci:
da850evm/omapl138-lcdk: Move BSS to SDRAM
Hi,
Here is a set of patches that fixes MMC/SD boot breakage introduced
after 2018.09 release.
This was tested with MMC/SD boot on OMAP-L138 LCDK. I still need to
do SPI and NAND boot on this board.
Thanks,
Sekhar
Sekhar Nori (2):
ARM: davinci: omal138_lcdk: fix MMC boot breakage due to
Dear Tom
> -Original Message-
> From: Tom Rini
> Sent: Sunday, May 19, 2019 7:22 PM
> To: u-boot@lists.denx.de
> Cc: Albert ARIBAUD ; Andy Fleming
> ; Ashish Kumar ; Dirk Eibach
> ; Fabio Estevam ; Marek
> Vasut ; Naveen Burmi ; Oleksandr
> Zhadan and Michael Durrant ; Po Liu
> ; Poonam
On Tue, May 21, 2019 at 04:34:19PM +0200, Marek Vasut wrote:
> On 5/21/19 4:29 PM, Marcel Ziswiler wrote:
> > On Tue, 2019-05-21 at 14:49 +0200, Marek Vasut wrote:
> >> On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
> >>> On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
> It's slightly
Hi Simon,
> Hi Lukasz,
>
> On Sun, 19 May 2019 at 15:03, Lukasz Majewski wrote:
> >
> > Hi Simon,
> >
> > > Hi Lukasz,
> > >
> > > On Sat, 18 May 2019 at 15:28, Lukasz Majewski
> > > wrote:
> > > >
> > > > Hi Simon,
> > > >
> > > > This is not the newest patch set version of CCF (v3 vs.
Dear Ran
> -Original Message-
> From: Ran Wang
> Sent: Monday, May 13, 2019 8:49 AM
> To: Albert Aribaud ; Prabhakar Kushwaha
>
> Cc: York Sun ; u-boot@lists.denx.de; Ran Wang
>
> Subject: [RESEND][PATCH v2] armv8: Add workaround for USB erratum A-
> 050106
>
> USB3.0 Receiver needs
> -Original Message-
> From: Meenakshi Aggarwal
> Sent: Wednesday, May 15, 2019 4:40 PM
> To: u-boot@lists.denx.de; Prabhakar Kushwaha
>
> Cc: Meenakshi Aggarwal
> Subject: [PATCH v2] cover letter for drivers: net: mc: Report extra memory to
> linux
>
> changes in different versions:
> -Original Message-
> From: Meenakshi Aggarwal
> Sent: Wednesday, May 15, 2019 4:40 PM
> To: u-boot@lists.denx.de; Prabhakar Kushwaha
>
> Cc: Meenakshi Aggarwal
> Subject: [PATCH v2] drivers: net: mc: Report extra memory to Linux
>
V2 but no revision history
> MC firmware need to
On 5/21/19 4:29 PM, Marcel Ziswiler wrote:
> On Tue, 2019-05-21 at 14:49 +0200, Marek Vasut wrote:
>> On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
>>> On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
It's slightly off-topic but I wonder whether this ongoing
deprecation
of
On Tue, 2019-05-21 at 14:49 +0200, Marek Vasut wrote:
> On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
> > On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
> > > It's slightly off-topic but I wonder whether this ongoing
> > > deprecation
> > > of ARMv4 and ARMv5 (first in GCC, then in U-Boot)
1 - 100 of 158 matches
Mail list logo
