From: Subodh Nijsure <snijsure-4jo+YWezP1RWk0Htik3J/w@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Booting MX28-EVK without bootloader support
Date: Fri, 8 Jun 2012 00:53:46 -0700 [thread overview]
Message-ID: <4FD1AF8A.8070406@grid-net.com> (raw)
In-Reply-To: <1339113456-27089-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 956 bytes --]
I am using git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
for-next branch to get familiar with device tree.
I am following procedure described in thread --
http://lists.ozlabs.org/pipermail/devicetree-discuss/2012-April/014600.html
Turn on CONFIG_ARM_APPENDED_DTB, CONFIG_ARM_ARAG_DTB, then appending
imx28-evk.dtb and constructing zImage_dtb
However this image never initializes network interfaces, I can't mount
nfs as rootfs. Is the appended DTB supposed to work from above
referenced git repo & branch?
Pardon me, if this is too basic DT question on device tree
initialization sequence. During initialization I see that -
mxs_machine_init gets called which invokes of_platform_populate().
However I don't see the mx28evk_init() function never gets called,
should that function be getting called?
If mx28evk_init shouldn't be called how is MXS ethernet driver supposed
to get registered when using device tree?
-Subodh
[-- Attachment #1.2: Type: text/html, Size: 1952 bytes --]
[-- Attachment #2: Type: text/plain, Size: 192 bytes --]
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
next prev parent reply other threads:[~2012-06-08 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 23:57 [PATCH] of: export of_platform_populate() Stephen Warren
[not found] ` <1339113456-27089-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-06-08 7:53 ` Subodh Nijsure [this message]
2012-06-11 14:26 ` Rob Herring
2012-06-20 18:00 ` Stephen Warren
2012-06-20 19:32 ` Rob Herring
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=4FD1AF8A.8070406@grid-net.com \
--to=snijsure-4jo+ywezp1rwk0htik3j/w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).