From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Feature Freeze?
Date: 06 Mar 2003 09:18:07 +0800 [thread overview]
Message-ID: <1046913396.1227.176.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0303051829450.27760-100000@phoenix.infradead.org>
On Thu, 2003-03-06 at 02:34, James Simmons wrote:
>
> > > 1. Text mode support?
> >
> > Required by at least davem and petr
>
> Just Petr. I'm working to seperate the text code out into a matroxcon.c
> file. Needs alot more work tho.
>
> > > 2. console resizing using fbset (besides stty)?
> >
> > Nice, if it's not too much work.
>
> :-( I hope to improve fbcon to handle this.
>
If you're really against using fbset to resize the console, then the
first step is to protect the console from the "dangers" of fbset.
Secondly, we can have fbcon_resize() validate the mode instead of just
blindly calling fb_set_var(). If it's not valid, then it can also fetch
a working mode for it. The user can then fine tune the timings using
fbset afterwards.
So, do we allow fbcon to handle mode validating and fetching, or do we
just leave all this to fbdev? At least let's bring out some ideas on how
to go about doing this. Having a working idea, even if dumb, should
interest other developers in contributing.
Tony
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
next prev parent reply other threads:[~2003-03-06 1:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 8:26 Feature Freeze? Antonino Daplas
2003-03-05 9:57 ` Geert Uytterhoeven
2003-03-05 12:46 ` Antonino Daplas
2003-03-05 18:37 ` James Simmons
2003-03-06 1:17 ` Antonino Daplas
2003-03-11 15:55 ` James Simmons
2003-03-05 18:34 ` James Simmons
2003-03-05 18:45 ` Geert Uytterhoeven
2003-03-06 1:18 ` Antonino Daplas [this message]
2003-03-06 7:03 ` Carlo E. Prelz
2003-03-06 7:54 ` Antonino Daplas
2003-03-11 15:57 ` James Simmons
2003-03-05 11:05 ` Sven Luther
2003-03-05 12:46 ` Antonino Daplas
2003-03-05 13:43 ` Sven Luther
2003-03-05 14:04 ` Geert Uytterhoeven
2003-03-05 14:21 ` Sven Luther
2003-03-05 14:23 ` Geert Uytterhoeven
2003-03-05 14:26 ` Sven Luther
2003-03-05 14:46 ` Antonino Daplas
2003-03-05 14:49 ` Sven Luther
2003-03-05 15:25 ` Antonino Daplas
2003-03-05 18:55 ` James Simmons
2003-03-05 18:46 ` James Simmons
2003-03-05 18:52 ` James Simmons
2003-03-05 18:39 ` James Simmons
2003-03-05 18:36 ` James Simmons
2003-03-05 18:29 ` James Simmons
2003-03-06 1:18 ` Antonino Daplas
2003-03-11 16:06 ` James Simmons
[not found] <20030305211727.GA3839@g-kabel.si>
2003-03-05 23:59 ` James Simmons
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=1046913396.1227.176.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--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).