> 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. By moving these unused low-level functions into
> seperate function-se
> In order to reuse the support for the u-boot,spl-boot-order property
> from the rk3399, we split it into a reusable module that can be
> included by the SPL code for any of our boards.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> ---
>
> Changes in v4: None
> Changes in
> There is no reasonably robust way (this will be needed so early that
> diagnostics will be limited) to specify the base-address of the secure
> timer through the DTS for TPL and SPL. In order to allow us a cleaner
> way to structure our SPL and TPL stage, we now move to a DM timer
> driver.
>
>
> Let's clean up behind ourselves and move the (newly defined)
> TPL_STACK, TPL_MAX_SIZE and TPL_TEXT_BASE into Kconfig. Given that
> 0x0 might be considered to be valid values for TPL_TEXT_BASE and
> TPL_STACK, we need to introduce helper config options
> ("TPL_NEEDS_SEPARATE_...") to indicate th
> SPL_CLK should also depend on SPL_DM (and not just on CLK).
> Add the additional dependency.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> Reviewed-by: Tom Rini
> ---
>
> Changes in v4: None
> Changes in v3: None
> Changes in v2: None
>
> drivers/clk/Kconfig | 2 +-
>
> This commit models the dependency from SPL_RAM to SPL_DM in Kconfig.
>
> Signed-off-by: Philipp Tomsich
>
> Reviewed-by: Simon Glass
> Reviewed-by: Tom Rini
> ---
>
> Changes in v4: None
> Changes in v3: None
> Changes in v2: None
>
> drivers/ram/Kconfig | 2 +-
> 1 file changed, 1 insert
Spotted this debugging OpenBSD's bootloader in qemu. (Wouldn't really
fix anything, the problem was not having any disks, but we should
probably return the correct error code.)
Signed-off-by: Rob Clark
---
v2: early-return in the EFI_NOT_FOUND case, as suggested by Heinrich
lib/efi_loader/efi_
On Sun, Aug 6, 2017 at 6:49 PM, Rob Clark wrote:
> On Sun, Aug 6, 2017 at 1:28 PM, Mark Kettenis wrote:
>>> From: Rob Clark
>>> Date: Sun, 6 Aug 2017 11:34:15 -0400
>>>
>>> On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark wrote:
>>> >
>>> > I've started trying to hack up test_efi_loader.py to add a t
> From: Rob Clark
> Date: Sun, 6 Aug 2017 13:49:43 -0400
>
> On Sun, Aug 6, 2017 at 1:28 PM, Mark Kettenis wrote:
> >> From: Rob Clark
> >> Date: Sun, 6 Aug 2017 11:34:15 -0400
> >>
> >> On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark wrote:
> >> >
> >> > I've started trying to hack up test_efi_loa
On Thu, Jul 27, 2017 at 6:55 AM, Tom Rini wrote:
> On Wed, Jul 26, 2017 at 09:22:06PM -0500, Adam Ford wrote:
>> On Wed, Jul 26, 2017 at 8:52 PM, Tom Rini wrote:
>> > On Wed, Jul 26, 2017 at 09:03:37AM -0500, Adam Ford wrote:
>> >
>> >> This converts the following to Kconfig:
>> >>CONFIG_SYS_
> Date: Sun, 6 Aug 2017 20:21:45 +0200 (CEST)
> From: Mark Kettenis
>
> > Mind sending me or pastebin'ing your u-boot .config? There are some
> > different device-path construction depending on legacy vs
> > CONFIG_DM+CONFIG_BLK (the legacy case *looks* right to me, and is used
> > by vexpress_c
> From: Rob Clark
> Date: Sun, 6 Aug 2017 12:23:50 -0400
>
> Spotted this debugging OpenBSD's bootloader in qemu. (Wouldn't really
> fix anything, the problem was not having any disks, but we should
> probably return the correct error code.)
>
> Signed-off-by: Rob Clark
Reviewed-by: Mark Ket
On Sun, Aug 6, 2017 at 2:21 PM, Mark Kettenis wrote:
>> From: Rob Clark
>> Date: Sun, 6 Aug 2017 13:49:43 -0400
>>
>> On Sun, Aug 6, 2017 at 1:28 PM, Mark Kettenis
>> wrote:
>> >> From: Rob Clark
>> >> Date: Sun, 6 Aug 2017 11:34:15 -0400
>> >>
>> >> On Sun, Aug 6, 2017 at 10:45 AM, Rob Clark
On Sun, Aug 6, 2017 at 2:37 PM, Mark Kettenis wrote:
>> Date: Sun, 6 Aug 2017 20:21:45 +0200 (CEST)
>> From: Mark Kettenis
>>
>> > Mind sending me or pastebin'ing your u-boot .config? There are some
>> > different device-path construction depending on legacy vs
>> > CONFIG_DM+CONFIG_BLK (the leg
On Sun, Aug 6, 2017 at 2:47 PM, Rob Clark wrote:
> On Sun, Aug 6, 2017 at 2:37 PM, Mark Kettenis wrote:
>>> Date: Sun, 6 Aug 2017 20:21:45 +0200 (CEST)
>>> From: Mark Kettenis
>>>
>>> > Mind sending me or pastebin'ing your u-boot .config? There are some
>>> > different device-path construction
> From: Rob Clark
> Date: Sun, 6 Aug 2017 12:10:28 -0400
>
> Signed-off-by: Rob Clark
> ---
> Kinda works, but since we don't have an 'exit' command like grub, we
> have to reboot, which leaves the "board" in a bad state (I guess,
> since the next test fails). I haven't tackled the travis bits
On Sun, Aug 6, 2017 at 2:54 PM, Mark Kettenis wrote:
>> From: Rob Clark
>> Date: Sun, 6 Aug 2017 12:10:28 -0400
>>
>> Signed-off-by: Rob Clark
>> ---
>> Kinda works, but since we don't have an 'exit' command like grub, we
>> have to reboot, which leaves the "board" in a bad state (I guess,
>> s
Hi Christophe,
On 05/08/2017 14:58, christophe leroy wrote:
Le 14/07/2017 à 23:45, Angelo Dureghello a écrit :
Signed-off-by: Angelo Dureghello
---
arch/m68k/Kconfig | 5 +
board/sysam/stmark2/Kconfig | 15 +++
board/sysam/stmark2/MAINTAINERS | 6 ++
board
Hi Bin,
On 05/08/2017 15:19, Bin Meng wrote:
Hi Angelo,
On Sat, Jul 15, 2017 at 5:45 AM, Angelo Dureghello wrote:
Signed-off-by: Angelo Dureghello
Can you please write something about your board in the commit message?
sure, sending patch v2.
---
arch/m68k/Kconfig
On 08/06/2017 07:15 AM, Simon Glass wrote:
> On 24 July 2017 at 09:07, wrote:
>> From: Patrice Chotard
>>
>> Add CONFIG_DM_USB flag to avoid following compilation errors
>> detected by buildman :
>> +drivers/usb/host/built-in.o: In function `xhci_dwc3_remove':
>> +drivers/usb/host/xhci-dwc3.c:16
Hi Marek,
On 6 August 2017 at 13:17, Marek Vasut wrote:
> On 08/06/2017 07:15 AM, Simon Glass wrote:
>> On 24 July 2017 at 09:07, wrote:
>>> From: Patrice Chotard
>>>
>>> Add CONFIG_DM_USB flag to avoid following compilation errors
>>> detected by buildman :
>>> +drivers/usb/host/built-in.o: I
Sysam stmark2 board is a generic and fully (hw and sw) open board, with
a mcf54415 Coldfire CPU, 128MB of DDR2, 16MB of SPI flash and SD card
as non volatile memories, and a wifi module included on-board.
The board is actually used mainly for Coldfire custodian testing activity
related to the mcf54
Hi :
When run buildman rockchip on the master branch of current
u-boot-rockchip tree, I got warnings about 16 rockchip arm32 based boards:
include/config/auto.config: line x: ARCH: command not found.
the line x is the definition of the: SPL_LDSCRITP
"arch/$(ARCH)/cpu/u-boot-spl.lds
Hi JJ,
On 08/04/2017 09:26 PM, Jean-Jacques Hiblot wrote:
> Hi Jaehoon,
>
>
> On 01/08/2017 06:23, Jaehoon Chung wrote:
>> Dear JJ,
>>
>> On 07/19/2017 10:52 PM, Jean-Jacques Hiblot wrote:
>>> In the TI SOCs a PBIAS cell exists to provide a bias voltage to the MMC1
>>> IO cells. Without this bia
Hi Marek,
2017-08-06 4:23 GMT+09:00 Marek Vasut :
> On 08/03/2017 02:36 PM, Masahiro Yamada wrote:
>> Hi Marek,
>
> Hi,
>
> [...]
>
>>> +static u32 uniphier_sd_readl(struct uniphier_sd_priv *priv, const u32 reg)
>>
>> "const" is unneeded here.
>
> Why? The function should not modify reg , so it i
On 8/5/2017 8:12 AM, Nishanth Menon wrote:
> ES2.0 descopes OPP_LOW definition. So remove it from macros defined.
Reviewed-by: Lokesh Vutla
Thanks and regards,
Lokesh
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
On 8/5/2017 8:12 AM, Nishanth Menon wrote:
> OMAP5432 did go into production with AVS class0 registers which were
> mutually exclusive from AVS Class 1.5 registers.
>
> Most OMAP5-uEVM boards use the pre-production Class1.5 which has
> production efuse registers set to 0. However on production d
On Jum, 2017-08-04 at 15:10 +0200, Marek Vasut wrote:
> On 08/04/2017 07:37 AM, Chee, Tien Fong wrote:
> >
> > On Rab, 2017-08-02 at 23:32 +0200, Marek Vasut wrote:
> > >
> > > On 08/02/2017 12:21 PM, Chee, Tien Fong wrote:
> > > >
> > > >
> > > > On Isn, 2017-07-31 at 12:53 +0200, Marek Vasut
This appears to be a simple typo that dates back to the original
implementation of board_detail in commit e79394643b26 ("common: Update
cmd_bdinfo for PPC").
Signed-off-by: Chris Packham
---
cmd/bdinfo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/bdinfo.c b/cmd/bdin
On 07/31/2017 06:33 PM, Łukasz Majewski wrote:
> Hi Seung-Woo,
>
>> During using dwc2 usb gadget, if usb message size is too small,
>> following cache misaligned warning is shown:
>>
>>CACHE: Misaligned operation at range [bfdbcb00, bfdbcb04]
>>
>> Align size of invalidating dcache before star
101 - 130 of 130 matches
Mail list logo
