David A Kondrad wrote:
> /*Flag that indicates whether any of the display is enabled or not*/
> int display_enable;
> } vpbe_dm_info_t;
>
> I have a lot of other things in my queue at the moment so I won't be able
> to make a patch for some time, but I hope this gives you enough info to
> track it down in the MV 2.6.10 kernel.
> I'm guessing that montavista changed or eliminated these structs to clean
> up and standardize the code (which is a common theme for the code that TI
> produced) so there's some investigation to be done.
Yes, the new driver is cleaner and has less features. DirectFB does not
really need FBIO_GET_TIMING, but these are needed for good support:
#define FBIO_ENABLE_DISABLE_WIN \
_IOW('F', 0x30, unsigned char)
#define FBIO_SET_BITMAP_BLEND_FACTOR \
_IOW('F', 0x31, sizeof(vpbe_bitmap_blend_params_t))
#define FBIO_ENABLE_DISABLE_ATTRIBUTE_WIN \
_IOW('F', 0x33, unsigned int)
#define FBIO_SETPOS \
_IOW('F', 0x49, u_int32_t)
Though I must say I'd love to see them go, replaced by one ioctl
setting the whole config with flags for indication of changed
entries.
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
