Re: New API

[James S. <jsi...@tr...>]

>    *      Note: If screen is blanked, all other functions (setcolreg,
>    *      imageblit) may be still invoked, and must work. This needs
>    *      special care if you are blanking by programming DAC to all black.
> 
> or something like that.   

See other email.

> >  *      Returns negative errno on error, or zero on success.
> 
> If driver does not support specified powerdown mode, should it
> use nearest mode with greater power consumption, nearest mode with
> smaller power consumption, or should it report an error?

> ?   * If we have no hardware acceleration, we provide an unaccelerated
> ?   * functions in fbcon-cfb*.c modules. You can use these functions
> ?   * as fallbacks if hardware unsupported action is requested.

Yes this is the case. I have three different files each with a soft accel
for each possible accel function. The reason for breaking them up is
because in theory you could have a device with only fillrect support. Then
you can plug in the other two generic accel functions. As for non pack
pixel and non accelerated cards you have to provide your own functions.

> Move #endif up below xxxfb_init, as these macros works correctly
> when code is built into kernel, and we want to make sure that nobody
> will remove #ifdef MODULE when doing cleanup, as we still call
> init explicitly from global fb initialization. 

Done :-)