From: Fabian Schwartau <fabian@opencode.eu>
To: yocto@yoctoproject.org
Subject: Board files vs. device tree
Date: Sun, 21 Dec 2014 16:32:18 +0100 [thread overview]
Message-ID: <5496E802.1050904@opencode.eu> (raw)
Hi,
I am building a system with yocto for a board which is similar to
Beagleboard-xM. So I used beagleboard as a starter. However, the kernel
is not booting. Uboot just tells me that he is starting the kernel and
then nothing happens any more.
So I guess there is something wrong with the pin muxing as my board is a
little different from Beagleboard.
At the moment I am using the device tree file for beagleboard-xm by
passing it with the uboot command
bootm ${loadaddr} - ${dtbaddr}
I looked around in the kernel and had to notice that there are still
several board files build in the kernel.
When there are several board files compiled into the kernel, how does
the kernel determine the right one at boot time?
What does the kernel do if there are board files activated and I am also
passing a device tree?
Why are there still board files when the specific board has already a
device tree file?
next reply other threads:[~2014-12-21 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 15:32 Fabian Schwartau [this message]
2014-12-21 17:08 ` Board files vs. device tree Maciek Borzecki
2014-12-21 17:56 ` Fabian Schwartau
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=5496E802.1050904@opencode.eu \
--to=fabian@opencode.eu \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.