From: Aidan Williams <aidan@nicta•com.au>
To: Anantharaman Chetan-W16155 <Chetan.S.Anantharaman@motorola•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Linux 2.4 Kernel on Xilinx Virtex4 FX100's PPC
Date: Thu, 01 Jun 2006 08:22:29 +1000 [thread overview]
Message-ID: <447E1725.4010908@nicta.com.au> (raw)
In-Reply-To: <EDF27F298D4B03498AE0C249A941DFF803D6E6@de01exm68.ds.mot.com>
Anantharaman Chetan-W16155 wrote:
> Has anyone successfully ported a Linux 2.4 Kernel on a Xilinx Virtex-4
> FX series FPGA’s, PPC405 processor?
>
Yes, see
http://ozlabs.org/pipermail/linuxppc-embedded/2006-April/022583.html
Note that there are silicon bugs that prevent caches being used in some
chips.
> More specifically, the FX100 FPGA?
I don't have one of those, sorry.
- aidan
next prev parent reply other threads:[~2006-05-31 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 19:02 Linux 2.4 Kernel on Xilinx Virtex4 FX100's PPC Anantharaman Chetan-W16155
2006-05-31 19:35 ` Grant Likely
2006-05-31 21:47 ` Anantharaman Chetan-W16155
2006-05-31 22:33 ` Grant Likely
2006-06-01 16:59 ` Peter Ryser
2006-05-31 23:14 ` Anantharaman Chetan-W16155
2006-05-31 22:22 ` Aidan Williams [this message]
2006-06-01 17:05 ` Peter Ryser
2006-06-01 17:08 ` Grant Likely
2006-06-01 18:03 ` Peter Ryser
2006-06-12 16:57 ` Stephen Telfer
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=447E1725.4010908@nicta.com.au \
--to=aidan@nicta$(echo .)com.au \
--cc=Chetan.S.Anantharaman@motorola$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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