|
From: Sven L. <lu...@dp...> - 2003-03-05 14:50:09
|
On Wed, Mar 05, 2003 at 10:46:37PM +0800, Antonino Daplas wrote: > > I thought that the new API, separating the fbcon layer from the fbdev > > drivers would add support for this more easily. I guess it would be easy > > for the Appian Jeronimo 2000 board, which has two permedia3 chips, and > > thus can be seen as two separate devices. Cards with two ramdacs per > > chip, like the G400, the later radeon's and most recent cards would need > > driver level support, that is understandable, but is all there for fbcon > > to take advantage of it ? What about multi-seat, with two full consoles, > > with mouse and keyboard for each ? > > > > This was one of the goals of the Ruby project, but I think it's mostly > the input layer that got into the kernel. :((( > Fbcon needs to be cleaned up, a lot. It still implements the "current > console or foreground console" concept (only one console active at a > time). Also, this is more of a job for linuxconsole than fbdev. I may > be wrong though. Mmm, do you know who is working on linuxconsole, and what their plan are ? > > > It does have one benefit though, the newer code should make it easier to > > > add an infrastructure on top of fbdev, such as xinerama-style support. > > > But this will be in the future. > > > > Mmm, I don't know if there is really a point to this, are there really > > all that much applications which do xinerama-like things on top of fbdev ? > > I rather thought that more higlevel userland apps would be doing this. > > like either xfree86 with chip-specific drivers or fbdev drivers, or > > directfb or something such. > > > > You're right, xinerama is mainly user-app. :))) Friendly, Sven Luther |