Karmic
Differences between revisions 1 and 8 (spanning 7 versions)
|
Size: 6134
Comment:
|
Size: 6609
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. | 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 11: | Line 11: |
| == Rationale == | == Roadmap == |
| Line 13: | Line 13: |
| 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. | [Formatted for emailing] |
| Line 15: | Line 15: |
| 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. | {{{ 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 |
| Line 17: | Line 24: |
| 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. | (We are carrying rc versions of the above currently, but anticipate these versions will be released in time for Karmic.) |
| Line 19: | Line 27: |
| Bottom line: the better your spec, the better the chances that your ideas will be clearly understood by the review team. | 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 21: | Line 35: |
| == Use Cases == | 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) |
| Line 23: | Line 47: |
| * 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. | -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: All chipsets DisplayPort: No |
| Line 25: | Line 59: |
| * 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. | -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 |
| Line 27: | Line 69: |
| * 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. | -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 |
| Line 29: | Line 81: |
| == Scope == | -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 |
| Line 31: | Line 91: |
| This specification covers feature specifications for Ubuntu and Launchpad. It is not meant as a more general specification format. | -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 |
| Line 33: | Line 101: |
| == Design == | Key Karmic Goals for X.org -------------------------- 1. KMS / Flicker-Free Boot |
| Line 35: | Line 105: |
| A specification should be built with the following considerations: | 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 37: | Line 108: |
| * 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 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 39: | Line 112: |
| * That the use cases covered in the specification should be practical situations, not contrived issues. | 2. Fast Boot / Fast Resume |
| Line 41: | Line 114: |
| * Limitations and issues discovered during the creation of a specification should be clearly pointed out so that they can be dealt with explicitly. | 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 43: | Line 120: |
| * 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. | We anticipate KMS will help in achieving this objective, and are looking for additional ideas for improving X.org boot speed further. |
| Line 45: | Line 123: |
| * 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. | 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 47: | Line 132: |
| Specific issues related to particular sections are described further below. | 3. Virtual Terminals |
| Line 49: | Line 134: |
| === Summary === | In Karmic, VT1 will be used for X, VT2 as a console login, and VT3 for kernel log messages. |
| Line 51: | Line 137: |
| The summary should not attempt to say '''why''' the spec is being defined, just '''what''' is being specified. | More Information ---------------- Specific dates of Ubuntu Alpha releases are at: https://wiki.ubuntu.com/KarmicReleaseSchedule |
| Line 53: | Line 142: |
| === Rationale === | Ubuntu Alpha release ISOs are available for testing at: http://cdimage.ubuntu.com/releases/9.10/ }}} |
| Line 55: | Line 146: |
| This should be the description of '''why''' this spec is being defined. | == Design / Rationale == |
| Line 57: | Line 148: |
| === Scope and Use Cases === | -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. |
| Line 59: | Line 150: |
| 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. | == Implementation Tasks == |
| Line 61: | Line 152: |
| ==== Use Cases ==== Use cases are positive statements which (loosely) conform to a pattern like * A person and their role * The objective they want to achieve * The steps they go through * The positive result Specifically, describing the current unsatisfactory state of affairs is not a use case; that belongs in the Rationale section. === Implementation Plan === 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). == 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. |
* (DONE) Write roadmap * Send roadmap to video driver partners, Mobile team, and any other X.org requirements consumers * Pull intel-gpu-tools into Karmic/Universe * Update directions at https://launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test (Probably move into wiki) * Follow up with jbarnes regarding automatic GPU lockup resetting / apport triggering * Ogasawara says she can obtain a listing indicating the most common video hardware; this needs following up on * Provide jbarnes with a listing of the hardware Canonical certifies against |
| Line 84: | Line 162: |
| 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 92: | Line 165: |
| We'll have a first public session on this on the first Monday in UBZ. | <ghexsel> - According to Phoronix (http://www.phoronix.com/scan.php?page=news_item&px=NzI4OQ). the schedule slipped. Will it still make the cut? |
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.
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.)
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: All chipsets
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
- Send roadmap to video driver partners, Mobile team, and any other X.org requirements consumers
- Pull intel-gpu-tools into Karmic/Universe
Update directions at https://launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test (Probably move into wiki)
- Follow up with jbarnes regarding automatic GPU lockup resetting / apport triggering
- Ogasawara says she can obtain a listing indicating the most common video hardware; this needs following up on
- 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?
X/Roadmap/Karmic (last edited 2009-08-05 13:24:02 by 89)