From: Wouter Cloetens <wouter@mind.be>
To: linuxppc-embedded@lists.linuxppc.org
Cc: v2p@mind.be
Subject: [PATCH] Insight Memec Virtex-II Pro Development Board support
Date: Fri, 12 Dec 2003 22:56:01 +0100 [thread overview]
Message-ID: <20031212215601.GH3935@roadkill.intern.mind.be> (raw)
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/.
This version of the patches is against kernel version 2.4.23 in the
linuxppc_2_4_devel tree, BitKeeper tag v2.4.23_linuxppc_2_4_devel.
If needed, we can also submit the diff against the linuxppc_2_4 tree.
We commit to maintaining this port on an ongoing basis against the
linuxppc_2_4 tree.
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)
ftp://ftp.mind.be/Virtex2Pro/patch-v2.4.23_linuxppc_2_4_devel/patch-uartlite
Xilinx UART Lite support (not board-specific)
ftp://ftp.mind.be/Virtex2Pro/patch-v2.4.23_linuxppc_2_4_devel/patch-memec-emac
MemecCore Ethernet MAC support (not board-specific)
ftp://ftp.mind.be/Virtex2Pro/patch-v2.4.23_linuxppc_2_4_devel/patch-mtd
MTD support for the NOR flash on the P160 comm module
ftp://ftp.mind.be/Virtex2Pro/patch-v2.4.23_linuxppc_2_4_devel/patch-defconfig
board default configuration
--
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 reply other threads:[~2003-12-12 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 21:56 Wouter Cloetens [this message]
2003-12-19 15:31 ` [PATCH] Insight Memec Virtex-II Pro Development Board support Wouter Cloetens
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=20031212215601.GH3935@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 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).