linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Woody <woody@suwalski.net>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, Jan Rinze <janrinze@home.nl>
Subject: Re: [PATCH] cyber2000fb.c: Fix 16bpp mode
Date: Thu, 8 Nov 2007 08:03:41 -0500	[thread overview]
Message-ID: <4733092D.3010104@suwalski.net> (raw)
In-Reply-To: <20071108082159.GB23626@deprecation.cyrius.com>

Martin Michlmayr wrote:
> Jan Rinze noticed that 16bpp screen mode is not working on Netwinder:
> "After some deduction it appeared that it was running in 24bpp instead
> of 16bpp. Found the bug: a missing 'break' statement at the end of a
> switch case.  After adding the break statement 16bpp works fine."
>
> Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
> Cc: Jan Rinze <janrinze@home.nl>
> Cc: Woody Suwalski <woody@suwalski.net>
>
> --- a/drivers/video/cyber2000fb.c
> +++ b/drivers/video/cyber2000fb.c
> @@ -874,6 +874,8 @@ static int cyber2000fb_set_par(struct fb_info *info)
>  		default:
>  			BUG();
>  		}
> +		break;
> +
>  	case 24:/* TRUECOLOUR, 16m */
>  		hw.co_pixfmt		= CO_PIXFMT_24BPP;
>  		hw.width		*= 3;
>
>   
Yes, with the above bug fix I have tested that 16-bit X fbdev works OK.
Woody


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  reply	other threads:[~2007-11-08 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000501c81e5e$c1334160$4399c420$@nl>
2007-11-08  8:22 ` [PATCH] cyber2000fb.c: Fix 16bpp mode Martin Michlmayr
2007-11-08 13:03   ` Woody [this message]
2007-11-10 16:52   ` Martin Michlmayr

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=4733092D.3010104@suwalski.net \
    --to=woody@suwalski.net \
    --cc=janrinze@home.nl \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=tbm@cyrius.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).