From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Chris Dumoulin" <cdumoulin@ics-ltd.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Moving from 2.4 to 2.6 kernel
Date: Thu, 4 May 2006 14:04:29 -0600 [thread overview]
Message-ID: <528646bc0605041304q695a183ao68a4720e974ad4f@mail.gmail.com> (raw)
In-Reply-To: <445A534D.8090800@ics-ltd.com>
On 5/4/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> I'm looking into getting a BDI 2000 so I can start stepping through and
> see what is going on.
>
> I looked at the ML300 and V2Pro code in the arch/ppc/platforms/4xx
> folder, but I did not use any of that in my code. It looks like this is
> intended to be used with the BSP that is generated by Xilinx Platform
> Studio. I've tried generating the BSP this way, but the generated code
> is obviously not a complete patch to port Linux to your hardware, and I
> figure that by the time I figure out what I do/don't have to add, I
> might as well write the whole thing by myself. Have you had success
> integrating the automatically generated BSP from Xilinx Platform Studio?
No; the stuff in 2.6 is not integrated w/ platform studio. (only 2.4
is). However, you do need to extract the xparameters.h file from the
platform studio BSP. You can generate a Linux BSP w/o actually
telling it where your Linux tree is. Once its generated; pull out
xparameters.h and drop it into arch/ppc/platforms/4xx/xparameters/ in
your source tree. Note: it's important that you generate a LINUX BSP;
not a 'standalone' bsp. If you don't, then you'll be missing a bunch
of #defines.
Let me say that once more for clarity: The only file you need from
platform studio is the generated xparameters.h
This will give you at the very least a serial port driver. Once your
booting with that, you can focus on other device drivers.
Trust me; this is the path of far less pain.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 399-0195
next prev parent reply other threads:[~2006-05-04 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 17:32 Moving from 2.4 to 2.6 kernel Chris Dumoulin
2006-05-04 18:11 ` Grant Likely
2006-05-04 19:04 ` Andy Gospodarek
2006-05-04 19:17 ` Chris Dumoulin
2006-05-04 20:04 ` Grant Likely [this message]
2006-05-05 13:39 ` Chris Dumoulin
2006-05-05 15:31 ` Grant Likely
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=528646bc0605041304q695a183ao68a4720e974ad4f@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=cdumoulin@ics-ltd.com \
--cc=linuxppc-embedded@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).