Karmic

Differences between revisions 2 and 3
Revision 2 as of 2009-05-07 00:14:40
Size: 765
Editor: pool-71-117-254-52
Comment:
Revision 3 as of 2009-05-26 08:50:08
Size: 3514
Editor: 80
Comment:
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
{{{
- Bryce: disable KMS, enable on per-model testing
- Pitti, Scott: enable KMS by default, disable on per-model testing -> more testing
Line 31: Line 34:
We'll have a first public session on this on Tuesday at the Karmic UDS in Spain. - there is a kernel option to disable KMS globally, for a fallback

- don't move drivers into initramfs, Scott says that the boot will be fast enough to justify having a black screen until the driver gets loaded by udev

- usplash and fsck integration costs some 2 seconds of boot speed

- move usplash startup after video driver loading after enabling KMS by default

- select X.org server version for Karmic:
 * upstream release dates cannot be predicted
   (plan: http://lists.x.org/archives/xorg-devel/2009-April/000774.html)
 * current Karmic plan: 1.7
   this would bring libxi 2.0, inputproto 2.0, evdev 2.3(ish)
 
- intel driver version:
  * 2.7.1 in karmic, planned to upload 2.7.99 next week
  * 2.9 will disable non-KMS support
  * beyond 2.9, no big changes planned
  * current Karmic target: 2.8, with possibility of 2.9

- nouveau driver needs testing, easy to install (packaged for jaunty)

- nouveau needs kernel portion in drm linux branches, for KMS

- GEM: graphics memory manager geared for integrated chipsets like intel and via
- TTM: graphics memory manager, similar to GEM, but geared towards discrete graphics cards with VRAM (confirm!)

- Intel 8xx support:
  * no upstream interest in support/bug fixing
  * Jesse says that for 810/815 you have to run the old -810 driver; with some hammering it should build
  * 830 and up are tested by upstream; recent kernel patch fixed a lot of 8xx issues
  * tutorials available? not really

- https://launchpad.net/~xorg-edgers/+archive/ppa has latest versions for testing
- https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/ (more stable bits for jaunty, i.e. upstream bugfix releases)

- when 2.6.31 comes up, kernel side will be in better shape than the user land drivers

- intel-gpu-tools available in PPA, needs to be uploaded to karmic proper
- when intel driver runs into a GPU lockup, it's possible to capture a batch buffer dump using:
  https://launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test
  (upstream says they are working on code that will automatically reset the GPU
   when it locks up. In an ideal world the user might not even notice the lockup)

- Tagging intel and ATI bugs in LP: both with chipset and symptom tags
  There is a wiki page with all the tags listed.

- We need a platform for testing (defined set of functionality that we want
  working on a defined set of cards). We can use this to measure the quality
  of the release. The list of certified hardware for example.
  Apple has limited/bounded set of hardware and MS has the Windows logo program.

- Is there a way to get a list of the most common hardware out there?
}}}

Summary

This specification will provide a roadmap of X.org changes for Karmic, as well as a compatibility requirements listing of versions of dependencies we will want our video drivers to support.

Design

Summary

Rationale

Scope and Use Cases

Use Cases

Implementation Plan

Implementation

Outstanding Issues

BoF agenda and discussion

- Bryce: disable KMS, enable on per-model testing
- Pitti, Scott: enable KMS by default, disable on per-model testing -> more testing

- there is a kernel option to disable KMS globally, for a fallback

- don't move drivers into initramfs, Scott says that the boot will be fast enough to justify having a black screen until the driver gets loaded by udev

- usplash and fsck integration costs some 2 seconds of boot speed

- move usplash startup after video driver loading after enabling KMS by default

- select X.org server version for Karmic:
 * upstream release dates cannot be predicted
   (plan: http://lists.x.org/archives/xorg-devel/2009-April/000774.html)
 * current Karmic plan: 1.7
   this would bring libxi 2.0, inputproto 2.0, evdev 2.3(ish)
 
- intel driver version:
  * 2.7.1 in karmic, planned to upload 2.7.99 next week
  * 2.9 will disable non-KMS support
  * beyond 2.9, no big changes planned
  * current Karmic target: 2.8, with possibility of 2.9

- nouveau driver needs testing, easy to install (packaged for jaunty)

- nouveau needs kernel portion in drm linux branches, for KMS

- GEM: graphics memory manager geared for integrated chipsets like intel and via
- TTM: graphics memory manager, similar to GEM, but geared towards discrete graphics cards with VRAM (confirm!)

- Intel 8xx support:
  * no upstream interest in support/bug fixing
  * Jesse says that for 810/815 you have to run the old -810 driver; with some hammering it should build
  * 830 and up are tested by upstream; recent kernel patch fixed a lot of 8xx issues
  * tutorials available? not really

- https://launchpad.net/~xorg-edgers/+archive/ppa has latest versions for testing
- https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/ (more stable bits for jaunty, i.e. upstream bugfix releases)

- when 2.6.31 comes up, kernel side will be in better shape than the user land drivers

- intel-gpu-tools available in PPA, needs to be uploaded to karmic proper
- when intel driver runs into a GPU lockup, it's possible to capture a batch buffer dump using:
  https://launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test
  (upstream says they are working on code that will automatically reset the GPU
   when it locks up. In an ideal world the user might not even notice the lockup)

- Tagging intel and ATI bugs in LP: both with chipset and symptom tags
  There is a wiki page with all the tags listed.

- We need a platform for testing (defined set of functionality that we want
  working on a defined set of cards). We can use this to measure the quality
  of the release. The list of certified hardware for example.
  Apple has limited/bounded set of hardware and MS has the Windows logo program.

- Is there a way to get a list of the most common hardware out there?


CategorySpec

X/Roadmap/Karmic (last edited 2009-08-05 13:24:02 by 89)