On 15/08/16 13:10, Vladimir Murzin wrote:
> Make vfb a bit more flexible in sense what it can represent and allow
> the end user to specify video mode parameters via newly introduced module
> option "mode". Since it is test module it is still up to the end user
> to make sure there is enough memory to satisfy video mode settings.
>
> Signed-off-by: Vladimir Murzin <vladimir.murzin@xxxxxxx>
> ---
> drivers/video/fbdev/vfb.c | 43 +++++++++++++++++++++----------------------
> 1 file changed, 21 insertions(+), 22 deletions(-)
>
> diff --git a/drivers/video/fbdev/vfb.c b/drivers/video/fbdev/vfb.c
> index e9ecae2..2645875 100644
> --- a/drivers/video/fbdev/vfb.c
> +++ b/drivers/video/fbdev/vfb.c
> @@ -37,6 +37,10 @@ static u_long videomemorysize = VIDEOMEMSIZE;
> module_param(videomemorysize, ulong, 0);
> MODULE_PARM_DESC(videomemorysize, "RAM available to frame buffer (in bytes)");
>
> +static char *mode_option = NULL;
> +module_param(mode_option, charp, 0);
> +MODULE_PARM_DESC(mode_option, "Preferred video mode (e.g. 640x480-8@60)");
> +
> /**********************************************************************
> *
> * Memory management
> @@ -86,26 +90,17 @@ static void rvfree(void *mem, unsigned long size)
> vfree(mem);
> }
>
> -static struct fb_var_screeninfo vfb_default = {
> +static struct fb_videomode vfb_default = {
I think this can be const.
Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature
