From: Sean MacLennan <smaclennan@pikatech.com>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] 4xx: Workaround for CHIP_11 Errata
Date: Thu, 15 May 2008 16:31:04 -0400 [thread overview]
Message-ID: <20080515163104.18f0a613@lappy.seanm.ca> (raw)
In-Reply-To: <20080515094346.3338e1f3@zod.rchland.ibm.com>
On Thu, 15 May 2008 09:43:46 -0500
"Josh Boyer" <jwboyer@linux.vnet.ibm.com> wrote:
> This implements the recommended workaround for this errata for chips
> that use older versions of firmware that do not already handle it.
> The last 4KiB of memory are hidden from the kernel to prevent the
> problem transactions from occurring.
Do you know which versions of firmware have this problem?
Cheers,
Sean
next prev parent reply other threads:[~2008-05-15 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:43 [PATCH] 4xx: Workaround for CHIP_11 Errata Josh Boyer
2008-05-15 15:16 ` Stefan Roese
2008-05-15 20:31 ` Sean MacLennan [this message]
2008-05-15 21:07 ` Josh Boyer
2008-05-16 4:57 ` Stefan Roese
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=20080515163104.18f0a613@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=jwboyer@linux.vnet.ibm.com \
--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).