linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: IngoM <ingo.maindorfer@ipm.fraunhofer.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [Virtex 4 PPC] Which Linux?
Date: Mon, 4 Feb 2008 08:32:13 -0700	[thread overview]
Message-ID: <fa686aa40802040732q62f67f1exd9ec41da1f08ff8f@mail.gmail.com> (raw)
In-Reply-To: <15268468.post@talk.nabble.com>

On 2/4/08, IngoM <ingo.maindorfer@ipm.fraunhofer.de> wrote:
>
> Hello,
>
> we develop a new laser-ranging-system and our hardware freaks have choosen
> the Virtex 4 FX 12 on the "AVNET FX12 Mini-Module". The system had to
> deliver the raw data via UDP (12 Mbyte/sec) and on TCP the processed data
> (about 6 Mbyte/sec). When you get the processed data via TCP then no data
> send by UDP.
>
> I'm confused by the following:
>
> 1) Hard-TEMAC vs. Soft-TEMAC.
> Avnet provide a demo for the module which using Soft-TEMAC. If I get it
> right this core has to be licenced. But when ther is a hard-TEMAC why pay
> for it?

Use the hard TEMAC.

> 2) Linux
> I'd like to build my kernel and filesystem myself. But which way to go?
> Using OE, buildroot, ELDK...
> Can you please provide some starting points for me?

I've got buildroot working; it's probably the simplest for building
from scratch.  ELDK works well too.

http://wiki.secretlab.ca/index.php/Linux_on_Xilinx_Virtex

>
> 3) Boot-Concept
> The Mini-Module had only 4MB Flash. Is this enough for a root-fs?

It's tight, but doable.  You kernel image will be somewhere around 1
to 1.5 MB.  Depends on how big your application is.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-02-04 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 13:54 [Virtex 4 PPC] Which Linux? IngoM
2008-02-04 15:32 ` Grant Likely [this message]
2008-02-05 14:58 ` Robert Schwebel
2008-02-06 14:51   ` IngoM
2008-02-06 19:29 ` Stephen Neuendorffer

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=fa686aa40802040732q62f67f1exd9ec41da1f08ff8f@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=ingo.maindorfer@ipm.fraunhofer.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).