All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: fix typo in fb_videomode Array
Date: Mon, 18 May 2015 05:16:21 +0000	[thread overview]
Message-ID: <20150518050421.GA3906@sudip-PC> (raw)
In-Reply-To: <20150516193128.GA1534@x230-arch.Speedport_W_724V_01011602_00_001>

On Sat, May 16, 2015 at 09:31:28PM +0200, Michel von Czettritz wrote:
> It appears that 'FB_SYNC_HOR_HIGH_ACT' should be assined to 'sync'
> and 'FB_VMODE_NONINTERLACED' is a flag for 'vmode'.
> 
<snip>
> 
> diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
> index 77310ff..8ff29c6 100644
> --- a/drivers/staging/sm750fb/sm750.c
> +++ b/drivers/staging/sm750fb/sm750.c
> @@ -94,7 +94,8 @@ static const struct fb_videomode lynx750_ext[] = {
>  	 FB_VMODE_NONINTERLACED},
>  
>  	{NULL, 60, 1360, 768, 11804, 208, 64, 23, 1, 144, 3,
> -	 FB_SYNC_HOR_HIGH_ACT|FB_VMODE_NONINTERLACED},
> +	 FB_SYNC_HOR_HIGH_ACT,
> +	 FB_VMODE_NONINTERLACED},

good catch. But, see that all the entries are having:
        FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
        FB_VMODE_NONINTERLACED

this is the only entry with a different flag settings. moreover this
entry is for 1360x768@60 , see the next entry and that is also for
1360x768@60 with the correct flags. So my opinion this entry is wrong.

Send a patch instead to delete this entry and I can check that on the
hardware.

regards
sudip

	
>  
>  	/*	1360 x 768	[1.77083:1]	*/
>  	{NULL,  60, 1360, 768, 11804, 208,  64, 23, 1, 144, 3,
> -- 
> 2.3.7
> 

      reply	other threads:[~2015-05-18  5:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-16 19:31 [PATCH] staging: sm750fb: fix typo in fb_videomode Array Michel von Czettritz
2015-05-18  5:16 ` Sudip Mukherjee [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150518050421.GA3906@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.