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: Mon, 5 Jan 2004 15:38:47 +0100 [thread overview]
Message-ID: <20040105143847.GE31876@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:
> If needed, we can also submit the diff against the linuxppc_2_4 tree.
That's available too now on ftp://ftp.mind.be/Virtex2Pro/patch-v2.4.23_linuxppc_2_4/.
One notable difference with the patch against the devel tree is that
I've applied a patch to allow the boot code to pick up the command line
from RedBoot (arch/ppc/boot/simple/misc-embedded.c).
> The patches should be applied in the following order:
See the README file in that directory.
> We commit to maintaining this port on an ongoing basis against the
> linuxppc_2_4 tree.
And that's still true. Would any of the committers be so kind as to
merge this into the linuxppc_2_4[_devel] trees? Or is there anything
else (besides posting the link to the patches here) we should do to get
this stuff in?
--
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/
prev parent reply other threads:[~2004-01-05 14:38 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
2004-01-05 14:38 ` Wouter Cloetens [this message]
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=20040105143847.GE31876@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).