Karmic

Differences between revisions 4 and 13 (spanning 9 versions)
Revision 4 as of 2009-06-04 00:24:03
Size: 6908
Editor: pool-74-107-135-97
Comment:
Revision 13 as of 2009-08-05 13:24:02
Size: 7029
Editor: 89
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
== Design == == Roadmap ==

[Formatted for emailing]
Line 19: Line 21:
   x-server: 1.7    x-server: 1.7   (Brings libxi 2.0, inputproto 2.0, evdev 2.3)
Line 24: Line 26:

   UPDATE - As of Alpha-4, some components were unavailable. We are now targeting the following:
   kernel: 2.6.31
   libdrm: 2.6.12
   mesa: 7.6
   x-server: 1.6.3
   xorg: 7.4
Line 36: Line 46:
          Version: 2.8 (potentially 2.9 if schedule permits)
Line 45: Line 56:
          Version: Unspecified
Line 52: Line 64:
          TV-Out: All chipsets           TV-Out: R1xx-R3xx
Line 56: Line 68:
          Version: 9.10
Line 65: Line 78:
          Version: Unspecified
Line 71: Line 85:
          Duallink DVI: R600 and newer
          TV-Out: R600 and newer
          Duallink DVI: Unspecified
          TV-Out: Unspecified
Line 76: Line 90:
          Version: -96.x, -173.x
Line 80: Line 95:
          Duallink DVI: Unspecified
          TV-Out: Unspecified
          DisplayPort: No
Line 81: Line 99:
   -nvidia (current): Newer Nvidia chipsets    -nvidia (current): GeForce 6xxx and newer
         Version:      -185.x
Line 86: Line 105:
          Duallink DVI: Unspecified
          TV-Out: Yes
          DisplayPort: Yes
Line 87: Line 109:
Key Karmic Goals for X.org
--------------------------
Line 107: Line 131:
    Key design points for this objective:
    * No plymouth at all.
    * No usplash for a default boot.
    * usplash will be started for fsck, and for entering a passphrase for
      encrypted root partitions.
    * X will be started as early as possible in the boot process and just
      display a bg image with a throbber. Once enough of the system is
      up, gdm starts and replaces the throbber.
Line 112: Line 145:
More Information
----------------
Line 115: Line 150:
Ubuntu Alpha release ISOs are available at: Ubuntu Alpha release ISOs are available for testing at:
Line 119: Line 154:
== Design / Rationale ==
Line 120: Line 156:
-intel version 2.9 may be available in time for Karmic. There are no major features planned for that release; mostly it will be removing non-KMS code (not something we care about). However it may contain some worthwhile bug fixes, so may be worth consideration if it is released with sufficient time for integration; we'll plan on 2.8 for now and see how things go.

== Implementation Tasks ==

 * (DONE) Write roadmap
 * (DONE) Send roadmap to video driver partners, Mobile team, and any other X.org requirements consumers
 * (DONE) Pull intel-gpu-tools into Karmic/Universe
 * (DONE) Update directions at https://launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test (Probably move into wiki)
 * (DONE) Follow up with jbarnes regarding automatic GPU lockup resetting / apport triggering
 * (DONE) Ogasawara says she can obtain a listing indicating the most common video hardware; this needs following up on
 * (DONE) Provide jbarnes with a listing of the hardware Canonical certifies against
 
