From: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
To: <linuxppc-dev@ozlabs.org>
Subject: Re: Patch: FW:Xilinx: BSP: Updated ML405 to match hardware usedfortesting
Date: Fri, 28 Mar 2008 13:35:04 +0100 [thread overview]
Message-ID: <068401c890d0$294e3e10$ad289e86@LPSC0173W> (raw)
In-Reply-To: 066b01c890c0$17d9a800$ad289e86@LPSC0173W
I should add that I've tried several things:
- compile the Xilinx kernel as indicated in my previous message.
- compile it with just the xparameters_ml*.h files added
- copy all the files from the BSP into the (Xilinx) kernel tree
- directly generate the BSP into the (Xilinx) kernel tree
For instance, the last one still gives me:
.config:117:warning: trying to assign nonexistent symbol WANT_EARLY_SERIAL
.config:122:warning: trying to assign nonexistent symbol BUBINGA
.config:123:warning: trying to assign nonexistent symbol CPCI405
.config:124:warning: trying to assign nonexistent symbol EP405
.config:127:warning: trying to assign nonexistent symbol SYCAMORE
.config:129:warning: trying to assign nonexistent symbol XILINX_ML300
.config:130:warning: trying to assign nonexistent symbol XILINX_XUPV2P
.config:131:warning: trying to assign nonexistent symbol XILINX_ML403
.config:132:warning: trying to assign nonexistent symbol XILINX_ML405
.config:133:warning: trying to assign nonexistent symbol XILINX_ML41x
.config:138:warning: trying to assign nonexistent symbol XILINX_EMBED_CONFIG
.config:139:warning: trying to assign nonexistent symbol EMBEDDEDBOOT
.config:140:warning: trying to assign nonexistent symbol PPC4xx_DMA
.config:142:warning: trying to assign nonexistent symbol UART0_TTYS0
.config:143:warning: trying to assign nonexistent symbol UART0_TTYS1
.config:149:warning: trying to assign nonexistent symbol PC_KEYBOARD
.config:759:warning: trying to assign nonexistent symbol SERIAL_TEXT_DEBUG
.config:772:warning: trying to assign nonexistent symbol XILINX_OCP
.config:773:warning: trying to assign nonexistent symbol XILINX_ML40x
Two more things:
$ make ARCH=ppc ml405_defconfig
cp .config
cp: missing destination file operand after `.config'
Try `cp --help' for more information.
make: *** [ml405_defconfig] Error 1
And on the page http://wiki.secretlab.ca/index.php/Linux_on_Xilinx_Virtex
which I've been studying closely, I also tried the Secret Lab repository:
$ git clone git://git.secretlab.ca/git/linux-2.6-virtex.git
Initialized empty Git repository in
/home/guinevere/buildroot/linux-2.6-virtex/.git/
fatal: The remote end hung up unexpectedly
fetch-pack from 'git://git.secretlab.ca/git/linux-2.6-virtex.git' failed.
--
Guillaume Dargaud
http://www.gdargaud.net/
next prev parent reply other threads:[~2008-03-28 12:35 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
2008-03-28 10:40 ` Patch: FW:Xilinx: BSP: Updated ML405 to match hardware used fortesting Guillaume Dargaud
2008-03-28 12:35 ` Guillaume Dargaud [this message]
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='068401c890d0$294e3e10$ad289e86@LPSC0173W' \
--to=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).