From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch v2] fsl-layerscape: fdt: add IFC fixup if no IFC is avaliable in U-Boot
Date: Mon, 02 May 2016 23:32:03 -0500 [thread overview]
Message-ID: <1462249923.16584.24.camel@buserror.net> (raw)
In-Reply-To: <1461823479-15244-1-git-send-email-Qianyu.Gong@nxp.com>
On Thu, 2016-04-28 at 14:04 +0800, Gong Qianyu wrote:
> IFC is considered as a required component in Layerscape platforms' Linux.
What does this mean?
> But if IFC is not enabled in U-Boot on some boards, accessing IFC memory
> space would cause kernel call trace. So disable IFC node in such cases.
That's the symptom, not the problem. The problem is that the kernel is
assuming that U-Boot has done certain initialization, such as the chipselect
registers, and clearing SRAM (though Linux really should be doing the latter).
Why is U-Boot being configured without this?
-Scott
next prev parent reply other threads:[~2016-05-03 4:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 6:04 [U-Boot] [Patch v2] fsl-layerscape: fdt: add IFC fixup if no IFC is avaliable in U-Boot Gong Qianyu
2016-04-30 12:27 ` Mingkai Hu
2016-05-03 4:32 ` Scott Wood [this message]
2016-05-03 6:23 ` Calvin Johnson
2016-05-16 16:47 ` York Sun
2016-05-17 3:47 ` Qianyu Gong
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=1462249923.16584.24.camel@buserror.net \
--to=oss@buserror.net \
--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