On Monday 09 August 2004 16:03, Andrew Morton wrote:

quoted

  - 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