Ruby redux
Quoted 4 lines
as large console cleanups went into the -mm tree and those cleanups are also part of the Ruby tree, I thought I look at the Ruby tree and port it to 2.6.11-rc4 + the following 4 patches:
Yeap. I talked to Andrew Morton and Christoph Hellwig about the patches. The major difference is that struct vt_struct is removed completely. Chris told me we can add in struct vt_struct again at a later time. Well he actually ask me to rename it to something else. The big patch which is really nice is the killing off of the console macros. This is a good thing that I never got around to doing.
Quoted 4 lines
1. cleanup-vc-array-access.patch
2. remove-console_macrosh.patch
3. merge-vt_struct-into-vc_data.patch
4. merge-vt_struct-into-vc_data-fix.patch
As for merging the ruby tree. I would suggest we wait until after the summer OSL conference. The reason beinging is that alot of rework is going into the fbdev/drm layer. I have ask Jon Smirl to help him with the demo at the OSL conference on the next generation X server.
The next generation X server will be based totally on top of OpenGL using drm/fbdev. I'm going to be working with him to make sure that it supported full multihead support!!!!! We will not have to do anymore X server hacks. All the X Server hack on the PCI bus will go away. So we have alot of work ahead. I say by next year this time main stream linux will be multi-desktop ready.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Quoted 7 lines
The next generation X server will be based totally on top of OpenGL using drm/fbdev. I'm going to be working with him to make sure that it supported full multihead support!!!!! We will not have to do anymore X server hacks. All the X Server hack on the PCI bus will go away. So we have alot of work ahead. I say by next year this time main stream linux will be multi-desktop ready.
In fact, DRM handles hardware access arbitration. Wether it's 3D/GL/whatever depends on what userland client library is used.
For "legacy" cards, we can perfectly have a 2D driver using DRM to submit commands (or beeing allowed to mmap the registers the good old way eventually) and a server built on top of this (hint hint:
kdrive ? :)
The main ideas is to have a common mode setting and hw access arbitration (& command submiting, DMA/AGP management etc...) infrastructure that isn't in the server.
Wether you then use a 2D userland driver, a 3D userland driver, XGL on top of the later, or whatever else is pretty much irrelevant.
I may want to rework a bit of the fbdev mode setting API if I can find time to work on this. It needs some better ways to determine "related" framebuffers, trigger re-probe of outputs, play with the output mapping, and get hotplug events to userland. It also need to properly work with the DRM for access arbitration to the HW. There are a lot of issues to deal with before we can safely change modes on the fly while a 3D server is running, but we'll have to be capable of it ultimately.
Ben.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click