Re: [Linux-fbdev-devel] unified accerated interface

[Romain D. <do...@ir...>]

Geert Uytterhoeven wrote:

> Do you really have to implement the pixel-based functions for all possible
> values? E.g. for mfb, afb and ilbm it's quite complex, and the console driver
> doesn't really need it. That's why we have the support for width field for the
> cell-based operations.

None of those driver exist in Ruby ;-)

The idea is, the pixel-based functions are _required_ in Ruby. Either
the driver supply them, or there's some generic functions for
the most common pixel type.

The ioctls simply give access to these functions to userland apps. They
don't have to worry on specific hardware, they just say 'copy
area "width*height+sourceX+sourceY" to "destX,destY"', or
'fill area "w*h+x+y" with color C'.

If there's driver where pixel-based stuff is problematic, tell
James or Vojtech, as it might cause worse problems than userland
accelerated drawing...

-- 
DOLBEAU Romain               | l'histoire est entierement vraie, puisque
                             |     je l'ai imaginee d'un bout a l'autre
do...@ir...             |           -- Boris Vian