From: Antonino A. D. <ad...@ho...> - 2004-08-09 08:41:15
|
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 |