From: Scott Wood <scottwood@freescale.com>
To: leroy christophe <christophe.leroy@c-s.fr>
Cc: LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: Patch "Convert some mftb/mftbu into mfspr" breaks MPC885
Date: Wed, 20 Nov 2013 10:57:20 -0600 [thread overview]
Message-ID: <1384966640.1403.421.camel@snotra.buserror.net> (raw)
In-Reply-To: <528C82D1.4090803@c-s.fr>
On Wed, 2013-11-20 at 10:37 +0100, leroy christophe wrote:
> Scott,
>
> The patch "Convert some mftb/mftbu into
> mfspr" (beb2dc0a7a84be003ce54e98b95d65cc66e6e536) breaks startup on
> MPC885.
>
> The CPU traps (SoftwareEmulation trap) at sched_clock() when trying to
> read TBU with mfspr.
>
> Reverting the patch solves the issue.
>
> What's the prefered way to fix this ?
I guess we need to add an ifdef.
-Scott
next prev parent reply other threads:[~2013-11-20 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 9:37 BUG: Patch "Convert some mftb/mftbu into mfspr" breaks MPC885 leroy christophe
2013-11-20 16:57 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 10:21 leroy christophe
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=1384966640.1403.421.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.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).