linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/4 v2] [POWERPC] Kilauea defconfig file
Date: Thu, 11 Oct 2007 15:31:12 +0200	[thread overview]
Message-ID: <200710111531.13022.sr@denx.de> (raw)
In-Reply-To: <1192107771.5534.120.camel@localhost.localdomain>

On Thursday 11 October 2007, Josh Boyer wrote:
> On Thu, 2007-10-11 at 14:08 +0200, Stefan Roese wrote:
> > Signed-off-by: Stefan Roese <sr@denx.de>
> > +# CONFIG_MATH_EMULATION is not set
>
> Does the 405EX have an FPU?

No.

> If not, do you want this set by default so 
> floating point instructions work?

I just checked some existing arch/ppc defconfig files (and arch/powerpc too). 
Most if not all have MATH_EMULATION not set. Even on those PPC's without FPU. 
I assume we see no problems since soft-float is used while compiling.

Anyways, I'll change this and resubmit.

> > +CONFIG_RESOURCES_64BIT=y
>
> I'm not sure about that one.  I see walnut has the same thing for some
> reason, but is it really needed?

No, I don't think it is needed. As all 405 PPC's, the 405EX is 32bit only. 
I'll change this too.

> > +CONFIG_WANT_DEVICE_TREE=y
> > +CONFIG_DEVICE_TREE="walnut.dts"
>
> That looks wrong.  Should be selecting the Kilauea dts

Yes, good catch. Since I'm not using the bootwrapper, I should be able to get 
rid of WANT_DEVICE_TREE too. But it seems to be autoselected in 
arch/powerpc/platforms/Kconfig.cputype for 40x and most other "embedded" 
CPU's. Any idea why this is the case?

Thanks.

Best regards,
Stefan

  reply	other threads:[~2007-10-11 13:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 12:08 [PATCH 4/4 v2] [POWERPC] Kilauea defconfig file Stefan Roese
2007-10-11 13:02 ` Josh Boyer
2007-10-11 13:31   ` Stefan Roese [this message]
2007-10-11 15:37     ` Wolfgang Denk
2007-10-11 16:39       ` Josh Boyer
2007-10-11 20:12     ` Scott Wood
2007-10-11 21:13       ` Josh Boyer
2007-10-12  3:23         ` David Gibson
2007-10-12 15:20           ` Scott Wood

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=200710111531.13022.sr@denx.de \
    --to=sr@denx.de \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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).