Hey Miah, On Wed, 2003-02-26 at 23:06, Miah Gregory wrote: > > Don't do that, it's evil. JPEG decompression shouldn't be done > > in-kernel. Use v4l2, identify as V4L2_PIX_FMT_JPEG and let userspace > > applications decode that. > Absolutely right, if you have v4l2 available. Unfortunately, if you want > to provide backwards compatibility, there are very few options available > to you. It's not feasible to change all the existing v4l applications to > support an unofficial 'this is jpeg' type. That's one of the very reasons > why there is a new v4l API being developed. > > We've had to do the above in the spca50x (spca50x.sourceforge.net) driver. > In summary, yes, it's evil. Yes, it should be done in userspace, but in > some situations, there is no realistic alternative. Isn't the fact that drivers provide backwards compatibility one of the very reason why application developers aren't in a hurry to provide v4l2 with proper JPEG decoding support in their applications? Applications are currently just slow in following these new things, unfortunately... So yeah, you have a point (unfortunately). Ronald -- Ronald Bultje <rbultje@xxxxxxxxxxxxxxxxxxx> Linux Video/Multimedia developer
