From: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
To: <linuxppc-dev@ozlabs.org>
Subject: Re: Patch: FW:Xilinx: BSP: Updated ML405 to matchhardwareusedfortesting
Date: Tue, 1 Apr 2008 09:24:37 +0200 [thread overview]
Message-ID: <093b01c893c9$758b1d60$f52f9e86@LPSC0173W> (raw)
In-Reply-To: 20080328160614.6018DF68050@mail116-sin.bigfish.com
>> 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
>
> This should work.
It doesn't... Which makes me wonder if my problem may be with the boot
itself.
Once I have my zImage properly (?) compiled, I create an ACE file thus:
$ xmd -tcl genace.tcl -jprog -board ml405 -target ppc_hw -hw system.bit -elf
zImage -ace Kernel26.ace
But then nothing happens when I boot with it.
[...]
>> .config:773:warning: trying to assign nonexistent symbol XILINX_ML40x
>
> Did you check out the head of the tree?
You mean svn head ? Yes.
Something escapes me here. I pull the complete kernel git tree from Xilinx
and
when I menuconfig it, it removes the Xilinx additions ('nonexistent symbol
')...
I'm not very knowledgeable of the kernel organization, so I don't know what
this means, but I imagine there's a relation between 'XILINX_ML40x=y' in
.config, Kconfig which holds the help text and the .h/.c driver files
themselves. How can I check that the whole package is sane ?
>> 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
>
> I'd suggest starting over with a fresh tree.
> 1) Copy the xparameters file, overwriting the appropriate xparameters
> file in the git tree.
> 2) make ARCH=ppc ml405_defconfig
> 3) make ARCH=ppc all
One detail, I'm not doing 'make' from the kernel directory, but from the
buildroot directory, this way I'm sure it's compiled with the appropriate
cross-compiler and environment. Maybe targets such as ml405_defconfig are
not transmitted properly from one make to the other. Anyone who knows
buildroot care to
comment on that ?
--
Guillaume Dargaud
http://www.gdargaud.net/
prev parent reply other threads:[~2008-04-01 7:24 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 ` 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 ` Guillaume Dargaud [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='093b01c893c9$758b1d60$f52f9e86@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).