Karmic
Differences between revisions 1 and 4 (spanning 3 versions)
|
Size: 6134
Comment:
|
Size: 6908
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| * '''Launchpad Entry''': UbuntuSpec:foo * '''Created''': <<Date(2005-10-25T15:45:54Z)>> * '''Contributors''': * '''Packages affected''': * '''See also''': SpecTemplate |
* '''Launchpad Entry''': UbuntuSpec:desktop-karmic-xorg * '''Created''': <<Date(2009-05-06T17:00:00Z)>> * '''Contributors''': BryceHarrington * '''Packages affected''': xorg * '''See also''': [[X/Blueprints]] |
| Line 9: | Line 9: |
| This specification describes the way we would like Ubuntu specifications to be written. It takes the form of a specification itself. == Rationale == As we develop new ideas for features in Ubuntu, it's important to be able to communicate them clearly. This serves the purpose of making it clear what the feature is about, and allowing people to evolve an implementation strategy for it. Publishing this content gives our community a chance to participate in the discussion and design of a feature, and increases the chance that community members will feel confident enough to start work on the implementation of the feature. A good specification also allows community members who were not physically present at meetings discussing a topic to participate in the implementation of the spec. Bottom line: the better your spec, the better the chances that your ideas will be clearly understood by the review team. == Use Cases == * Bob is the maintainer for the boot process for Ubuntu. In the Dapper cycle, he would like to work on getting the boot time down to two seconds from boot manager to GDM screen. He creates an entry for the specification in Launchpad, proposes it for the UBZ sprint, and starts writing out a braindump of it in the Ubuntu wiki. Magnus, who is in charge of UBZ scheduling, thinks it sounds fishy but approves it to make sure that the change is discussed and documented properly. He marks it as priority Medium because he isn't sure Bob will have time free for implementing it during Dapper. * Pedro works on Malone, in Launchpad. Before UBZ, he remembers that the dependency handling in the bug tracker is really not optimal. He writes out a Summary and Rationale in a Launchpad wiki page, registers it as a specification in Launchpad, and suggests it for UBZ. Monica, Launchpad manageress, thinks that this is really not the time to be talking about it and rejects the application for UBZ. He then indicates it for the next conference, UBB, and marks its priority is Low. * Jason is an Ubuntu and Rosetta user. He has noticed that changes made to translations are making their way into language packs but not to the upstream versions, and adds a specification that describes a way for getting upstream to use language packs. Monica also has a plan for this but hadn't described it in a spec, so she adds it to the UBZ spec list, and adds Carlos, Rosetta maintainer, as drafter for it. == Scope == This specification covers feature specifications for Ubuntu and Launchpad. It is not meant as a more general specification format. |
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. |
| Line 35: | Line 13: |
| A specification should be built with the following considerations: | {{{ Karmic Target Versions for Release ---------------------------------- kernel: 2.6.31 libdrm: 2.6.12 mesa: 7.6 x-server: 1.7 xorg: 7.5 |
| Line 37: | Line 22: |
| * The person implementing it may not be the person writing it. It should be clear enough for someone to be able to read it and have a clear path towards implementing it. If it doesn't, it needs more detail. | (We are carrying rc versions of the above currently, but anticipate these versions will be released in time for Karmic.) |
| Line 39: | Line 25: |
| * That the use cases covered in the specification should be practical situations, not contrived issues. | 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 |
| Line 41: | Line 33: |
| * Limitations and issues discovered during the creation of a specification should be clearly pointed out so that they can be dealt with explicitly. | Driver-Specific Requirements ---------------------------- -intel: All Intel chipsets >= i810 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) |
| Line 43: | Line 44: |
| * If you don't know enough to be able to competently write a spec, you should either get help or research the problem further. Avoid spending time making up a solution: base yourself on your peers' opinions and prior work. | -ati: All Radeon chipsets 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: All chipsets DisplayPort: No |
| Line 45: | Line 55: |
| * Specifications should be written in clear, concise and correct English. If you're not a native speaker, co-editing the spec with somebody who is might be a good idea. | -fglrx: Radeon chipsets R600 and newer only 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 |
| Line 47: | Line 64: |
| Specific issues related to particular sections are described further below. | -nouveau: All Nvidia chipsets >= NV04 AccelMethod: EXA DRI: 2D only Best efforts for 3D Memory: Unspecified KMS: "On" for NV40 and newer Best efforts for older chipsets Duallink DVI: R600 and newer TV-Out: R600 and newer DisplayPort: G98 only |
| Line 49: | Line 75: |
| === Summary === | -nvidia (legacy): Older Nvidia chipsets AccelMethod: Unspecified DRI: Unspecified Memory: Unspecified KMS: No |
| Line 51: | Line 81: |
| The summary should not attempt to say '''why''' the spec is being defined, just '''what''' is being specified. | -nvidia (current): Newer Nvidia chipsets AccelMethod: Unspecified DRI: Unspecified Memory: Unspecified KMS: No |
| Line 53: | Line 87: |
| === Rationale === | 1. KMS / Flicker-Free Boot |
| Line 55: | Line 89: |
| This should be the description of '''why''' this spec is being defined. | 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. |
| Line 57: | Line 92: |
| === Scope and Use Cases === | 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. |
| Line 59: | Line 96: |
| While not always required, but in many cases they bring much better clarity to the scope and scale of the specification than could be obtained by talking in abstract terms. | 2. Fast Boot / Fast Resume |
| Line 61: | Line 98: |
| ==== Use Cases ==== | 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. |
| Line 63: | Line 104: |
| Use cases are positive statements which (loosely) conform to a pattern like | We anticipate KMS will help in achieving this objective, and are looking for additional ideas for improving X.org boot speed further. |
| Line 65: | Line 107: |
| * A person and their role * The objective they want to achieve * The steps they go through * The positive result |
3. Virtual Terminals |
| Line 70: | Line 109: |
| Specifically, describing the current unsatisfactory state of affairs is not a use case; that belongs in the Rationale section. | In Karmic, VT1 will be used for X, VT2 as a console login, and VT3 for kernel log messages. |
| Line 72: | Line 112: |
| === Implementation Plan === | Specific dates of Ubuntu Alpha releases are at: https://wiki.ubuntu.com/KarmicReleaseSchedule |
| Line 74: | Line 115: |
| This section is usually broken down into subsections, such as the packages being affected, data and system migration where necessary, user interface requirements and pictures (photographs of drawings on paper work well). | Ubuntu Alpha release ISOs are available at: http://cdimage.ubuntu.com/releases/9.10/ }}} |
| Line 76: | Line 119: |
| == Implementation == To implement a specification, the assignee should observe the use cases carefully, and follow the design specified. He should make note of places in which he has strayed from the design section, adding rationale describing why this happened. This is important so that next iterations of this specification (and new specifications that touch upon this subject) can use the specification as a reference. The implementation is very dependent on the type of feature to be implemented. Refer to the team leader for further suggestions and guidance on this topic. |
|
| Line 84: | Line 122: |
| The specification process requires experienced people to drive it. More documentation on the process should be produced. The drafting of a specification requires English skills and a very good understanding of the problem. It must also describe things to an extent that someone else could implement. This is a difficult set of conditions to ensure throughout all the specifications added. There is a lot of difficulty in gardening obsolete, unwanted and abandoned specifications in the Wiki. |
|
| Line 91: | Line 124: |
| {{{ - 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 92: | Line 127: |
| We'll have a first public session on this on the first Monday in UBZ. | - 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? }}} |
Launchpad Entry: desktop-karmic-xorg
Created: 2009-05-06
Contributors: BryceHarrington
Packages affected: xorg
See also: X/Blueprints
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.
Design
Karmic Target Versions for Release
----------------------------------
kernel: 2.6.31
libdrm: 2.6.12
mesa: 7.6
x-server: 1.7
xorg: 7.5
(We are carrying rc versions of the above currently, but anticipate
these versions will be released in time for Karmic.)
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
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
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: All chipsets
DisplayPort: No
-fglrx: Radeon chipsets R600 and newer only
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
AccelMethod: EXA
DRI: 2D only
Best efforts for 3D
Memory: Unspecified
KMS: "On" for NV40 and newer
Best efforts for older chipsets
Duallink DVI: R600 and newer
TV-Out: R600 and newer
DisplayPort: G98 only
-nvidia (legacy): Older Nvidia chipsets
AccelMethod: Unspecified
DRI: Unspecified
Memory: Unspecified
KMS: No
-nvidia (current): Newer Nvidia chipsets
AccelMethod: Unspecified
DRI: Unspecified
Memory: Unspecified
KMS: No
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.
3. Virtual Terminals
In Karmic, VT1 will be used for X, VT2 as a console login, and VT3
for kernel log messages.
Specific dates of Ubuntu Alpha releases are at:
https://wiki.ubuntu.com/KarmicReleaseSchedule
Ubuntu Alpha release ISOs are available at:
http://cdimage.ubuntu.com/releases/9.10/
Outstanding Issues
BoF agenda and discussion
- 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 - 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?
X/Roadmap/Karmic (last edited 2009-08-05 13:24:02 by 89)