> People are going in > circles, discussing high-level things like which video formats to > decode and which video formats to output. > > You're putting the cart before the horse.
Not at all. There are two ways to approach it: 1) I have this hardware thingy, what can I get it to do? 2) I need a box that does foo, what do I need inside the box? Both ways are perfectly valid. In practice, we usually tend to do a bit of both in parallel. I'm approaching this mainly via path 2. Make a list of required and desired features, then look at ways to build something that does it. > - Let's assume PCIe 1x (the answer to the alternatives is basically > the same). How are you going to connect that to a processing element? I'm assuming Ethernet. The TI DSP chips have Ethernet builtin, so connecting it to the processing element is already done. The problem is that the currently available TI DSP chips aren't fast enough. Maybe TI will come out with a faster chip, maybe not. In the meantime, we need to look for other solutions. They may or may not have Ethernet builtin. > - What kind of processing element are you going to use for basic > graphics stuff? (DSP? something else?) If we can find a suitable DSP, it should be able to handle basic graphics stuff. If we find a suitable hardware video decoder, we will likely require something else. We will probably need some sort of CPU/DSP anyway. > - What kind of processing is your primary focus? Graphics rendering? > 2D? 3D? Video decoding? My primary focus is video decoding. If we can also do things like CAD and google earth, that would be great. > - How are you going to handle things like graphics memory? That is, > how is the processing element connected to the memory? Assuming we use an existing CPU/DSP chip, look at the data sheet. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
