From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Eger <eger-dated-1080865620.ef4dea@theboonies.us>,
Jakub Jelinek <jj@ultra.linux.cz>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: scrollmode, accel_flags, fbcon.c ...
Date: Sat, 27 Mar 2004 01:42:48 +1100 [thread overview]
Message-ID: <1080312167.1390.19.camel@gaston> (raw)
In-Reply-To: <Pine.GSO.4.58.0403260802590.409@waterleaf.sonytel.be>
>
> These are hints for fbcon to use different types of scrolling. Using special
> hardware features is usually faster than doing dumb copies.
Yes, that all make sense, but there isn't a simple way for the fbdev
to set that now in 2.6 since it's in struct display which is now local
to fbcon. fbcon itself will initialize that to some value picked based
on the default var accel flags but I don't like that, espeically since
I think those flags should be deprecated.
> It is (was?) mainly a flag to indicate the fbdev uses and thus owns the accel
> engine. Userspace cannot mmap the MMIO registers and use the accel engine
> unless it first clears this flag. It can also be used just to disable the accel
> engine.
I know, I used them this way in 2.4, but with the 2.6 changes, they
becaome mostly unmanageable.
> These days it seems like vt_cons[vc->vc_num]->vc_mode == KD_TEXT seems to
> indicate the fbdev owns the accel engine, right James?
Yes.
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-26 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0403081323040.32244@rosencrantz.theboonies.us>
[not found] ` <Pine.GSO.4.58.0403091111540.26626@waterleaf.sonytel.be>
2004-03-26 0:14 ` scrollmode, accel_flags, fbcon.c David Eger
2004-03-26 2:21 ` Benjamin Herrenschmidt
2004-03-26 7:14 ` Geert Uytterhoeven
2004-03-26 14:42 ` Benjamin Herrenschmidt [this message]
2004-03-26 15:03 ` Geert Uytterhoeven
2004-03-27 1:24 ` Benjamin Herrenschmidt
2004-03-28 8:16 ` Geert Uytterhoeven
2004-03-29 17:50 ` James Simmons
2004-03-29 22:35 ` Benjamin Herrenschmidt
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=1080312167.1390.19.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=eger-dated-1080865620.ef4dea@theboonies.us \
--cc=geert@linux-m68k.org \
--cc=jj@ultra.linux.cz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).