public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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: Tue, 15 Jun 2010 18:12:40 +0000	[thread overview]
Message-ID: <0016e6480e82129c210489158d26@google.com> (raw)
In-Reply-To: <0016e646536657d603048903e5b2@google.com>

On Jun 14, 2010 5:08pm, gnemas at gmail.com wrote:
> On Jun 14, 2010 4:30pm, Wolfgang Denk wd at 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";

I discovered what was causing the FPU problem. Maybe this might help  
someone.

I noticed that my processor was being recognized by Linux as a 440GRX  
(which does not have FPU) rather than the correct 440EPx. It seems that  
these two processors have the same PVR value. The kernel differentiates  
these based on the value of the CPU model in the device tree.

Even though I had the correct entries in my device tree source, the kernel  
was not finding the correct model entry.

The problem was that I was using the device tree compiler from

git://git.kernel.org/pub/scm/linux/kernel/git/galak/dtc.git

instead of the one included with the kernel source. When I started working  
on this, it did not occur to me that the dtc was included in the kernel  
tree, so I had searched for it online and discovered that git repository.  
The galak dtc reports version 1.1.0, whereas the kernel dtc reports versio  
1.2.0.

So it all works correctly now.

Thanks for the DT pointer.

Gregg

  parent reply	other threads:[~2010-06-15 18:12 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
2010-06-14 21:23     ` Wolfgang Denk
2010-06-15 18:12     ` gnemas at gmail.com [this message]
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=0016e6480e82129c210489158d26@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox