From: Paul Mackerras <paulus@samba.org>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: hide CONFIG_ALTIVEC on iSeries
Date: Fri, 2 Dec 2005 09:25:36 +1100 [thread overview]
Message-ID: <17295.30816.292109.714074@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20051201204632.GA3764@suse.de>
Olaf Hering writes:
> Do not offer CONFIG_ALTIVEC for legacy iSeries. They predate the 970.
I am still hoping that we will get to the point of being able to build
a single binary kernel for both iSeries and the rest (pSeries, pmac,
etc.). If we put in this patch then we'll undoubtedly forget to take
it back out when we do get to the single binary kernel.
Does it cause any actual problem to have CONFIG_ALTIVEC offered on
legacy iSeries?
Paul.
next prev parent reply other threads:[~2005-12-01 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 20:46 [PATCH] powerpc: hide CONFIG_ALTIVEC on iSeries Olaf Hering
2005-12-01 22:25 ` Paul Mackerras [this message]
2005-12-01 22:28 ` Olaf Hering
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=17295.30816.292109.714074@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.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;
as well as URLs for NNTP newsgroup(s).