From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: John Zielinski <grim@undead.cc>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: console resize working
Date: Mon, 29 Dec 2003 18:04:34 +1100 [thread overview]
Message-ID: <1072681474.812.12.camel@gaston> (raw)
Hi !
I have console resize working properly finally (and not trashing
over memory like mad after I closed a bunch of races in the VT
code itself) in my tree.
Right now, that relies on the low-level fbdev doing some kind of
mode validation and implementing FB_ACTIVATE_FIND though. Sucks a
bit but I'll fix fbdev's. No other way to do that properly imho.
Only my new radeonfb implements that for now (and it's only tested
on flat panels so far, where I allow almost any mode when I have a
scaler).
Comments welcome.
Ben.
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next reply other threads:[~2003-12-29 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 7:04 Benjamin Herrenschmidt [this message]
2003-12-29 21:08 ` console resize working John Zielinski
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=1072681474.812.12.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=grim@undead.cc \
--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).