ckpatch.pl check for that:
https://lore.kernel.org/u-boot/20250306201540.127646-1...@os-cillation.de/
The original thread has been idle for a few weeks, i was about to ask
how to move forward with the initial problem.
Regards,
Hendrik
Hello,
On 17.03.25 12:10, Quentin Schulz wrote:
Hi Fabio,
On 3/15/25 12:58 PM, Fabio Estevam wrote:
Hi Hendrik,
On Fri, Mar 14, 2025 at 5:09 PM Hendrik Donner
wrote:
In c9713c155127 the device tree was moved
from CONFIG_SPL to CONFIG_SPL_BUILD and later to CONFIG_XPL_BUILD, but
the
build
issue.
Fixes: c9713c15512 ("imx8-u-boot: Fix SPL guard option")
Signed-off-by: Hendrik Donner
---
arch/arm/dts/imx8qm-u-boot.dtsi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/dts/imx8qm-u-boot.dtsi b/arch/arm/dts/imx8qm-u-boot.dtsi
index a
t;)
Signed-off-by: Hendrik Donner
---
arch/arm/dts/imx8qxp-u-boot.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/dts/imx8qxp-u-boot.dtsi b/arch/arm/dts/imx8qxp-u-boot.dtsi
index 8058caae9ba..db6a3dedb95 100644
--- a/arch/arm/dts/imx8qxp-u-boot.dtsi
+++ b/ar
As discussed on the mailing list, move instances of CONFIG_XPL_BUILD
back to the initially used CONFIG_SPL in device trees.
Hendrik Donner (2):
imx8qxp: Do not use CONFIG_XPL_BUILD in device tree
imx8qm: Do not use CONFIG_XPL_BUILD in device tree
arch/arm/dts/imx8qm-u-boot.dtsi | 4
The defines for the different build phases shouldn't be used in device
trees, currently they aren't even defined for device tree pre processing,
resulting in build errors.
Link: https://lists.denx.de/pipermail/u-boot/2025-March/582787.html
Signed-off-by: Hendrik Donner
---
scripts/che
Hello,
On 06.03.25 11:18, Quentin Schulz wrote:
Hi Hendrik,
On 3/5/25 7:35 PM, Hendrik Donner wrote:
[You don't often get email from h...@os-cillation.de. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
The CONFIG_*PL_BUILD defines are currently not de
The CONFIG_*PL_BUILD defines are currently not defined when
preprocessing the dts files, leading to build problems with binman. Set
the defines based on the related CONFIG_*PL values.
Tested-by: Oliver Graute
Signed-off-by: Hendrik Donner
---
scripts/Makefile.lib | 10 ++
1 file
nal blobs and is non-functional: spl.bin
Some images are invalid
Guard creation of flash.bin with CONFIG_XPL_BUILD option.
Fixes: c9713c155127 ("imx8-u-boot: Fix SPL guard option")
Tested-by: Oliver Graute
Signed-off-by: Hendrik Donner
---
arch/arm/dts/imx8qm-u-boot.dtsi | 2 ++
1 file change
Just 2 fixes related to CONFIG_XPL_BUILD usage in dts files with binman.
The second patch works for me, not sure if it is exactly the correct
approach.
Hendrik Donner (2):
imx8qm: Fix build when using SPL
Makefile.lib: Set xPL build related defines for DTB build
arch/arm/dts/imx8qm-u
10/A20
boards (I checked A20-SOM, A20-LIME2, A20-Lime and A10-Lime).
Regards,
Hendrik
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
oes not
seem to have any specific runtime option for enabling or disabling pull
ups or downs, but I didn't really look into this as u-boot already
misbehaves and some of our peripherals won't start on boot because of this.
I hope anyone can help me out.
Regards,
Hendrik
__
Hi,
I now tried to get the latest version from
git://git.denx.de/u-boot-sunxi.git and then replaced the dram.c/h files
with the ones from https://github.com/linux-sunxi/u-boot-sunxi.
That seems to work. The LCD screen no longer flickers!
Regards,
Hendrik
between the mainline and sunxi
sources that could cause this? That was the opposite of what I am doing
now (so sunxi-uboot with mainline kernel instead of now mainline sunxi
with sunxi-kernel)
Regards,
Hendrik
On 03-10-14 11:19, Hans de Goede wrote:
Hi,
On 10/03/2014 10:49 AM, Siarhei Siamashka
igin) of U-boot.
Can anybody shine some light on this? Maybe Hans de Goede? I have seen
his name pop-up a lot of times with the Sunxi branch.
Regards,
Hendrik
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Jens Gehrlein wrote:
> Hi hendrik,
>
> hendrik schrieb:
>> Hi all
>>
>> could someone pls point me to where i can find documentation
>> regarding changes and the implications there of between die Freescale
>> mpc8548 v1 and v2 silicone CPUs. I have searched
Hi all
this is probably a beginers question, but I am finding strange things
when booting with the BDI2000 on my mpc8548 CPU v2 board. I am using the
bdi config for rev2 silicon as shown below: Am i missing something?
;bdiGDB configuration file for SDH/SONET Gateway (MPC8548)
; based on
™ III Integrated Host Processor Family
Reference Manual, Rev. 2
thanks hendrik
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
o to get rid of this error? My initial efforts show by
hacking RD_en = 0 is the only way to get my board to boot. but this
roes not feel like the way to go. I would appreciate any help.
thanks Hendrik
___
U-Boot mailing list
U-Boot@lists.denx.de
ht
Andy Fleming wrote:
> On Fri, Feb 13, 2009 at 6:36 AM, hendrik wrote:
>
>> Hi all
>>
>> When i included the struct as is the my board with the MPC8548 ver1 cpu
>> worked correctly but the board with ver2 CPU does not work.
>> A would appeciate any help
C8548 ver1 cpu
worked correctly but the board with ver2 CPU does not work.
A would appeciate any help
thanks Hendrik
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi all
I would like to boot using the new style FDT kernel booting. I have been
using the guidelines in "u-boot-2009/doc/uImage.FIT/how to" and I have
the latests dtc (v1.2) . But I am unable to compile the FIT image. I
get a syntax error for line 1:
#u-boot/tools/mkimage -f /work/kernel
Kernel command line is:
root=/dev/mtdblock0 ro console=ttyS0,115200
In the console output i dont see ant CFI interaction. I have been throug
my board's default_config basing it closely on tqm8548_defconfig but
coulf not get the CFI interface to work.
a would appreciate any help,
thanks He
Hi All
The MPC8548 board i inherited used to boot a CRAMFS that was made by
mkcramfs in ELDK4.1 using the "-r" option to reverse endian-ness of
filesystem I have switched over ti ELDK4.2 and noted that there is no
longer a "-r" for mkcramfs. I compile linux 2.6.27 using ppc_85xx cross
compiler
he board not using the BDI the bootregion shows the old
uboot image and was not erased.
I think the sram is mapped over the flash boot region and when i try to
erase and cp to the bootreagion the commands and date gets lost. Can
anyone help me find the problem?
th
25 matches
Mail list logo