From: Philippe De Muyter <phdm@macqel.be>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: MPC8540 : What's "SPE used in kernel" ?
Date: Tue, 26 Feb 2008 11:34:28 +0100 [thread overview]
Message-ID: <20080226103428.GA2849@netgate.macqel> (raw)
In-Reply-To: <8B0E09C7-BA68-4994-9AB6-36F400F65832@kernel.crashing.org>
Hi Kumar,
On Tue, Feb 26, 2008 at 01:39:20AM -0600, Kumar Gala wrote:
>
> On Feb 23, 2008, at 4:25 AM, Johannes Berg wrote:
>
>>
>>> But as I said in the same mail, processes still dies unexpectedly.
>>
>> Yeah, no idea though. I guess you could try putting that into the
>> arch/ppc Makefile, but arch/ppc will be removed this year so you don't
>> want to rely on it.
>
> Its been removed (or will be for 2.6.25).
>
> What compiler version are you using?
a gcc-4.2.1 derivative from codesourcery (4.2-50) that I needed to compile
eglibc for e500 and that I tweaked to use it with CLFS and that I compiled
with --host=powerpc-linuxspe. I now noticed that it still generates
spe insn's even when given '-mno-spe'.
I am now busy to retest with a vanilla powerpc-linuxspe-gcc-4.2.2 and
that seems to work fine. I don't think, though, that it is able to compile
eglibc for e500.
Thanks for the attention, and sorry for the noise.
Philippe
next prev parent reply other threads:[~2008-02-26 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080221123534.GA17716@ingate.macqel>
2008-02-22 9:50 ` MPC8540 : What's "SPE used in kernel" ? Philippe De Muyter
2008-02-22 15:29 ` Johannes Berg
2008-02-22 18:33 ` Andy Fleming
2008-02-23 9:24 ` Philippe De Muyter
2008-02-23 9:51 ` Johannes Berg
2008-02-23 10:17 ` Philippe De Muyter
2008-02-23 10:25 ` Johannes Berg
2008-02-26 7:39 ` Kumar Gala
2008-02-26 10:34 ` Philippe De Muyter [this message]
2008-02-25 14:47 ` E500 linux : are the 64-bit GPRs context-switched ? Philippe De Muyter
2008-02-25 16:58 ` 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=20080226103428.GA2849@netgate.macqel \
--to=phdm@macqel.be \
--cc=galak@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--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).