From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Patch: FW:Xilinx: BSP: Updated ML405 to match hardware used for testing
Date: Wed, 26 Mar 2008 07:01:16 -0600 [thread overview]
Message-ID: <fa686aa40803260601j6e7f507fpe4d31c7c462fce5e@mail.gmail.com> (raw)
In-Reply-To: <052801c88f37$3b51f7e0$ad289e86@LPSC0173W>
On Wed, Mar 26, 2008 at 5:47 AM, Guillaume Dargaud
<dargaud@lpsc.in2p3.fr> wrote:
> Hello all,
>
> I'm trying to get things up and running on a Xilinx Virtex-4 ml405 board,
> and as such I've been trying to figure out the following recent message to
> the list:
> http://patchwork.ozlabs.org/linuxppc/patch?person=1226&id=17037
>
> I don't understand what this patch applies to: it references files such as
> ml405_defconfig which are not part of the normal kernel tree and which I
> cannot find anywhere. Is there some other kind of patch that needs to apply
> first in order to get for instance CONFIG_XILINX_DRIVERS,
> CONFIG_XILINX_EMAC, etc...
>
> Thanks
It applies to Xilinx's git tree of the Linux kernel.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-03-26 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 11:47 Patch: FW:Xilinx: BSP: Updated ML405 to match hardware used for testing Guillaume Dargaud
2008-03-26 13:01 ` Grant Likely [this message]
2008-03-28 10:40 ` Patch: FW:Xilinx: BSP: Updated ML405 to match hardware used fortesting Guillaume Dargaud
2008-03-28 12:35 ` Patch: FW:Xilinx: BSP: Updated ML405 to match hardware usedfortesting Guillaume Dargaud
2008-03-28 16:06 ` Patch: FW:Xilinx: BSP: Updated ML405 to match hardwareusedfortesting Stephen Neuendorffer
2008-04-01 7:24 ` Patch: FW:Xilinx: BSP: Updated ML405 to matchhardwareusedfortesting Guillaume Dargaud
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=fa686aa40803260601j6e7f507fpe4d31c7c462fce5e@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dargaud@lpsc.in2p3.fr \
--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).