From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Andrew Morton <akpm@osdl.org>, Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [RFC] Video Mode Handling
Date: Mon, 9 Aug 2004 16:41:00 +0800 [thread overview]
Message-ID: <200408091641.00570.adaplas@hotpop.com> (raw)
In-Reply-To: <20040809010326.305620a7.akpm@osdl.org>
On Monday 09 August 2004 16:03, Andrew Morton wrote:
> > - private modedb:
> > - increase memory footprint by full mode database per driver.
> > - more complex (and larger) code
> > - subtle differences with 2.4, because not the whole var is saved
> > (BTW, which fields do you want to save, and which not, so I can
> > evaluate the impact on some drivers?)
>
> Well gee. If we're talking about 3k, or even 10k or 30k, let's go with the
> simplest code?
>
The simplest code is adding per-display var and removing stty/resize support.
If stty/resize support is needed, then we need a per-driver mode database.
Using fb_find_mode() + default modedb is no guarantee.
Best to wait for the other developers to respond.
Tony
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-08-09 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 1:43 [RFC] Video Mode Handling Antonino A. Daplas
2004-08-09 3:50 ` Jon Smirl
2004-08-09 7:59 ` Antonino A. Daplas
2004-08-09 14:56 ` Jon Smirl
2004-08-09 6:04 ` Andrew Morton
2004-08-09 7:23 ` Geert Uytterhoeven
2004-08-09 8:03 ` Andrew Morton
2004-08-09 8:10 ` Geert Uytterhoeven
2004-08-09 8:41 ` Antonino A. Daplas [this message]
2004-08-09 8:26 ` Antonino A. Daplas
2004-08-09 7:59 ` Antonino A. Daplas
2004-08-09 8:08 ` Geert Uytterhoeven
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=200408091641.00570.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.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).