> The reason why there is no single 'format conversion library' thatAgreed. What I think it should happen is that the userspace library should focus at the "weird" codecs. E. g. those which uses some sort of proprietary format. This way, an userspace app may use the userspace library as a "fallback method" for unknown FOURCC formats. The result will be probably far away from an optimal result on some cases (since it probably mean double buffering), but this will at least allow userspace apps to work. As performance become an issue, the userspace app developer may use the GPL code at userspace API as a reference to write a proper optimized format driver for its apps. Just my 2 cents. Cheers, Mauro -
| Theodore Tso | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 011/196] sysfs: Fix a copy-n-paste typo in comment |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
