From: "Grant Likely" <grant.likely@secretlab.ca>
To: schardt <g.schardt@fz-juelich.de>
Cc: Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: Newbie and linux on virtex-II ppc
Date: Tue, 28 Aug 2007 07:55:21 -0600 [thread overview]
Message-ID: <fa686aa40708280655mf0c08cct43eb9dbd75452690@mail.gmail.com> (raw)
In-Reply-To: <46D4257C.7060208@fz-juelich.de>
On 8/28/07, schardt <g.schardt@fz-juelich.de> wrote:
> Grant Likely wrote:
> > On 8/28/07, schardt <g.schardt@fz-juelich.de> wrote:
> >
> >> Grant Likely wrote:
> >>
> >>> You've got 2 choices:
> >>> 1. use the new sysace driver; it's already in mainline. The new
> >>> driver is faster, but it doesn't handle hotswap of the CF card (yet)
> >>>
> >>>
> >> But where in menuconfig could i find the sysace driver ? i'm blind, i
> >> think :)
> >>
> >
> > Which version of kernel are you using? The new sysace driver was
> > merged into 2.6.22
> >
> >
> linux-2.6.22.5
Should be under drivers->block devices then.
> >>> 2. use the EDK driver; easiest way is to use my tree which already hasGrant Likely <grant.likely@secretlab.ca>
> >>> it merged: http://git.secretlab.ca
> >>>
> >>>
> >>>
> >> i made an EDK update and now i have the linux_2_2 os in the software
> >> options. the bsp with all drivers is generated.
> >> and now ?
> >> - copy to kernel tree
> >> - use the xmake to build the kernel, or make ?
> >>
> > Grant Likely <grant.likely@secretlab.ca>
> > Don't use EDK to build you're kernel. It's too fragile and you need
> > to use the *exact* version of kernel that EDK expects. You're better
> > off to manually copy the xparams file from the generated BSP. (ie.
> > Don't let EDK know where your real kernel source tree is)
> >
> wuh ? i dont need all the driver from the generatet bsp files ? what
> about the gpios and leds ?
Most drivers are already in my tree; any that are missing you can copy
over manually.
> i compile the kernel with a self made cross toolchain, not with the edk.
> until now i copied the bsp files into the kernel tree (modfied some
> defines) und compile with "make zImage". But know with the linux_2_6
> option there is some more stuff in the bsp directory and i don't know
> what to do with :)
>
> >
> >> and why is there no dokumentation :)
> >
> > Care to write some?
> >
> huh, not really :)
> im just a little newbie
best way to learn. :-)
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-08-28 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 12:55 Newbie and linux on virtex-II ppc schardt
2007-08-27 13:09 ` Grant Likely
2007-08-27 14:17 ` schardt
2007-08-27 14:21 ` Grant Likely
2007-08-28 6:51 ` schardt
[not found] ` <46D2CFFB.6050602@fz-juelich.de>
[not found] ` <fa686aa40708270719s1fd230e9g188948ef02b3eda7@mail.gmail.com>
[not found] ` <46D41298.7060109@fz-juelich.de>
2007-08-28 13:06 ` Grant Likely
2007-08-28 13:24 ` schardt
2007-08-28 13:30 ` Grant Likely
2007-08-28 13:39 ` schardt
2007-08-28 13:55 ` Grant Likely [this message]
2007-08-28 14:12 ` schardt
2007-08-28 14:43 ` Grant Likely
2007-08-28 14:44 ` Grant Likely
2007-08-29 9:29 ` schardt
2007-08-29 13:31 ` schardt
2007-08-29 14:44 ` Grant Likely
[not found] ` <46DBA4F9.2010703@fz-juelich.de>
2007-09-03 13:41 ` Grant Likely
2007-08-27 13:54 ` Ming Liu
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=fa686aa40708280655mf0c08cct43eb9dbd75452690@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=g.schardt@fz-juelich.de \
--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).