linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: Mark Chambers <markc@mail.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Yosemite/440EP 'issues' as a PCI target
Date: Fri, 10 Feb 2006 10:19:04 -0800	[thread overview]
Message-ID: <43ECD918.1050202@ovro.caltech.edu> (raw)
In-Reply-To: <001701c62e6c$09c48ea0$6401a8c0@CHUCK2>

Hi Mark,

> Some unsolicited brainstorming

Brainstorm away!

> if you go with a QUICC based processor you could bring 
> the data into SDRAM via a serial port. That gets you DMA
> and some extra buffer management help from the co-processor.

Ooooh I like it.

> Some extra logic in the FPGA (but less pins), but you've got
> a lot of flexibility in what you can do with SCCs or I2C.

But do I have the bandwidth? (I'll look in the data book).

> I'm currently working on an MPC8247 based design, btw.
> It has a PC104+ header and is directly connected to a 
> T.I. 6205 (which, at $10, is a lot of crunch for the buck).

But the you have to program it with Code Composer and
the horrid TI DSP tools. Yeah, ok I've got the older
C31 version, not the newer 6x-based DSPs. I'm trying
to move the system to Linux, so that others round
here can 'share the burden'. I'm designing the boards,
drivers, and host software (ACE/C++) at the moment.
I need a break! :)

I want to avoid spending $20k on the TI tools and an
emulator ... hey, call me cheap.

However, I like the SCC idea. They sound very similar
to the multi-processor links on the Analog Devices
SHARC DSPs.

More reading :)

Dave

  parent reply	other threads:[~2006-02-10 18:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  9:35 Yosemite/440EP why are readl()/ioread32() setup to readlittle-endian? Jenkins, Clive
2006-02-02  9:46 ` Eugene Surovegin
2006-02-02 14:37   ` Matt Porter
2006-02-02 17:45     ` Eugene Surovegin
2006-02-02 18:16       ` Matt Porter
2006-02-05  4:41         ` Yosemite/440EP PLB4 vs PLB3 DMA to PCI issue David Hawkins
2006-02-05 10:39           ` Wolfgang Denk
2006-02-05 23:47             ` David Hawkins
2006-02-06 18:31               ` Stefan Roese
2006-02-06 19:09                 ` David Hawkins
2006-02-08 15:38                   ` Stefan Roese
2006-02-08 18:43                     ` David Hawkins
2006-02-09  0:34                       ` Wolfgang Denk
2006-02-09 13:25                         ` Mark Chambers
2006-02-09 23:58                         ` Yosemite/440EP 'issues' as a PCI target David Hawkins
2006-02-10  7:47                           ` Stefan Roese
2006-02-10 17:05                             ` David Hawkins
2006-02-10 17:20                               ` Andrew Armitage
2006-02-10 17:26                                 ` David Hawkins
2006-02-10 17:31                               ` Wolfgang Denk
2006-02-10 17:38                                 ` David Hawkins
2006-02-10 17:58                                   ` David Hawkins
2006-02-11  6:03                                 ` David Hawkins
2006-02-11  8:21                                   ` Stefan Roese
2006-02-11 18:15                                     ` David Hawkins
2006-02-11 13:03                                   ` Wolfgang Denk
2006-02-10 17:59                               ` Stefan Roese
2006-02-10 18:11                                 ` David Hawkins
2006-02-11  8:06                                   ` Stefan Roese
2006-02-11 18:06                                     ` David Hawkins
2006-02-11 19:00                                     ` David Hawkins
     [not found]                               ` <43ECCCA2.1070007@sandburst.com>
     [not found]                                 ` <43ECCE7A.4090507@ovro.caltech.edu>
     [not found]                                   ` <43ECD19E.8010604@sandburst.com>
2006-02-10 19:13                                     ` David Hawkins
     [not found]                               ` <001701c62e6c$09c48ea0$6401a8c0@CHUCK2>
2006-02-10 18:19                                 ` David Hawkins [this message]
2006-02-11  6:06                                 ` David Hawkins

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=43ECD918.1050202@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=markc@mail.com \
    /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).