linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jake Moilanen <moilanen@austin.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH] CAS DFP support
Date: Wed, 22 Nov 2006 09:20:14 -0600	[thread overview]
Message-ID: <1164208814.1954.372.camel@goblue> (raw)

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 */
 
 /* Option vector 5: PAPR/OF options supported */
 #define OV5_LPAR		0x80	/* logical partitioning supported */
@@ -674,7 +675,7 @@ static unsigned char ibm_architecture_ve
 	/* option vector 3: processor options supported */
 	3 - 2,				/* length */
 	0,				/* don't ignore, don't halt */
-	OV3_FP | OV3_VMX,
+	OV3_FP | OV3_VMX | OV3_DFP,
 
 	/* option vector 4: IBM PAPR implementation */
 	2 - 2,				/* length */

             reply	other threads:[~2006-11-22 15:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 15:20 Jake Moilanen [this message]
2006-11-22 15:25 ` [PATCH] CAS DFP support Kumar Gala
2006-11-22 15:46 ` Kumar Gala
2006-11-22 15:58   ` Jake Moilanen
2006-11-22 16:06   ` Peter Bergner
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=1164208814.1954.372.camel@goblue \
    --to=moilanen@austin.ibm.com \
    --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).