From: U.Mutlu <for-gmane@mutluit.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] bug "missing clock-frequency property" (sunxi/sun7i)
Date: Thu, 4 Apr 2019 22:05:27 +0200 [thread overview]
Message-ID: <q85o27$tuh$1@blaine.gmane.org> (raw)
Hi,
I used the latest u-boot version via "git clone git://git.denx.de/u-boot.git
u-boot/"
and built using Lamobo_R1_defconfig.
After copying the u-boot-sunxi-with-spl.bin to the boot device with these
commands:
dd if=/dev/zero of=/dev/mmcblk0 bs=1k count=1023 seek=1
dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8
sync
and rebooting the device, the kernel writes the following errors to the logfile:
[ 0.049630] /cpus/cpu at 0 missing clock-frequency property
[ 0.049647] /cpus/cpu at 1 missing clock-frequency property
How to fix this?
Thx
my build script:
...
make -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- mrproper
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- Lamobo_R1_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
#
# Automatically generated file; DO NOT EDIT.
# U-Boot 2019.04-rc4 Configuration
...
CONFIG_SYS_ARCH="arm"
CONFIG_SYS_CPU="armv7"
CONFIG_SYS_SOC="sunxi"
CONFIG_SYS_BOARD="sunxi"
CONFIG_SYS_CONFIG_NAME="sun7i"
...
CONFIG_DEFAULT_DEVICE_TREE="sun7i-a20-lamobo-r1"
...
--
U.Mutlu
reply other threads:[~2019-04-04 20:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='q85o27$tuh$1@blaine.gmane.org' \
--to=for-gmane@mutluit.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox