We have not had a good method to debug the early boot stage such as
lowlevel_init function. I guess developers generally use dedicated
debuggers for that, but it is difficult in some cases.
(For example, my debugger cannot connect to the ARM processor when
it is in the secure state. It sometimes
U-Boot does not have arch/arm/kernel, include/uapi directories,
This commit copies files as follows:
Location in Linux -> Location in U-Boot
arch/arm/kernel/debug.S -> arch/arm/lib/debug.S
arch/arm/include/debug/8250.S -> arch/arm/include/debug/8250.S
include/uapi/
Signed-off-by: Masahiro Yamada
---
arch/arm/Kconfig | 8
arch/arm/cpu/armv8/Kconfig | 7 +++
board/armltd/vexpress64/Kconfig| 4
board/freescale/ls2085a/Kconfig| 8
configs/ls2085a_emu_D4_defconfig | 2 +-
configs
We do not have to distinguish CONFIG_TARGET_VEXPRESS_AEMV8A_SEMI
from CONFIG_TARGET_VEXPRESS_AEMV8A. Rename the former to the latter.
Signed-off-by: Masahiro Yamada
Cc: David Feng
Cc: Steve Rae
---
arch/arm/Kconfig | 3 ---
board/armltd/vexpress64/Kconfig| 20
I have been in trouble for a while to debug some nasty problem
where neighter a debugger nor printf() function is available.
I found the lowlevel debug feature in ARM Linux can be used as is
in U-Boot too.
I tested this series on our SoCs (32bit ARM, specificly Coretex-A9).
Because I was not sure
Commit 51148790 added scripts/multiconfig.py written in Python 2
to adjust Kconfig for U-Boot.
It has been hard for Python 3 users because Python 2 and Python 3
are not compatible with each other.
We are not happy about adding a new host tool dependency
(in this case, Python version dependency) f
Commit 51148790 added scripts/multiconfig.py written in Python 2
to adjust Kconfig for U-Boot.
The problem is that Python 2 and Python 3 are not compatible
with each other and some users are using Python 3.
We are not happy about adding host tool dependency (in this case,
Python version dependenc
> From: Wang Huan <[hidden email]>
>
> This patch is to add LETECH support for LS1021AQDS/TWR board.
> For LETECH, lpuart is used as console.
>
I suggest you update README to add some information about this LETECH. I
have no
idea what it is until I dig into some internal documents.
[Alison
On 08/13/2014 11:44 PM, Alison Wang wrote:
> This patch is to add I2C 1,2,3 support for LS102xA.
>
I think the commit message should say which existing I2C driver is
compatible
with the controller of LS201x. From the change, you are using the same
driver
for i.MX. But it is not clear if you a
On 08/13/2014 11:45 PM, Alison Wang wrote:
> On LS1021ATWR, Silicon's Sii9022A HDMI Transmitter
> is used. This patch adds the common setting for this
> chip.
>
Shouldn't this driver stay under driver/video? It is for the HDMI
transmitter,
not Freescale board specific, is it?
[Alison Wang]
On 08/13/2014 11:44 PM, Alison Wang wrote:
> As extra FPGA settings is needed for MDIO read/write
> on LS1021AQDS, private MDIO read/write functions are
> created.
>
> Signed-off-by: Alison Wang <[hidden email]>
> ---
> Change log:
> v4: No change.
> v3: Split from the 0004-arm-ls102xa-A
Dear All,
I'm trying to do a firmware update on my BeagleBone Black using DFU and
nearly getting there:
U-Boot# dfu 0 mmc 1
GADGET DRIVER: usb_dnl_dfu
musb-hdrc: peripheral reset irq lost!
MMC write: dev # 0, block # 63, count 762 ... 762 blocks write: OK
#
DFU complete CRC32: 0xee7826ec
DOW
Hi Vasili,
On 08/14/2014 10:42 PM, Vasili Galka wrote:
When compiling the current code on GCC 4.8.3, the following warnings
appear:
warning: format '%zu' expects argument of type 'size_t', but argument
2 has type 'long unsigned int' [-Wformat=]
There were many mails about such warnings on diff
13 matches
Mail list logo
