linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: adaplas@pol.net
Cc: adaplas@hotpop.com, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [RFC] Video Mode Handling
Date: Sun, 8 Aug 2004 23:04:12 -0700	[thread overview]
Message-ID: <20040808230412.6dc16bf4.akpm@osdl.org> (raw)
In-Reply-To: <200408090944.01414.adaplas@hotpop.com>

"Antonino A. Daplas" <adaplas@hotpop.com> wrote:
>
> Most fbdev developers are proposing to bring back the per-display var
>  structures to ease the difficulty of video mode handling.  This proposal
>  is countered by a few (notably James) in that it severely increases the 
>  memory footprint of the kernel.  

Surprised.

By how much does this increase the kernel's memory footprint?

And how much simpler would the code be if we were to bring back the
per-display var structures?

IOW: what's the tradeoff here?


-------------------------------------------------------
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

  parent reply	other threads:[~2004-08-09  6:06 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 [this message]
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
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=20040808230412.6dc16bf4.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --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).