From: Peter Bergner <bergner@vnet.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] CAS DFP support
Date: Wed, 22 Nov 2006 10:06:04 -0600 [thread overview]
Message-ID: <1164211565.4932.7.camel@otta> (raw)
In-Reply-To: <AA60A1D7-D271-4CE1-A39F-2CE9F605DB16@kernel.crashing.org>
On Wed, 2006-11-22 at 09:46 -0600, Kumar Gala wrote:
> On Nov 22, 2006, at 9:20 AM, Jake Moilanen wrote:
>
> > When booting a Power6 in compat mode, the DFP bit must be set in the
> > client architecture call, or else firmware will downgrade the
> > compliance
> > to P5 compat mode, thus removing VMX and DFP instructions.
> >
> > Signed-off-by: Jake Moilanen <moilanen@austin.ibm.com>
> >
> > --- 2.6/arch/powerpc/kernel/prom_init.c~ 2006-11-13 15:01:13.000000000
> > -0600
> > +++ 2.6/arch/powerpc/kernel/prom_init.c 2006-11-21 18:38:27.000000000
> > -0600
> > @@ -627,6 +627,7 @@ static void __init early_cmdline_parse(v
> > /* Option vector 3: processor options supported */
> > #define OV3_FP 0x80 /* floating point */
> > #define OV3_VMX 0x40 /* VMX/Altivec */
> > +#define OV3_DFP 0x20 /* decimal floating point */
>
> Can we make the flag OV3_DECFP to distinguish it from Double FP.
One thing OV3_DFP has going for it is that is matches the nomenclature
used by GCC, binutils. I'm not sure what you mean by Double FP, unless
you're referring to the double wide FP unit on the Blue Gene/L 440
processor, but they don't refer to it as Double FP.
Peter
next prev parent reply other threads:[~2006-11-22 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 15:20 [PATCH] CAS DFP support Jake Moilanen
2006-11-22 15:25 ` Kumar Gala
2006-11-22 15:46 ` Kumar Gala
2006-11-22 15:58 ` Jake Moilanen
2006-11-22 16:06 ` Peter Bergner [this message]
2006-11-22 16:41 ` Kumar Gala
2006-11-22 18:36 ` Will Schmidt
2006-11-22 18:51 ` Kumar Gala
2006-11-23 14:39 ` Segher Boessenkool
2006-11-22 21:48 ` Paul Mackerras
2006-11-22 18:36 ` Will Schmidt
2006-11-22 21:45 ` Paul Mackerras
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=1164211565.4932.7.camel@otta \
--to=bergner@vnet.ibm.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).