From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
To: "Jacob Holladay Poteet" <txtbox@gmail.com>, <linuxppc-dev@ozlabs.org>
Subject: RE: Making the Kernel
Date: Mon, 9 Jun 2008 13:22:30 -0700 [thread overview]
Message-ID: <20080609202244.6B58C2B8052@mail130-sin.bigfish.com> (raw)
In-Reply-To: <1213042163.7776.4.camel@Phoebe>
The kernel at git.xilinx.com has a rule to make zImage.virtex. Note
that this elf file will almost certainly *not* fit in blockram, hence
you can't use it to 'make a bitstream'. You can use it to generate a
SystemAce file, however.
If you are using a current mainline kernel, then you need to make a
simpleImage, which requires having a dts file that starts with the
'virtex-' prefix.
Steve
> -----Original Message-----
> From: linuxppc-dev-bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org
[mailto:linuxppc-dev-
> bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org] On Behalf Of Jacob
Holladay Poteet
> Sent: Monday, June 09, 2008 1:09 PM
> To: linuxppc-dev@ozlabs.org
> Subject: Making the Kernel
> =
> Good Afternoon,
> =
> I've gone through the process of configuring a kernel for my Xilinx
> board design using the mhs->devtree, dts+'make menuconfig'
> options->'make all' process and things seem to have succeeded. I was
> under the expectation that I would find a file
> arch/powerpc/boot/zImage.virtex, which is a type of .elf file that I
can
> use to make a bitstream, but I didn't find this said file in the
output.
> I found several zImage files (zImage,
> zImage.pmac,.miboot,.chrp,.lds,.cofflds), but none of them had the
> desired '.virtex' extension. Am I looking for something that doesn't
> exist? If not, can someone help me generate the necessary file?
> =
> This is my first time through this process so I appreciate your
advice.
> =
> Sincerely,
> Jake Poteet
> =
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
This email and any attachments are intended for the sole use of the named r=
ecipient(s) and contain(s) confidential information that may be proprietary=
, privileged or copyrighted under applicable law. If you are not the intend=
ed recipient, do not read, copy, or forward this email message or any attac=
hments. Delete this email message and any attachments immediately.
prev parent reply other threads:[~2008-06-09 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 20:09 Making the Kernel Jacob Holladay Poteet
2008-06-09 20:22 ` Stephen Neuendorffer [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=20080609202244.6B58C2B8052@mail130-sin.bigfish.com \
--to=stephen.neuendorffer@xilinx.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=txtbox@gmail.com \
/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).