--- what about the Cell Broadband Engine Family? IBM wants folks to sign on pretty badly. It may simplify getting the "processing power/ bandwidth" needed. I doubt it would make the design overly easy.

As far as I can tell, the CBE is hard to get a hold of, hard to work with, hard to power, etc. While it seems great, the problem is that we won't have the resources to build a board for one. Correct me if I am wrong - I would love to have a cheap, $150 dollar development platform with video out for the CBE now that Sony cut the $500 PS3. I am sure that others would also - heck, we could
probably even get a partnership with RapidMind or something!

--- There probably will be a market for H.264 and MPEG 4. Basicly you would be trying to enter the home entertainment pc market. With basic video card functions.

I think that video decoding is a must, including H.264 and MPEG4. Considering that this is supposed to be FOSS friendly, Ogg
Vorbis/Theora is probably a good idea.

Another question: Are we going to have a hard drive? SSD? Any form of storage to facilitate "media center" activity? This doesn't include
the boot flash, of couse.

I have a 32" Sony Trinitron from a few years back (I want to say 2002), and it has Component in - I doubt many people who would buy this would complain with just HDMI (which, with the adapter JRT mentioned, goes to S/P-DIF and DVI), Component, and RCA
audio.

--- Probably better think about DRM legalities.

If the silicon labs separate chip we discussed for ODG is available, they might be interested in our business. Then we *really*
don't have to worry about!

And as for the suggestion of using the Virtex II: that was my first thought. It seemed like the perfect solution, but then I realised they cost an arm and a leg (they are, IIRC, >$100 in 10000 qty). Not really an option if we want to keep this cheap.

Nicholas


_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)

Reply via email to