From: Wolfgang Denk <wd@denx.de>
To: Joakim.Tjernlund@lumentis.se
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: CPU15 errata workaround for 8xx by WD
Date: Sun, 13 Feb 2005 21:08:42 +0100 [thread overview]
Message-ID: <20050213200847.1AE42C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sun, 02 Jan 2005 15:12:01 +0100." <BCEFJBPJCGFCNMMMIDBHOEPBCJAA.Joakim.Tjernlund@lumentis.se>
Dear Jocke,
sorry for the late reply.
In message <BCEFJBPJCGFCNMMMIDBHOEPBCJAA.Joakim.Tjernlund@lumentis.se> you wrote:
>
> Had a look at your CPU15 errata workaround for 8xx and I have a comment
> or two:
>
> 1) I think you should make the sysctl support a compile time option
> as the overhead for sysctl support in the TLB handler is 6 instr. when
> the fix itself is only 4 instr.
You are right.
> 2) You placed the workaround in the middle of the CPU6 workaround which will
> disable the CPU6 workaround(I think). Move it before the #ifdef CONFIG_8xx_CPU6
> and you should be fine.
You are right again - we fixed this in our CVS tree now.
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 22 - 24, Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The management question ... is not _whether_ to build a pilot system
and throw it away. You _will_ do that. The only question is whether
to plan in advance to build a throwaway, or to promise to deliver the
throwaway to customers. - Fred Brooks, "The Mythical Man Month"
next prev parent reply other threads:[~2005-02-13 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 14:12 CPU15 errata workaround for 8xx by WD Joakim Tjernlund
2005-01-02 20:54 ` Wolfgang Denk
2005-01-02 21:58 ` Joakim Tjernlund
2005-02-13 20:08 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 17:07 Wrobel Heinz-r39252
2005-01-04 18:26 ` Joakim Tjernlund
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=20050213200847.1AE42C1430@atlas.denx.de \
--to=wd@denx.de \
--cc=Joakim.Tjernlund@lumentis.se \
--cc=linuxppc-embedded@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).