Line 124: Line 172:
{{{
- 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
Line 127: Line 173:
- 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
<ghexsel> - According to Phoronix (http://www.phoronix.com/scan.php?page=news_item&px=NzI4OQ). the schedule slipped. Will it still make the cut?
<bryce> - presumably yes; if not we'll ship whatever -rc version is available at the time, and backport fixes as appropriate.
Line 139: Line 176:
- 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 provides 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.

Roadmap

[Formatted for emailing]

Karmic Target Versions for Release
----------------------------------
   kernel:              2.6.31
   libdrm:              2.6.12
   mesa:                7.6
   x-server:            1.7   (Brings libxi 2.0, inputproto 2.0, evdev 2.3)
   xorg:                7.5

   (We are carrying rc versions of the above currently, but anticipate
    these versions will be released in time for Karmic.)

   UPDATE - As of Alpha-4, some components were unavailable.  We are now targeting the following:
   kernel:              2.6.31
   libdrm:              2.6.12
   mesa:                7.6
   x-server:            1.6.3
   xorg:                7.4


Karmic Important Dates
----------------------
   June 19th            xserver 1.6.99.901 + xorg 7.5 beta 1
   July 15th            xserver 1.7 + xorg 7.5 release
   Sept 7th             Ubuntu Deadline for driver version updates
   Oct 1st              Ubuntu Beta
   Oct 29th             Ubuntu Final Release

Driver-Specific Requirements
----------------------------
   -intel:              All Intel chipsets >= i810
          Version:      2.8 (potentially 2.9 if schedule permits)
          AccelMethod:  UXA
          DRI:          DRI2
          Memory:       GEM
          KMS:          "On" for all chipsets by default
          Duallink DVI: Chipsets >= i830
          TV-Out:       Chipsets >= i830
          DisplayPort:  Best efforts (G40-series)

   -ati:                All Radeon chipsets
          Version:      Unspecified
          AccelMethod:  EXA
          DRI:          3D on chipsets R5xx and older only
                        Best efforts for newer chipsets
          Memory:       Unspecified
          KMS:          "On" for chipsets R5xx and older only
                        Best efforts for newer chipsets
          Duallink DVI: R400 and newer
          TV-Out:       R1xx-R3xx
          DisplayPort:  No

   -fglrx:              Radeon chipsets R600 and newer only
          Version:      9.10
          AccelMethod:  Unspecified
          DRI:          Unspecified
          Memory:       Unspecified
          KMS:          No
          Duallink DVI: R600 and newer
          TV-Out:       R600 and newer
          DisplayPort:  DCE 3.0 chipsets and newer

   -nouveau:            All Nvidia chipsets >= NV04
          Version:      Unspecified
          AccelMethod:  EXA
          DRI:          2D only
                        Best efforts for 3D
          Memory:       Unspecified
          KMS:          "On" for NV40 and newer
                        Best efforts for older chipsets
          Duallink DVI: Unspecified
          TV-Out:       Unspecified
          DisplayPort:  G98 only

   -nvidia (legacy):    Older Nvidia chipsets
          Version:      -96.x, -173.x
          AccelMethod:  Unspecified
          DRI:          Unspecified
          Memory:       Unspecified
          KMS:          No
          Duallink DVI: Unspecified
          TV-Out:       Unspecified
          DisplayPort:  No

   -nvidia (current):   GeForce 6xxx and newer
          Version:      -185.x
          AccelMethod:  Unspecified
          DRI:          Unspecified
          Memory:       Unspecified
          KMS:          No
          Duallink DVI: Unspecified
          TV-Out:       Yes
          DisplayPort:  Yes

Key Karmic Goals for X.org
--------------------------
1.  KMS / Flicker-Free Boot

    Kernel mode-setting (KMS) is a major target objective for this release.
    We may be updating to newer versions of mesa if needed for KMS support.

    We anticipate that not all drivers will support KMS, so the kernel will
    be determining whether to use KMS or not on a per-driver basis, and if
    KMS is not in use, will boot similar to how it's been done up to now.

2.  Fast Boot / Fast Resume

    Improving boot and suspend/resume speed is another major goal for
    Karmic.  Our objective is to boot fast enough that no splash screen
    is required.  Therefore we will not be integrating plymouth into our
    boot process.  Where boot speeds cannot be sufficiently reduced we
    will continue to use usplash.

    We anticipate KMS will help in achieving this objective, and are
    looking for additional ideas for improving X.org boot speed further.

    Key design points for this objective:
    * No plymouth at all.
    * No usplash for a default boot.
    * usplash will be started for fsck, and for entering a passphrase for
      encrypted root partitions.
    * X will be started as early as possible in the boot process and just
      display a bg image with a throbber. Once enough of the system is
      up, gdm starts and replaces the throbber.

3.  Virtual Terminals

    In Karmic, VT1 will be used for X, VT2 as a console login, and VT3
    for kernel log messages.

More Information
----------------
Specific dates of Ubuntu Alpha releases are at:
  https://wiki.ubuntu.com/KarmicReleaseSchedule

Ubuntu Alpha release ISOs are available for testing at:
  http://cdimage.ubuntu.com/releases/9.10/

Design / Rationale

-intel version 2.9 may be available in time for Karmic. There are no major features planned for that release; mostly it will be removing non-KMS code (not something we care about). However it may contain some worthwhile bug fixes, so may be worth consideration if it is released with sufficient time for integration; we'll plan on 2.8 for now and see how things go.

Implementation Tasks

  • (DONE) Write roadmap
  • (DONE) Send roadmap to video driver partners, Mobile team, and any other X.org requirements consumers
  • (DONE) Pull intel-gpu-tools into Karmic/Universe
  • (DONE) Update directions at https://launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test (Probably move into wiki)

  • (DONE) Follow up with jbarnes regarding automatic GPU lockup resetting / apport triggering
  • (DONE) Ogasawara says she can obtain a listing indicating the most common video hardware; this needs following up on
  • (DONE) Provide jbarnes with a listing of the hardware Canonical certifies against

Outstanding Issues

BoF agenda and discussion

<ghexsel> - According to Phoronix (http://www.phoronix.com/scan.php?page=news_item&px=NzI4OQ). the schedule slipped. Will it still make the cut? <bryce> - presumably yes; if not we'll ship whatever -rc version is available at the time, and backport fixes as appropriate.


CategorySpec

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