From: Andrei Konovalov <akonovalov@ru.mvista.com>
To: Trevor Barton <tmb@isotek.co.uk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Arch: powerpc or ppc?
Date: Thu, 22 Mar 2007 15:34:38 +0300 [thread overview]
Message-ID: <460277DE.8080808@ru.mvista.com> (raw)
In-Reply-To: <4602578C.4010401@isotek.co.uk>
Hi Trevor,
There is (minimalistic) support for Xilinx Virtex 4 under ppc.
Unless you plan to move those chips to powerpc by yourself,
you should use ppc.
Thanks,
Andrei
Trevor Barton wrote:
> I've just started bringing Linux up on a Xilinx Virtex 4 FPGA with a
> PPC405 core. I'm using 2.6.15, and a crosstools-built toolchain from an
> x86 running Linux. The choice of kernel version was because crosstools
> identified it as a working combination and I can see no reason to choose
> anything different at the moment.
>
> I'm a bit confused about the difference between the ppc and powerpc
> architecture trees in the kernel. I've been using the ppc tree because
> that seems to have the requisite sources in it (I'm basing it on the
> ML300 code which seems to be the thing to do), and also because that was
> the only powerpc-related tree in earlier kernels. I can't seem to find
> any documentation as to where the powerpc tree appeared from and why.
>
> Can anyone confirm that I should still be using the ppc tree? Or even
> better, point me to some documentation regarding them both?
>
> Actually, while I'm at it, pointers to anything useful regarding the 2.6
> kernel and the Virtex 4 would be helpful. I've found a reasonable
> amount of stuff myself, but as these things usually go I'll only find
> the best documentation after I've solved the problems myself and
> therefore know what I'm looking for!
>
> Thanks in advance,
> Trevor Barton
>
prev parent reply other threads:[~2007-03-22 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 10:16 Arch: powerpc or ppc? Trevor Barton
2007-03-22 12:34 ` Andrei Konovalov [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=460277DE.8080808@ru.mvista.com \
--to=akonovalov@ru.mvista.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tmb@isotek.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.