From: Stefan Bauer <stefan.bauer@cs.tu-chemnitz.de>
To: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Antonino Daplas <adaplas@pol.net>
Subject: Re: [PATCH] i810fb: Fix console switch regression
Date: Mon, 17 Mar 2008 09:20:32 +0100 [thread overview]
Message-ID: <200803170920.33626.stefan.bauer@cs.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0803162042460.7207@anakin>
Am Sonntag, 16. März 2008 20:48 schrieb Geert Uytterhoeven:
> On Sun, 16 Mar 2008, Stefan Bauer wrote:
> > --- linux-2.6/drivers/video/i810/i810_main.c.orig
> > +++ linux-2.6/drivers/video/i810/i810_main.c
> > @@ -1476,7 +1476,7 @@ static int i810fb_cursor(struct fb_info
> > struct i810fb_par *par = info->par;
> > u8 __iomem *mmio = par->mmio_start_virtual;
> >
> > - if (!(par->dev_flags & LOCKUP))
> > + if (!par->dev_flags & LOCKUP)
> > return -ENXIO;
>
> However, the original expression didn't make sense, as LOCKUP is 8 and
> !par->dev_flags is either 0 or 1, so `!par->dev_flags & LOCKUP' is
> always 0.
>
> I took a quick look at the usage of the LOCKUP flag. Apparently when a
> lock-up is detected, this flag is set, and the driver will fall back to
> software operations instead of hardware accelerated operations.
>
> Is it possible the intended code was
>
> if (par->dev_flags & LOCKUP)
> return -ENXIO;
>
> ?
Yes, IMO you are right. 4c7ffe0 ("fbdev: prevent drivers that have hardware
cursors from calling software cursor code") introduced the senseless code.
I'm going on testing today, but I think that's it.
Again, please CC me, thanks.
---
From: Stefan Bauer <stefan.bauer@cs.tu-chemnitz.de>
Since 4c7ffe0b9f7f40bd818fe3af51342f64c483908e ("fbdev: prevent drivers that
have hardware cursors from calling software cursor code") every call of
i810fb_cursor fails with -ENXIO because of a incorrect "!".
This hasn't striked until eaa0ff15c30dc9799eb4d12660edb73aeb6d32c5 ("fix !
versus & precedence in various places") surrounded the expression with
braces, so that the intended behavior was inverted. That caused 'pixel
waste' - the same line of multi-colored pixels repeated over the whole
screen - during console switch.
This switches back to the original pre-4c7ffe0 behavior.
Signed-off-by: Stefan Bauer <stefan.bauer@cs.tu-chemnitz.de>
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Antonino Daplas <adaplas@pol.net>
---
--- linux-2.6/drivers/video/i810/i810_main.c.orig
+++ linux-2.6/drivers/video/i810/i810_main.c
@@ -1476,7 +1476,7 @@ static int i810fb_cursor(struct fb_info
struct i810fb_par *par = info->par;
u8 __iomem *mmio = par->mmio_start_virtual;
- if (!(par->dev_flags & LOCKUP))
+ if (par->dev_flags & LOCKUP)
return -ENXIO;
if (cursor->image.width > 64 || cursor->image.height > 64)
next prev parent reply other threads:[~2008-03-17 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 18:42 Stefan Bauer
2008-03-16 19:48 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2008-03-17 8:20 ` Stefan Bauer [this message]
2008-03-17 15:41 ` Stefan Bauer
2008-03-18 3:48 ` Andrew Morton
2008-03-18 7:09 ` Stefan Bauer
2008-03-16 19:57 ` Henrique de Moraes Holschuh
2008-03-16 20:02 ` Henrique de Moraes Holschuh
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=200803170920.33626.stefan.bauer@cs.tu-chemnitz.de \
--to=stefan.bauer@cs.tu-chemnitz.de \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®