From: James S. <jsi...@ac...> - 2000-03-05 03:26:52
|
> but I do not see reason why I cannot move VC from one head to another. Why? > will run boxes in dangerous environment where you want strictly splitted > head0 user/resources/... from head1 user/resources. In most applications > you just have two keyboards and two monitors. And you want to > select two of your 64 VCs to be visible/controllable at one time... Withe fbdev in theory you can up to 256 displays. 64 isn't going to cut it. Also how do we split the 64 VC between 9 fbdev/keyboards. This is a odd number which we have to write special code for. > > I'm working on that now with the new fbdev API. > 'New fbdev API' does not look like backward compatibility stuff. Okay. Almost. > More I think about this, more I believe that we should split problems > on per-driver basis to userspace and kernel, and create userspace library > providing an industry interface (OpenGL(, DirectX) or ...). From what > I see graphics engines are way too different to put all emulation into > kernel (in other way, I do not believe in DRI future, unless it is more > powerfull than I think (I tried to get some info about that company > and their products after press release from Jan 12 that PI will write > Matrox drivers for Linux, but I failed... maybe I choosed wrong email)). Something is wrong. We agree about DRI. Don't feel bad. Most kernel developers that have sent them email seems to disappear into a black hole. So far I'm the only one they responded to. That's because they don't like me since i point out their design flaws. "Look its a text editor, not its a OS, no it Emacs" James Simmons ____/| fbdev/gfx developer \ o.O| http://www.linux-fbdev.org =(_)= http://linuxgfx.sourceforge.net U |