From: Wouter Cloetens <wouter@mind.be>
To: linuxppc-embedded@lists.linuxppc.org
Cc: v2p@mind.be
Subject: Re: [PATCH] Insight Memec Virtex-II Pro Development Board support
Date: Fri, 19 Dec 2003 16:31:00 +0100 [thread overview]
Message-ID: <20031219153100.GA15181@roadkill.intern.mind.be> (raw)
In-Reply-To: <20031212215601.GH3935@roadkill.intern.mind.be>
On Fri, Dec 12, 2003 at 10:56:01PM +0100, Wouter Cloetens wrote:
> Mind is making available a set of Linux kernel patches adding support for the Insight
> Memec Virtex-II Pro Development Board using Memec's reference design for Linux on
> ftp://ftp.mind.be/Virtex2Pro/patch-v2.4.23_linuxppc_2_4_devel/.
[...]
> The patches should be applied in the following order:
> ftp://ftp.mind.be/Virtex2Pro/patch-v2.4.23_linuxppc_2_4_devel/patch-platform-insightv2pro
> board-specific platform support
> patch for the 405D5X[12] CPU_212 bug (see http://support.xilinx.com/xlnx/xil_ans_display.jsp?iLanguageID=1&iCountryID=1&getPagePath=14052)
I've updated this file and patch-defconfig because:
- It's not actually the CPU_212 erratum, but the solution 12 one below.
I got confused by the layout. I've renamed the config option
accordingly.
- The problem is apparently only present on a small subset of
early-release Virtex-II Pros. So I've made the option configurable,
and disabled by default, instead of always enabling it for the
Memec board.
Sorry about that. I should've read the '4xx Ports' thread on this list
a few weeks ago that discussed the issue.
--
There are 10 types of people in the world: Those who understand binary, and those who don't.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-19 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 21:56 [PATCH] Insight Memec Virtex-II Pro Development Board support Wouter Cloetens
2003-12-19 15:31 ` Wouter Cloetens [this message]
2004-01-05 14:38 ` Wouter Cloetens
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=20031219153100.GA15181@roadkill.intern.mind.be \
--to=wouter@mind.be \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=v2p@mind.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.