From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: adaplas@pol.net
Cc: Andrew Morton <akpm@osdl.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] fbdev: Add Tile Blitting support
Date: Fri, 10 Sep 2004 02:11:13 +0200 [thread overview]
Message-ID: <20040910001113.GA19132@vana.vc.cvut.cz> (raw)
In-Reply-To: <200409100534.56680.adaplas@hotpop.com>
On Fri, Sep 10, 2004 at 05:34:56AM +0800, Antonino A. Daplas wrote:
>
> In my case at least, the cleanup did produce an unexpected but beneficial
> side effect, a little more speedup. Not much, < 5%.
>
> Petr, if you have comments, suggestions, or you think this is a bad idea,
> let me know.
It looks like good idea to me. Though I still do not see benefits
2.6.x fbcon provides over 2.4.x.
BTW, there is still bad bug with software scrollback and multihead
(it is here since I remember): redraw_screen sets redraw to 0 when
old_console == new_console, but fbcon uses con_switch() method for
deciding whether software scrollback should be reinitialized or not.
As software scrollback is per-system and not per-fbdev thing, this
has rather nasty consequences - when both fbdevs have different xres,
console user can crash system (con2fb /dev/fb1 /dev/tty11; set xres
fb0 != xres fb1; chvt 11; chvt 10; chvt 11; hit alt-shift-pgup
or force vt11 to scroll; crash, some kernel data structures were
overwritten with 0x0720...).
Petr Vandrovec
next prev parent reply other threads:[~2004-09-10 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 21:34 [PATCH 7/7] fbdev: Add Tile Blitting support Antonino A. Daplas
2004-09-10 0:11 ` Petr Vandrovec [this message]
2004-09-10 0:47 ` Antonino A. Daplas
2004-09-10 7:58 ` Geert Uytterhoeven
2004-09-10 8:35 ` [Linux-fbdev-devel] " Antonino A. Daplas
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=20040910001113.GA19132@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--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;
as well as URLs for NNTP newsgroup(s).