linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Frank Bennett <bennett78@digis.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Video Card to Lite5200
Date: Wed, 07 Dec 2005 23:53:24 +0100	[thread overview]
Message-ID: <20051207225324.63BED352597@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 07 Dec 2005 14:23:10 MST." <439752BE.9030207@digis.net>

In message <439752BE.9030207@digis.net> you wrote:
>
> The denx.de web site looks great.

Thanks :-)

> Where can someone get this PCI card?  Do I have to contact Fujitsu 
> directly? Cost?

I guess you have to contact Fujitsu directly; we worked with  Fujitsu
Microelectronics Europe.

> The Fujitsu CoralP evaluation board MB86295EB01? or did you use the 

Yes.

> Coral PA?

No.

> I saw a posting that you also had some streaming video running.  Tell me 
> more.

See ftp://ftp.denx.de/pub/fujitsu/Coral-P/README.html

> What resolution? 4CIF (full DVD)
> What display?  LCD SVGA (800x600) and/or VGA analog port?

We used a 1024 x 768 LCD.

> Software MPEG decoder or does the Coral  have a decoder?

There was no decoder involved at all. The  CoralP  can  stream  video
directly,  without  any CPU load :-) We used the "zvideo" application
for demos - see above.

> Which player did you use?

None. Just a video source like a standard DVD player or a camera.

> Is all this covered in some release notes?

See the README.html

> Was the katix stuff ever integrated into linux_2_4_development?

Yes, it was. See the drivers/spi/ diretory in our  linuxppc_2_4_devel
tree, or
http://www.denx.de/cgi-bin/gitweb.cgi?p=linuxppc_2_4_devel.git;a=tree;h=464f005880de29947ee7d2d8941446c4ba76b0f8;hb=95300e1ab7d8a330784a882db868e355af6d638a;f=drivers/spi

> How does Wolfgang make a living if he spends all his time answering our 
> questions?

Dunno. Next question, please :-)


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Bradley's Bromide: If computers get too  powerful,  we  can  organize
them into a committee - that will do them in.

  reply	other threads:[~2005-12-07 22:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05 19:30 Video Card to Lite5200 Alan Carvalho
2005-12-05 20:35 ` Wolfgang Denk
2005-12-05 20:39   ` Alessandro Rubini
2005-12-07 17:23     ` roger blofeld
2005-12-07 18:53       ` Alan Carvalho
2005-12-07 19:51       ` Wolfgang Denk
2005-12-13 18:10         ` MPC5200 RTC bennett78
2006-06-30 23:16         ` Video Card to Lite5200 Benjamin Herrenschmidt
2006-07-01  9:15           ` Wolfgang Denk
2006-07-01  9:29             ` Benjamin Herrenschmidt
2005-12-08  0:25       ` Alessandro Rubini
2005-12-08  5:59       ` White
2005-12-08 23:10         ` Wolfgang Denk
2005-12-09 11:49           ` Andrey Volkov
2005-12-07 21:23   ` bennett78
2005-12-07 22:53     ` Wolfgang Denk [this message]
     [not found] <dc70db7d0512060906y7fa62c56q4c25dd5d92b2b2dd@mail.gmail.com>
     [not found] ` <20051206203343.67682353F5E@atlas.denx.de>
2005-12-08 13:18   ` Alan Carvalho
2005-12-08 23:14     ` Wolfgang Denk

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=20051207225324.63BED352597@atlas.denx.de \
    --to=wd@denx.de \
    --cc=bennett78@digis.net \
    --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).