From: gnemas at gmail.com <gnemas@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Whose responsibility is it to enable FPU?
Date: Mon, 14 Jun 2010 21:08:52 +0000 [thread overview]
Message-ID: <0016e646536657d603048903e5b2@google.com> (raw)
In-Reply-To: <20100614203055.D8947B7146@gemini.denx.de>
On Jun 14, 2010 4:30pm, Wolfgang Denk <wd@denx.de> wrote:
> U-Boot does not need nor use the FPU, so enabling it would not help
> you in any way.
It may not need it, but enabling it in u-boot did actually fix the problem.
I just called the fpu_enable function in the u-boot post code.
> Linux will do it's own settings, so this is where you need to look for
> your incorrect configuration settings (incorrect CPU description in
> the DT?).
Okay, thanks. I'll try to find out more about how Linux sets this up.
By the way, my dts file has
cpu at 0 {
device_type = "cpu";
model = "PowerPC,440EPx";
next prev parent reply other threads:[~2010-06-14 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 19:02 [U-Boot] Whose responsibility is it to enable FPU? gnemas at gmail.com
2010-06-14 20:10 ` Måns Rullgård
2010-06-14 20:30 ` Wolfgang Denk
2010-06-14 21:08 ` gnemas at gmail.com [this message]
2010-06-14 21:23 ` Wolfgang Denk
2010-06-15 18:12 ` gnemas at gmail.com
2010-06-18 4:17 ` Aggrwal Poonam-B10812
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=0016e646536657d603048903e5b2@google.com \
--to=gnemas@gmail.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 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.