KernelKarmicSponsoringStagingDrivers

Differences between revisions 2 and 6 (spanning 4 versions)
Revision 2 as of 2009-05-15 11:57:39
Size: 2612
Editor: 220
Comment:
Revision 6 as of 2009-05-25 09:23:06
Size: 2538
Editor: 80
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples. Discussing following topics in this session:
 * How can we better help drivers that Ubuntu is using that are in the /staging tree
 * Can we make an effort to clean up and help move the driver into mainline
 * If so what drivers etc...
Line 14: Line 17:
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.
N/A
Line 20: Line 21:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. Ubuntu carries a number of staging drivers to support users hardware. Many of them won't compile or of a quality that leaves the user with a bad experience.
Also the drivers receive less attention and may get improved over time because nobody looks at them either by using or trying to improve the code.
What we need is to find a way to get together with the people originally doing those drivers or currently interested in them and think of steps to get drivers moved out of staging into the generic kernel space.
Line 23: Line 26:
 * Bob has a notebook with the latest wifi card that does not have an in kernel supported driver. There is one in staging that works only until he suspends.
 * Song reported that T61P wifi which does not work in Intrepid works out-of-box on Jaunty. That is because of staging tree driver.
Line 26: Line 31:
 * The kernel team has the communtiy developer support or enough Canonical kernel team cycles to help fix.
Line 28: Line 35:
You can have subsections that better describe specific parts of the issue. TBD
Line 32: Line 39:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: TBD
Line 36: Line 43:
Should cover changes required to the UI, or specific UI that is required to implement this No UI changes should be required.
Line 40: Line 47:
Code changes should include an overview of what needs to change, and in some cases even the specific details. TBD
Line 57: Line 64:
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. TBD

Summary

Discussing following topics in this session:

  • How can we better help drivers that Ubuntu is using that are in the /staging tree
  • Can we make an effort to clean up and help move the driver into mainline
  • If so what drivers etc...

Release Note

N/A

Rationale

Ubuntu carries a number of staging drivers to support users hardware. Many of them won't compile or of a quality that leaves the user with a bad experience. Also the drivers receive less attention and may get improved over time because nobody looks at them either by using or trying to improve the code. What we need is to find a way to get together with the people originally doing those drivers or currently interested in them and think of steps to get drivers moved out of staging into the generic kernel space.

User stories

  • Bob has a notebook with the latest wifi card that does not have an in kernel supported driver. There is one in staging that works only until he suspends.
  • Song reported that T61P wifi which does not work in Intrepid works out-of-box on Jaunty. That is because of staging tree driver.

Assumptions

  • The kernel team has the communtiy developer support or enough Canonical kernel team cycles to help fix.

Design

TBD

Implementation

TBD

UI Changes

No UI changes should be required.

Code Changes

TBD

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

TBD

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.


CategorySpec

specs/KernelKarmicSponsoringStagingDrivers (last edited 2009-05-26 08:18:49 by 80)