On Tue, Jun 20, 2017 at 09:02:29AM +0200, Emmanuel Vadot wrote:
> endian.h on FreeBSD system exist in sys/ subdirectory.
> FreeBSD already have a fls function defined in strings.h which is included
> in string.h if __BSD_VISIBLE is defined, as a check for this.
This broke the build of u-boot on Op
Hi Andy,
On Sun, Jul 16, 2017 at 9:37 PM, Andy Shevchenko
wrote:
> On Fri, 2017-07-07 at 12:51 +0800, Bin Meng wrote:
>> On Thu, Jul 6, 2017 at 1:33 AM, Andy Shevchenko
>> wrote:
>> > From: Felipe Balbi
>> >
>> > Add watchdog driver for Intel Tangier based platforms.
>
> Can we get it applied?
On Wed, Jul 19, 2017 at 12:44:48PM +1000, Bin Chen wrote:
> On 18 July 2017 at 22:32, Tom Rini wrote:
>
> > On Thu, Jul 13, 2017 at 05:33:08PM +1000, Bin Chen wrote:
> > > Hi Tom,
> > >
> > > Thanks for the review.
> > >
> > > On 13 July 2017 at 04:25, Tom Rini wrote:
> > >
> > > > On Tue, Jul 1
Andy,
On 14 July 2017 at 17:30, Andy Yan wrote:
> Hi:
>
> 2017-07-13 15:33 GMT+08:00 Bin Chen :
>
>> Hi Tom,
>>
>> Thanks for the review.
>>
>> On 13 July 2017 at 04:25, Tom Rini wrote:
>>
>> > On Tue, Jul 11, 2017 at 03:56:04PM +1000, Bin Chen wrote:
>> >
>> > > It's my understanding that we a
On 18 July 2017 at 22:32, Tom Rini wrote:
> On Thu, Jul 13, 2017 at 05:33:08PM +1000, Bin Chen wrote:
> > Hi Tom,
> >
> > Thanks for the review.
> >
> > On 13 July 2017 at 04:25, Tom Rini wrote:
> >
> > > On Tue, Jul 11, 2017 at 03:56:04PM +1000, Bin Chen wrote:
> > >
> > > > It's my understandi
On 07/18/2017 10:59 PM, Michal Simek wrote:
> Hi Simon,
>
> On 18.7.2017 16:50, Simon Glass wrote:
>> Hi Michal,
>>
>> On 18 July 2017 at 07:23, Michal Simek wrote:
>>> Hi Simon,
>>>
>>> On 18.7.2017 16:01, Simon Glass wrote:
Hi Michal,
On 13 July 2017 at 06:50, Michal Simek wrote
On Mon, Jul 17, 2017 at 04:08:27PM +0200, Arno Steffens wrote:
> After using a plain vanilla instead of a vendor kernel I do have
> problems with fw_setenv.
> Althoug fw_printenv still works fine, after usage of fw_setenv the
> environment is destroyed, CRC error.
>
> I checked a lot of things, c
On Fri, Jul 14, 2017 at 05:46:02PM +0200, Stefano Babic wrote:
> Hi Tom,
>
> please pull from u-boot-imx, thanks !
>
> All boards compile clean, there are still warning for 9 boards dur to
> fec_get_miibus. Patch was already sent by Lothar and will follow the
> normal way through Joe's tree. At
On Tue, Jul 18, 2017 at 06:05:05PM +0200, Marek Vasut wrote:
> I no longer have any of these boards, mark boards orphan.
>
> Signed-off-by: Marek Vasut
> Cc: Tom Rini
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: Digital signature
_
Am Dienstag, 18. Juli 2017, 22:36:06 CEST schrieb Philipp Tomsich:
> With the new common SDRAM code for Rockchip, we need to define
> CONFIG_SYS_SDRAM_BASE to correctly indicate the start of the physical
> address range mapping onto DRAM.
>
> Signed-off-by: Philipp Tomsich
> ---
>
> include/con
On he RK3368, we need to temporarily disable security on the DMA
engines during TPL and SPL to allow the MMC host to DMA into DRAM. To
do so, we need to reset the two DMA engines, which in turn requires
the DMA1_SRST_REQ and DMA2_SRST_REQ constants to refer to the
appropriate bits in the CRU.
As
To allow a TPL and SPL to run from different addresses/memories, we
need to split setup of the TPL and SPL stacks. To do so, we introduce
CONFIG_TPL_STACK (not listed in Kconfig) which can be used to override
the initial stack pointer for TPL.
To provide backward compatibility for existing boards
This splits the compilation of code modules for TPL and SPL for
OF_CONTROL (and related) features between TPL and SPL. The typical
use-case of this is a TPL stage that uses OF_PLATDATA at TPL and
provides full OF_CONTROL at SPL (e.g. on the RK3368).
Signed-off-by: Philipp Tomsich
---
lib/Makef
This adds the TPL support for the RK3368, including the u-boot-tpl.lds.
Signed-off-by: Philipp Tomsich
---
arch/arm/mach-rockchip/Makefile | 1 +
arch/arm/mach-rockchip/rk3368-board-tpl.c| 158 +++
arch/arm/mach-rockchip/rk3368/u-boot-tpl.lds | 13 +++
To add GMAC (Gigabit Ethernet) support (limited to RGMII only at this
point), we need support for additional pin-configuration. This commit
adds the pinctrl support for GMAC in RGMII mode:
* adds a PERIPH_ID_GMAC and the mapping from IRQ number to PERIPH_ID
* configures the RGMII pins
Signed-of
Introduce TPL_CLK to allow finer-grained selection of TPL features
for feature-rich (i.e. DM-based) TPL stages.
Signed-off-by: Philipp Tomsich
---
drivers/clk/Kconfig | 10 ++
drivers/clk/Makefile | 2 +-
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/drivers/clk/Kconf
To build TPL and SPL stages for the RK3368, we will also need to
enable the SPL_FRAMEWORK.
Signed-off-by: Philipp Tomsich
---
include/configs/rk3368_common.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/rk3368_common.h b/include/configs/rk3368_common.h
index 8ffc293..2a38
For the bringup of the RK3368, we need to support TPL and SPL running
from different addresses... which requires both stages to use a
distinct TEXT_BASE.
This commit adds support for having a separate LDSCRIPT for TPL (which
is expected to make use of the TPL_MAX_SIZE define) and for having a
the
The RK3368 has a somewhat temperamental BootROM (which I learned the
hard way) when it comes to reconfiguring the CPLL and GPLL (in fact,
experiments show that changing the GPLL broke things for me, while
changing the CPLL seems to be more benign). These should not be
modified by the SPL stage, if
This commit adds support for RK3368 SoC in mkimage.
Signed-off-by: Philipp Tomsich
---
tools/rkcommon.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/rkcommon.c b/tools/rkcommon.c
index 25b0340..04e8272 100644
--- a/tools/rkcommon.c
+++ b/tools/rkcommon.c
@@ -77,6 +77,7 @@ static st
As part of the DRAM initialisation process (running as part of the TPL
stage) on the RK3368, we need to set up the DRAM PLL.
This implements support for configuring the PLL to for 1200, 1332 or
1600 MHz (i.e. for DDR3-1200, DDR3-1333, DDR3-1600 operating modes).
Signed-off-by: Philipp Tomsich
--
The GMAC in the RK3368 once again is identical to the incarnation in
the RK3288 and the RK3399, except for where some of the configuration
and control registers are located in the GRF.
This adds the RK3368-specific logic necessary to reuse this driver.
Signed-off-by: Philipp Tomsich
---
driver
Adds SPL support for the RK3368 (assuming that our TPL stage has
initialised DRAM and set up the memory firewall).
This includes an implementation of board_debug_uart_init().
Signed-off-by: Philipp Tomsich
---
arch/arm/mach-rockchip/rk3368-board-spl.c | 91 +++
1 fi
For full SPL support, including DRAM initialisation, we need a few
nodes from the DTS: this commit adds the DMC (DRAM controller) node,
the service_msch (memory scheduler) node and marks GRF, PMUGRF and CRU
as 'u-boot,dm-pre-reloc'. In addition to this, we also include the
dt-binding for the DMC t
To enable the GMAC on the RK3368, we need to set up the clocking
appropriately to generate a tx_clk for the MAC.
This adds an implementation that implements the use of the <&ext_gmac>
clock (i.e. an external 125MHz clock for RGMII provided by the PHY).
This is the clock setup used by the boards cu
The RK3368-uQ7 (codenamed 'Lion') is a micro-Qseven (40mm x 70mm,
MXM-230 edge connector compatible with the Qseven specification)
form-factor system-on-module based on the octo-core Rockchip RK3368.
It is designed, supported and manufactured by Theobroma Systems.
It provides the following feature
This adds the TPL_DRIVER_MISC_SUPPORT option to allow activation of
DRIVER_MISC_SUPPORT for devices that need it in the TPL stage.
Signed-off-by: Philipp Tomsich
---
common/spl/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git a/common/spl/Kconfig b/common/spl/Kconfig
index f49b
For the RK3368, we want to use OF_PLATDATA in TPL, but full OF_CONTROL
in SPL: this requires the introduction of a new family of
configuration options to decouple SPL_OF_CONTROL and SPL_OF_PLATDATA
from TPL.
Consequently, Makefile.spl needs to be adjusted to test for these
configuration items thro
The RK3368 GRF header was still defines with a shifted-mask but with
non-shifted function selectors for the IOMUX defines. As the RK3368
support is still fresh enough to allow a quick rename, we do this now
before having more code use this.
As some of the downstream drivers (e.g. the Designware G
The BootROM of the RK3368 Boot ROM does not initialise cntfrq_el0.
This change defines COUNTER_FREQUENCY, which is used by the AArch64 init
code in arch/arm/cpu/armv8/start.S to set up cntfrq_el0.
If the counter-frequency is not correctly set up, the calculation of
delays using the ARMv8 generic t
TPL builds today don't need to call into firmware or set up the MMU
(if this changes, it should be controlled through a config option
whether to include this or not), but include the needed support code
for this anyway.
Even for a feature-rich TPL (including DM support as for the RK3368),
this equ
With the clock support in rk3368_clk_set_rate() conditionalized on
various feature definitions, 'priv' can remain unused (e.g. in the
SPL build when only MMC is enabled).
Signed-off-by: Philipp Tomsich
---
drivers/clk/rockchip/clk_rk3368.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Even though there's now a TPL_DM configuration option, the spl logic
still checks for SPL_DM and thus does not pick up the proper config
option.
This introduces the use of CONFIG_IS_ENABLED(DM) in spl.c to always
pick up the desired configuration option instead of having a
hard-coded check for the
The RK3368 TRM recommends to configure the bandwith adjustment (CON2)
for PLLs to NF/2. This implements this for all reconfigurations of
PLLs and removes the 'has_bwadj' flag (as the RK3368 always has the
bandwidth-adjustment feature according to its manual).
Signed-off-by: Philipp Tomsich
---
This adds a DRAM controller driver for the RK3368 and places it in
drivers/ddr/rockchip (where the other DM-enabled DRAM controller
drivers for rockchip devices should also be moved eventually).
At this stage, only the following feature-set is supported:
- DDR3
- 32-bit configuration (i.e. fully
With SPL and TPL support for the RK3368 in place, mark SPL and TPL as
supported from Kconfig for the RK3368. As this is primarily tested on
the RK3368-uQ7, we'll leave it to board's individual defconfig to
enable.
Also enable DEBUG_UART_BOARD_INIT for the RK3368, so we get output
during the early
To simplify drivers/Makefile a bit when using TPL/SPL, we consistently
use the $(SPL_TPL_) macro to test for drivers that have separate
configuration symbols for the full U-boot, SPL and TPL stages.
Instead of explicitly repeating them in two separate if-guarded
sections of the Makefile, we can now
With the new common SDRAM code for Rockchip, we need to define
CONFIG_SYS_SDRAM_BASE to correctly indicate the start of the physical
address range mapping onto DRAM.
Signed-off-by: Philipp Tomsich
---
include/configs/rk3368_common.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/co
The RK3368 option in Kconfig referred to the RK3328 (copy-and-paste)
and had a few typos and unnecessarily used UTF-8 characters. While
fixing this, I also reformatted and further clarified the text
(e.g. made the grouping into a a big and little cluster of 4 cores
each explicit).
Signed-off-by:
The ITS file generated warnings due to @ designations in the naming
which cause DTC to complain as follows:
Warning (unit_address_vs_reg): Node /images/uboot@1 has a unit name, but no
reg property
Warning (unit_address_vs_reg): Node /images/atf@1 has a unit name, but no reg
property
Warning
For the RK3368, we use a multi-stage boot-process consisting of the
following:
1. TPL: initalises DRAM, returns to boot-ROM (which then loads
the next stage and transfers control to it)
2. SPL: a full-features SPL stage including OF_CONTROL and FIT
image loading, which f
The utility functions in sdram_common.c will be useful both for some
SPL implementations (and if unused, the linked will discard these
anyway) and for the full U-Boot stage.
This changes selects sdram_common.o through the $(SPL_TPL_) macro to
allow better control of its inclusion through the CONFI
SPL_CLK should also depend on SPL_DM (and not just on CLK).
Add the additional dependency.
Signed-off-by: Philipp Tomsich
---
drivers/clk/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
index 44da716..9c13587 100644
--- a/dri
Handling TPL and SPL in the Makefile for mach-rockchip was based on
nested if checks and/or if-else-if paths. This can be simplified and
made more readable by using $(SPL_TPL_) and by introducing
intermediate variables for the aggregation of SPL and TPL features.
Signed-off-by: Philipp Tomsich
-
To implement a TPL stage (incl. its DRAM controller setup) for the
RK3368, we'll want to configure the DPLL (DRAM PLL).
This commit implements setting the DPLL (CLK_DDR) and provides PLL
configuration details for the common DRAM operating speeds found on
RK3368 boards.
Signed-off-by: Philipp Toms
The RK3368 has both a limited SPL size (just 0x7000 bytes) and the
added challenge of booting in AArch64, which increases the code size
for SPL (particularily when using the LP64 programming model). For
this reason we expect the RK3368 to always use OF_PLATDATA for its
SPL stage.
This change adds
On the RK3368 we use a TPL-stage similar to Rockchip's DDR init
(i.e. it initialises DRAM, leaves some info for the next stage and
returns to the BootROM). To allow compatibility with Rockchip's DDR
init code, we use the same register os_reg2 in pmugrf for passing
this info (i.e. DRAM size and con
The original clock support for MMC/SD cards on the RK3368 suffered
from a tendency to select a divider less-or-equal to the the one
giving the requested clock-rate: this can lead to higher-than-expected
(or rather: higher than supported) clock rates for the MMC/SD
communiction.
This change rewrite
As include/malloc.h already checks for SYS_MALLOC_SIMPLE using the
CONFIG_IS_ENABLED macro, we need to move to having separate entries
as we switch to fully separate configuration for SPL and TPL.
Signed-off-by: Philipp Tomsich
---
common/spl/Kconfig | 9 +
1 file changed, 9 insertions(
From: Klaus Goger
Prefix the bl31 firmware needed to build uboot.itb so it can coexist in
the build area with ATFs from other boards (i.e. lion_rk3368).
Signed-off-by: Klaus Goger
Signed-off-by: Philipp Tomsich
---
board/theobroma-systems/puma_rk3399/README | 2 +-
board/theobroma-s
With the RK3368's limited TPL size, we'll want to use OF_PLATFDATA for
the SPL stage. This implements support for OF_PLATDATA in the clock
driver for the RK3368.
Signed-off-by: Philipp Tomsich
---
drivers/clk/rockchip/clk_rk3368.c | 17 +
1 file changed, 17 insertions(+)
diff
The RK3368 has two SD/MMC controllers that can be used from U-Boot
both during SPL and for booting an OS from the full bootloader stage.
While both are configured to (mostly) sensible settings from the BROM,
additional configuration for the MMC controller is needed to configure
it to 8bit mode.
Th
To allow for a finer-grained control of features for TPL and SPL
builds all modules/boot-methods/etc. need to be consistently selected
based on the $(SPL_TPL_) macros.
This allows splitting the associated config-options in Kconfig: we
don't split the Kconfig options here and now, as this should ha
The back-to-bootrom option is rather unfortunately named
CONFIG_ROCKCHIP_SPL_BACK_TO_BOOTROM
instead of
CONFIG_SPL_ROCKCHIP_BACK_TO_BOOTROM
To make is selectable through CONFIG_IS_ENABLED(ROCKCHIP_BACK_TO_BOOTROM),
we need to rename it. At the same time, we introduce a TPL_ variant of
the opt
This change introduces TPL variants of the REGMAP and SYSCON config
options (i.e. TPL_REGMAP and TPL_SYSCON in analogy to SPL_REGMAP and
SPL_SYSCON) in preparation of a finer-grained feature selection for
building feature-rich TPL variants.
Signed-off-by: Philipp Tomsich
---
drivers/core/Kconfi
To allow finer grained selection of features for TPL, we introduce
TPL_RAM (in analogy to SPL_RAM).
Signed-off-by: Philipp Tomsich
---
drivers/ram/Kconfig | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/ram/Kconfig b/drivers/ram/Kconfig
index e75c23f..836be25 100644
--- a/d
On the RK3368, we want our TPL to use the 'return to bootrom' boot
method (to have the bootrom load up the SPL stage) and then continue
with different boot methods (MMC, SPI, etc.) from SPL.
This adds the config option needed to control the availabily of the
'return to bootrom' boot-method separat
This commit models the dependency from SPL_RAM to SPL_DM in Kconfig.
Signed-off-by: Philipp Tomsich
---
drivers/ram/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ram/Kconfig b/drivers/ram/Kconfig
index 61afd7a..e75c23f 100644
--- a/drivers/ram/Kconfig
+++ b
The back-to-bootrom support for Rockchip is equivalent to an
(assembly) implementation of setjmp/longjmp (i.e. it saves the
stack-pointer, link-register and callee-saved registers). Up until
now, this had only been implemented for AArch32 (i.e. ARMv7 or older),
which puts the new ARMv8 devices (whi
With the finer-grained control over LIBGENERIC_SUPPORT for TPL/SPL (i.e.
with the newly introduced distinction between TPL_LIBGENERIC_SUPPORT and
SPL_LIBGENERIC_SUPPORT), we can simplify the #ifdef-check to simply use
CONFIG_IS_ENABELD.
Signed-off-by: Philipp Tomsich
---
arch/arm/mach-rockchip/
SPL_REGMAP and SPL_SYSCON were marked as depending on DM, when a
stricter dependency of SPL_DM was possible. This commit makes the
prereq more specific.
Signed-off-by: Philipp Tomsich
---
drivers/core/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/core/
Some devices (e.g. the RK3368) have only limited SRAM, but provide
support for loading the next boot stage after our SPL performs basic
setup (e.g. DRAM).
For target systems like these, we add a boot device BOOTROM that will
invoke a board-specific hook to return to the bootrom (if supported).
Si
When migrating to Kconfig there may be cases where the symbol to be
migrated depends on a preprocessed or calculated value, and thus
moveconfig.py will not migrate it correctly. Introduce an easily
hackable tool, tools/printvars.c that will give the final value. Hack
the main Makefile to only bui
Hi,
I resend the e-mail as you asked !
Can help in this tip .
Best Regards
Perfeito,Alexander
De: s...@google.com em nome de Simon Glass
Enviado: segunda-feira, 17 de julho de 2017 19:50
Para: Alexandre N. Perfeito
Assunto: Re: Uboot compatible wit
On Mon, Jul 17, 2017 at 04:44:55PM +0300, Sam Protsenko wrote:
> Also introduce CONFIG_USE_BOOTARGS option so we can control if
> CONFIG_BOOTARGS defined at all.
>
> Signed-off-by: Sam Protsenko
[snip]
> +config USE_BOOTARGS
> + bool "Enable boot arguments"
> + default n
n is default, w
Dear Jeff,
In message <9CEC332718C5B346927BF91C9F4A66EAC03346@prgmbx01> you wrote:
>
> New to U-Boot. It came installed with the BSP on a vendor MPC board
> to boot vxWorks. I have a requirement to use a checksum when
> downloading the vxWorks ELF image. Our development environ is Windows
> 7, us
Up to now the boot time supported only a single event.
This patch now allows four events.
Signed-off-by: Heinrich Schuchardt
---
v2
add TPL constants
consider multiple events in efi_wait_for_event
move notification to new function efi_signal_event
---
include/efi_api.h
efi_create_event is refactored to make it possible to call it
internally. For EFI applications wrapper function
efi_create_event_ext is created.
Signed-off-by: Heinrich Schuchardt
---
v2
new patch
---
include/efi_loader.h | 6 ++
lib/efi_loader/efi_boottime.c | 35 +
Currently U-Boot only allows a single event. This is sufficient to run
grub but not for other workloads as iPXE.
The EFI_SIMPLE_TEXT_INPUT_PROTOCOL requires an event WaitForKey. This
is used for instance by the iPXE shell.
The 1st patch replaces void * by struct efi_event * where applicable.
Thi
efi_set_timer is refactored to make the function callable internally.
Wrapper function efi_set_timer_ext is provided for EFI applications.
Signed-off-by: Heinrich Schuchardt
---
v2
new patch
---
include/efi_loader.h | 3 +++
lib/efi_loader/efi_boottime.c | 21 +-
Set up a timer event and the WaitForKey event.
In the notify function of the timer event check for console input
and signal the WaitForKey event accordingly.
Signed-off-by: Heinrich Schuchardt
---
v2
dynamically register events to monitor the serial console
input
---
cmd/bootefi.
In efi_set_timer we receive the trigger time in intervals of 100 ns.
We should convert it to intervals of 1000 ns by 64bit division.
The patch supplies function efi_div10 that uses multiplication to
implement the missing 64 bit division.
Signed-off-by: Heinrich Schuchardt
---
v2
move thi
The UEFI standard defines the type for the tpl level as EFI_TPL
alias UINTN.
UINTN is an integer is defined as an unsigned integer of native
width. So we can use size_t for the definition.
Signed-off-by: Heinrich Schuchardt
---
v2
new patch
---
include/efi_api.h | 8 +--
In our implementation the internal structure of events is known.
So use the known type instead of void.
Signed-off-by: Heinrich Schuchardt
---
v2
new patch
---
include/efi_api.h | 23 +--
lib/efi_loader/efi_boottime.c | 25 ++---
2 file
In the source_file_format.txt file we talk about how to construct a
valid FIT image. While it already says to look at the source for the
full list, add kernel_noload to the explicit list of types. This is
arguably the most important type to use as most often we are including a
kernel that will ru
Hi Maxime,
On Wed, Jul 12, 2017 at 9:34 AM, Maxime Ripard
wrote:
> The -mno-unaligned-access flag used on ARM to prevent GCC from generating
> unaligned accesses (obviously) will only do so on packed structures.
>
> It seems like gcc 7.1 is a bit stricter than previous gcc versions on this,
> and
On Tue, Jul 18, 2017 at 10:10:15AM -0500, Andrew F. Davis wrote:
> On 07/18/2017 07:59 AM, Tom Rini wrote:
> > On Mon, Jul 17, 2017 at 01:01:36PM -0500, Andrew F. Davis wrote:
> >> From: Madan Srinivas
> >>
> >> The load address of ramdisk, rdaddr is 0x8808 and fit_loadaddr
> >> is defined as
Hello Tom, hello Albert,
I did not see any objections.
Can this be merged?
https://patchwork.ozlabs.org/patch/774142/
Best regards
Heinrich
On 06/09/2017 10:13 PM, Heinrich Schuchardt wrote:
> The Odroid C2 has two GiB of memory with two reserved regions.
> reg = <0x0 0x0 0x0 0x100>;
> re
On 07/18/2017 03:12 PM, Alexander Graf wrote:
> On 07/11/2017 10:06 PM, Heinrich Schuchardt wrote:
>> efi_open_protocol was implemented to call a protocol specific open
>> function to retrieve the protocol interface.
>>
>> The UEFI specification does not know of such a function.
>>
>> It is not pos
On Mon, Jul 17, 2017 at 12:59:14PM -0500, Andrew F. Davis wrote:
> We first split the CONFIG_BOOTCOMMAND into its components to improve
> readability. We then make the following order changes:
>
> - Run findfdt first so the fdt name can be used in envboot like OMAP
> - Install the boot monitor
On Mon, Jul 17, 2017 at 12:59:12PM -0500, Andrew F. Davis wrote:
> Updates the default u-boot environment variables to support FIT image
> loading.
>
> Signed-off-by: Andrew F. Davis
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description: Digital signature
_
On Mon, Jul 17, 2017 at 01:02:02PM -0500, Andrew F. Davis wrote:
> From: "Srinivas, Madan"
>
> The inline assembly functions in mon.c assume that the caller will
> check for the return value in r0 according to regular ARM calling
> conventions.
>
> However, this assumption breaks down if the co
On Mon, Jul 17, 2017 at 12:59:13PM -0500, Andrew F. Davis wrote:
> From: Madan Srinivas
>
> Updates the default u-boot environment variables to support secure
> boot. On secure devices, a secure boot monitor (sec-bm) needs to
> be installed by u-boot.
>
> Signed-off-by: Madan Srinivas
Reviewe
On Mon, Jul 17, 2017 at 12:59:15PM -0500, Andrew F. Davis wrote:
> From: Madan Srinivas
>
> On early K2 devices (eg. K2HK) the secure ROM code does not support
> loading secure code to firewall protected memory, before decrypting,
> authenticating and executing it.
>
> To load the boot monitor
On Mon, Jul 17, 2017 at 12:59:11PM -0500, Andrew F. Davis wrote:
> Hello all,
>
> This series adds the default environment variables needed to boot
> K2x family secure devices.
>
> Thanks,
> Andrew
>
> Andrew F. Davis (2):
> configs: k2x_evm: Adds FIT loading environment variables
> configs
On Sun, Jul 16, 2017 at 07:59:18PM +0530, Lokesh Vutla wrote:
> board_is*("rev", board_ti_get_rev()) uses strncmp() for
> revison detection and assumes it is success if return value
> is <= 0. This will fail in case of multiple versions, as
> revb will be true for board_is_*revb() and board_is_*re
On Sun, Jul 16, 2017 at 07:59:19PM +0530, Lokesh Vutla wrote:
> BeagleBoard X15 revC board is similar to X15 revB1 except
> with a SR2.0 where revB1 uses a SR1.1. Add board detection
> support for revC.
>
> Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description:
On Tue, Jul 18, 2017 at 05:06:49PM +0200, Alexander Graf wrote:
> On 07/18/2017 04:54 PM, Simon Glass wrote:
> >Hi Alex,
> >
> >On 18 July 2017 at 07:47, Alexander Graf wrote:
> >>On 07/18/2017 04:00 PM, Simon Glass wrote:
> >>>Hi,
> >>>
> >>>On 12 July 2017 at 05:52, Alexander Graf wrote:
>
On Tue, Jul 18, 2017 at 05:01:39PM +0200, Daniel Schwierzeck wrote:
> 2017-07-18 16:00 GMT+02:00 Simon Glass :
> > Hi Daniel,
> >
> > On 10 July 2017 at 15:09, Daniel Schwierzeck
> > wrote:
> >>
> >>
> >> Am 09.07.2017 um 22:52 schrieb Simon Glass:
> >>> This converts the following to Kconfig:
> >
I no longer have any of these boards, mark boards orphan.
Signed-off-by: Marek Vasut
Cc: Tom Rini
---
board/aries/m28evk/MAINTAINERS | 4 ++--
board/aries/m53evk/MAINTAINERS | 4 ++--
board/aries/ma5d4evk/MAINTAINERS | 4 ++--
board/aries/mcvevk/MAINTAINERS | 4 ++--
4 files changed, 8 in
From: Patrice Chotard
STM32F7 and H7 shared the same SDRAM control block.
On STM32H7 few control bits has been added.
The current driver need some minor adaptation as FMC block
enable/disable for H7.
Signed-off-by: Patrice Chotard
---
v2: _ rework comment
_ replace generic_clear_bit/set_bit
From: Patrice Chotard
FMC is able to manage 2 SDRAM banks, but the current driver
implementation is only able to manage the first SDRAM bank.
Even if only bank2 is used, some bank1 registers must be
configured.
Signed-off-by: Patrice Chotard
Reviewed-by: Simon Glass
---
v2: _ add Reviewed-by
From: Patrice Chotard
Retrieve RAM base address from DT instead of using STM32_SDRAM_FMC
For STM32F7, FMC block base address is 0xA000, but SDRAM
registers are located at offset 0x140 inside FMC block.
Update the stm32_fmc_regs fields with all FMC registers
to map SDRAM registers at the righ
From: Patrice Chotard
FMC driver is now able to discover the bank number by
parsing bank subnodes.
Signed-off-by: Patrice Chotard
Reviewed-by: Simon Glass
---
v2: _ add Reviewed-by: Simon Glass
arch/arm/dts/stm32f746-disco.dts | 1 -
arch/arm/dts/stm32f769-disco.dts | 1 -
2 files changed,
From: Patrice Chotard
Replace all fdtdec_get..() calls by ofnode_read...() or dev_read..().
This will allow drivers to support a live device tree.
Signed-off-by: Patrice Chotard
Reviewed-by: Simon Glass
---
v2: _ add Reviewed-by: Simon Glass
drivers/ram/stm32_sdram.c | 83 +
From: Patrice Chotard
Migrate all FMC defines from arch/arm/include/asm/arch-stm32f7/fmc.h
to drivers/ram/stm32_sdram.c
This will avoid to add an additionnal arch-stm32xx/fmc.h file when
a new stm32 family soc will be introduced.
Signed-off-by: Patrice Chotard
Reviewed-by: Vikas Manocha
Revie
From: Patrice Chotard
This series aims to add some improvements to existing ram
driver decicated to stm32 SoCs :
_ some code clean up
_ full DT support, now the FMC base is retrieved through DT
_ update DT API by using ofnode_read...() or dev_read..() instead
of
Hi, Andre,
> -Original Message-
> From: Andre Przywara [mailto:andre.przyw...@arm.com]
> Sent: Tuesday, July 18, 2017 18:24
> To: Kostya Porotchkin
> Cc: Stefan Roese; Marc Zyngier; Thomas Petazzoni; Gregory CLEMENT;
> Antoine Tenart; Andreas Färber; U-Boot; Benjamin (Guodan) Huang
> Subje
Hi Kosta,
On 18/07/17 16:13, Kostya Porotchkin wrote:
> The A37xx SoC does not support boot from SD.
Ah!
> Only boot from eMMC is supported, however your board probably only has
> soldering pads for the eMMC and not eMMC chip installed.
> If you want to play with the bootloader without jeopardi
Hi, Andre,
The A37xx SoC does not support boot from SD.
Only boot from eMMC is supported, however your board probably only has
soldering pads for the eMMC and not eMMC chip installed.
If you want to play with the bootloader without jeopardizing your SPI image,
you have to use either UART or SATA
1 - 100 of 226 matches
Mail list logo
