AlsaModulesOutsideKernelTree

Revision 1 as of 2008-12-10 17:59:12

Clear message

Summary

Discuss ways in which the alsa driver modules can be maintained outside the kernel tree in a separate source package.

Release Note

The alsa driver modules are now maintained in a separate package, allowing for quicker turn-around times in supporting new audio hardware.

Rationale

Maintaining the alsa driver modules outside the kernel source will allow for much easier and quicker updates of existing drivers, such as adding system quirks or new PCI IDs. It also allows for a consistant alsa version accross the 3 kernel source trees currently in the Ubuntu archive.

Use Cases

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

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

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.

BoF agenda and discussion

  • How do we package the drivers separately? Is DKMS a consideration, or will it take too long to build all driver modules?
  • Could we possibly consider having separate packages for each kernel, which are pulled in with the metapackages? Likely not, as the kernel team want to do away with all such packages.

CategorySpec