On Wed, 23 Jan 2008 12:46:53 -0700
James Richard Tyrer <[EMAIL PROTECTED]> wrote:
> >>> BTW: What is a hardware motion compensation for you? I ask because
> >>> the process of motion compensation is something that looks always
> >>> very similar, no matter how much you do in hardware.
> >>>
> >> Hardware motion compensation would be motion compensation done (or
> >> partially done) by hardware dedicated to that use only.
> >
> > Uhm.. i dont want to be picky, but do you count a general purpose
> > CPU as an hardware motion compensation unit, if it is dedicated
> > for that use only?
>
> semantics issue. Dedicated hardware: Hardware that can only be used for
> a specific purpose. A general purpose CPU plus firmware is not what I
> would call dedicated hardware. Perhaps there is a better term for it,
> but can't think of one right now.
>
> For example: A general purpose CPU plus firmware can do color space
> conversion. But, you can also have dedicated hardware consisting of
> multipliers and adders that can only do that one thing.
My point here is that a motion compensation unit wouldnt look
too much different than a CPU, biggest difference would be
implizit parallelization and hardware aided resource
management, which on a CPU the software would need to do
completely itself.
Color space conversion (or a DCT) on the other hand is
something that has a total different layout if done in hardware.
The reason here is mostly that DCT and color space conversion
are a lot more computation intensive than data intensive,
while MC is mostly suffling around data with here and there
doing one simple arithmetic operation. Additionaly DCT and
CSC can be pipelined as the data flow is fixed, while MC
cannot be pipelined as data access is random.
Attila Kinali
--
Linux ist... wenn man einfache Dinge auch mit einer kryptischen
post-fix Sprache loesen kann
-- Daniel Hottinger
_______________________________________________
Open-hardware mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-hardware
