On Tue, Nov 27, 2018 at 01:45:02PM +0100, Rouven Czerwinski wrote:
> Commit 7e497d48acbd1184e3f6bd23bd16dfae84dd1129 introduced a name change which
> breaks support for the fixed clkdev for uart and sdhci for RPI.
> Use clkdev_add_physbase instead to be independant from the device tree names.
>
>
On Tue, Nov 27, 2018 at 08:13:00AM +0100, Steffen Trumtrar wrote:
> Instead of always printing the timing registers, make it a debug information
> only.
>
> Signed-off-by: Steffen Trumtrar
> ---
> drivers/mtd/nand/nand_denali.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied,
On Wed, Nov 28, 2018 at 03:53:45PM +0100, Erwin Rol wrote:
> Hallo All,
>
> I am trying to get USB device (DFU) to work on my Phytec Segin board
> (imx6ul SOC).
>
> I can upload barebox with imx-usb-loader and it starts fine (so USB
> hardware is working)
>
> Than when barebox runs I want to
Hallo All,
I am trying to get USB device (DFU) to work on my Phytec Segin board
(imx6ul SOC).
I can upload barebox with imx-usb-loader and it starts fine (so USB
hardware is working)
Than when barebox runs I want to put that same USB port in DFU mode and
update the nand flash (barebox, env,
Hello All,
I see there are they ways to stop the autoboot in barebox as of now,
- ENTER
- Ctrl - C
- Any single Key
please correct me if I have missed anything.
Question: Do we have option for sequence of character to stop the
autoboot?
--
Thanks,
Parthiban N
DENX Software Engineering GmbH,
On Wed, 28 Nov 2018 12:20:49 +0100
Michael Tretter wrote:
> This is v2 of the series to add support for the Xilinx Zynq Ultrascale+ MPSoC
> platform and the ZCU104 Evaluation Kit.
>
> The patch "[PATCH v2 3/4] ARM: aarch64: add ENTRY_PROC macro for arm64"
> probably needs a closer look, as it
Without this flag, gcc generates code to save the Q/V registers to the
stack for handling the va_list in pr_print(). Saving the registers is
useless, as the registers are never restored, but accessing the
registers to save them hangs the CPU.
Follow the Linux arch/arm64/Makefile and use the
This is v2 of the series to add support for the Xilinx Zynq Ultrascale+ MPSoC
platform and the ZCU104 Evaluation Kit.
The patch "[PATCH v2 3/4] ARM: aarch64: add ENTRY_PROC macro for arm64"
probably needs a closer look, as it adds a generic macro that is expected to
be used by other arm64
arm64 has no __naked__ attribute and the compiler adds a function prologue
for saving x29 and x30 to the stack for all C functions. This includes
functions defined using the ENTRY_FUNCTION macro. Therefore, the stack
needs to be setup before entering a C function, which is not possible if
the
Add support for the Xilinx Zynq Ultrascale+ MPSoC architecture (ZynqMP)
and the Xilinx ZCU104 board.
Barebox is booted as BL33 in EL-1 and expects that a BL2 (i.e. the FSBL)
already took care of initializing the RAM. Also for debug_ll, the UART
is expected to be already setup correctly. Thus, you
Commit e1287b1a8b27 ("arm: rework lib directory to support arm64")
restructured the lib directory and added the lib64 directory. It moved
the existing .gitignore to the lib32 directory but didn't add a new
.gitignore for lib64.
Thus building Barebox for arm64 results in stray barebox.lds files.
Signed-off-by: Jules Maselbas
---
drivers/clocksource/Kconfig | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
index 3caf72503..02659d86a 100644
--- a/drivers/clocksource/Kconfig
+++ b/drivers/clocksource/Kconfig
@@ -1,3 +1,5 @@
12 matches
Mail list logo
