RFC: MPEG encoding and decoding V4L2 API additions
- From: "Manu Abraham" <abraham.manu (at) gmail.com>
- Date: Sat, 17 Feb 2007 04:17:01 +0400
On 2/17/07, hermann pitton <hermann-pitton (at) arcor.de> wrote:
...
> >
> > For those without datasheets always accepted, but not for the others.
>
> Like ? What have datasheets got to do with API 's ? If API's are made
> out of datasheets, that's what happens (becomes hardware dependant)
Let me know when there is a most advanced _manu_ chip ...
An API (Application Programmer interface) is an interface to the user.
If this interface is hardware specific, probably if you understand, i
don't have to complete the rest.
The user need not know the specifics of the hardware, just needs to
have a convenient way of handling it in a generic way. When you tie
the API to a specific hardware, it ceases to become generic.
This explains the basic reason why API 's are based on technical
specifications rather than device specific implementations. (broken
are such device specific implementations)
Hermann
HTH
Manu
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list