All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 5/6] PowerPC 440EPx: Sequoia board support
Date: Fri, 03 Aug 2007 22:35:36 +1000	[thread overview]
Message-ID: <1186144536.5981.5.camel@gruick> (raw)
In-Reply-To: <200708031425.19475.sr@denx.de>


> Depends on interpretation. IIRC currently the same die is used for 440EPx and 
> 440GRx. I could be wrong here though and it is just a bug in the chip. But 
> anyway we should support this somehow. Could be that I missed this in the 
> current 440GRx (Rainier) arch/ppc support too. I have to admit, that no 
> clever solution comes to my mind right away though.

We can always come up with some kind of runtime detection, by turning on
MSR:FP, issuing an fp instruction and catching the illegal instruction
fault if any :-)

Ben.

  reply	other threads:[~2007-08-03 12:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 15:16 [PATCH 5/6] PowerPC 440EPx: Sequoia board support Valentine Barshak
2007-08-01  2:15 ` David Gibson
2007-08-01  5:01   ` Segher Boessenkool
2007-08-01  5:05     ` David Gibson
2007-08-02 20:32       ` Josh Boyer
2007-08-03  8:39         ` Kumar Gala
2007-08-03 12:57           ` Josh Boyer
2007-08-02 20:34 ` Josh Boyer
2007-08-03  6:44   ` Stefan Roese
2007-08-03 11:36     ` Valentine Barshak
2007-08-03 12:25       ` Stefan Roese
2007-08-03 12:35         ` Benjamin Herrenschmidt [this message]
2007-10-05 18:36           ` Valentine Barshak
2007-10-05 22:17             ` Benjamin Herrenschmidt
2007-08-03 11:20   ` Valentine Barshak

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=1186144536.5981.5.camel@gruick \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@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.