> In short decoding these fourcc values with all their implicit assumptions > about offset, strides and whatnotelse will be one giant switch mess. Not > my idea of a nice kernel interface. Also practically guaranteed to result > in slightly different behaviour in each driver. So you'd rather make each applicationa author get it wrong individually and uniquely. That is a bigger mess by far. > In conclusion: Ditch the addfb2ioctl and just add a few more kms pixel > formats for the new packed yuv layouts that the snb+ sprite code needs. If you need a decoder for some hardware then fine, write one - share it with the v4l one and put it in a library drivers can call. However - user space is already working in fourcc, v4l has working fourcc and dumping the mess on the user isn't going to be a win. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
