public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Federico Lucifredi <flucifredi@acm•org>
To: "Bora Þahin" <bora.sahin@ttnet•net.tr>,
	"Linux-ppc [mailing list]" <linuxppc-embedded@ozlabs•org>
Subject: Re: MPC8272ADS and frame buffer
Date: Fri, 28 Jan 2005 12:31:47 -0500	[thread overview]
Message-ID: <41FA7703.20304@acm.org> (raw)
In-Reply-To: <551817263.20050128123639@ttnet.net.tr>

Bora Þahin wrote:

>Hi Federico,
>
>FL> I meant that you have to stress-test the bus connection that you are
>FL> going to use to whatever graphic hardware you
>FL> select - you cannot count on embedded hardware being bleeding-edge 
>FL> performance, and you are going to play 25 or 30 frames a second over 
>FL> that bus -- it is a lot of data, and you have bandwidth (hopefully not a 
>FL> problem with pci) and jitter (delay variance) constraints.
>
>Sory for the late answer...
>
>I see you. In fact I know it but some blurry situations is matter. We use IBM-PPC. It has
>CoreConnect bus. I dont know implementation details of it but it has three different buses. One is
>PLB. This is for speedy ones. PCI bridge is in this bus also. AFAIK, data and addres bus of it is
>decoupled. Clock speed is also high. I think it also support burst mode. So in the light of these
>infos it seems enough. So PCI is enough, this one sholud be enough also.
>
>But as you said, we should take into consideration that these cpus and buses are embedded and at
>some points, may have clipped version of desktop brothers.
>
>  
>
Exactly. And even when the cpu is not clipped, the board might be (I am 
handling right now a fully complete Motorola MPC8272 based design, the 
chip supports PCI burst, the board design, however, does not).

-Federico

-- 
_________________________________________
-- "'Problem' is a bleak word for challenge" - Richard Fish

Muad'Dib of Caladan (Federico L. Lucifredi)- Harvard University & BU
http://metcs.bu.edu/~lucifred

  parent reply	other threads:[~2005-01-28 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 20:55 MPC8272ADS and frame buffer Federico Lucifredi
     [not found] ` <3535657973.20050126204614@ttnet.net.tr>
     [not found]   ` <41F816F6.8090204@acm.org>
     [not found]     ` <371777686.20050127005702@ttnet.net.tr>
2005-01-26 23:34       ` Federico Lucifredi
     [not found]         ` <396073913.20050127020839@ttnet.net.tr>
2005-01-27  0:20           ` Federico Lucifredi
     [not found]             ` <551817263.20050128123639@ttnet.net.tr>
2005-01-28 17:31               ` Federico Lucifredi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-26 23:30 Federico Lucifredi
2004-12-08  0:49 Federico Lucifredi

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=41FA7703.20304@acm.org \
    --to=flucifredi@acm$(echo .)org \
    --cc=bora.sahin@ttnet$(echo .)net.tr \
    --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