From: Jerry Van Baren <gvb.linuxppc.dev@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] The MPC83xx family doesn't support performance monitor instructions
Date: Thu, 06 Mar 2008 19:51:37 -0500 [thread overview]
Message-ID: <47D09199.4090800@gmail.com> (raw)
In-Reply-To: <74F2472D-65F2-422B-821B-554EC81A3494@kernel.crashing.org>
Kumar Gala wrote:
> On Mar 5, 2008, at 6:33 PM, Gerald Van Baren wrote:
>
>> "Errata to MPC8349EA PowerQUICC[tm] II Pro Integrated Host Processor
>> Family
>> Reference Manual, Rev. 1" (Freescale)
>>
>> Signed-off-by: Gerald Van Baren <vanbaren@cideas.com>
>> ---
>>
>> Hi Kumar,
>>
>> Please apply this fix to 2.6.25rc4 if possible. Without this
>> patch, the PPC_83xx family configuration is broken (will not compile).
>
> What's the compile issue? Some of the 83xx family have perf mon so we
> need to fix the compile issue.
>
> - k
Hi Kumar,
The mpc8360 and mpc8349 do not have a perfmon register (I don't find it
at all in the MPC8360RM and the mpc8349 errata I referenced says the
MPC8349RM is in error).
The result is that the assembler dies with an error. If the assembler
didn't die with an error, I presume the kernel would since it is an
invalid SPR.
CC arch/powerpc/kernel/pmc.o
{standard input}: Assembler messages:
{standard input}:7: Error: Unrecognized opcode: `mfpmr'
{standard input}:11: Error: Unrecognized opcode: `mtpmr'
make[1]: *** [arch/powerpc/kernel/pmc.o] Error 1
make: *** [arch/powerpc/kernel] Error 2
This is using ELDK4.1 (also 4.2rc) using the ppc_6xx- version of the
compiler (which symlinks to powerpc-linux-gcc).
If some of the mpc83xx processors have perfmon registers, we need a more
granular way of selecting the CONFIG_FSL_EMB_PERFMON option (or a Plan
B, but I don't know what Plan B would be).
Best regards,
gvb
prev parent reply other threads:[~2008-03-07 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 0:33 [PATCH] The MPC83xx family doesn't support performance monitor instructions Gerald Van Baren
2008-03-06 14:07 ` Kumar Gala
2008-03-06 14:48 ` Realtime ethernet Mehlan, Markus (Ritter Elektronik)
2008-03-07 0:51 ` Jerry Van Baren [this message]
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=47D09199.4090800@gmail.com \
--to=gvb.linuxppc.dev@gmail.com \
--cc=galak@kernel.crashing.org \
--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).