KernelKarmicReviewOfNonUpstreamedCode

Revision 2 as of 2009-05-16 09:32:00

Clear message

Summary

Code that was not upstream but useful to Ubuntu users has been carried in the ubuntu modules. However, now that staging exists, we should make every effort to remove code from there.

Release Note

(Only if there really will be drivers removed) Some drivers have been removed as they where no longer maintained upstream.

Rationale

All drivers in the ubuntu directory are not automatically synced with the kernel. This causes breakage and requires the ubuntu kernel team to either sync manually with a more recent version or modify that code to work again. Code there will also be much less reviewed and worked on compared to the rest of the kernel. Since the linux kernel now carries a staging tree which carries non-mature code in order to get it better tested and/or worked on, we should try to get all of our drivers in ubuntu moved over to staging.

User stories

  • Albert uses iscsitarget on Hardy. After upgrading to Intrepid it was broken as it was synced to some version that missed important fixes.
  • Bob used the prism2_usb module in Intrepid. It was usually not touched much often. Now the module is in the staging tree and get automatically maintained from upsream.

Implementation

We would have to assess and decide what to do with the following drivers currently in the karmic ubuntu directory:

  • aufs
  • compcache
  • dm-loop
  • dm-raid4-5
  • drbd
  • gfs
  • iscsitarget
  • lenovo-sl-laptop (ACPI driver for Lenovo SL laptops)
  • appleir (Apple USB infrared receiver)
  • fsam7400 (rfkill for Fujitsu Siemens Amilo M 7400)
  • lmpcm_usb (Logitech MediaPlay cordless mouse driver)

  • snd-bt-sco (Bluetooth SCI sound driver)
  • thinkpad_ec (access driver for the Thinkpad EC)
  • tp_smapi (enhanced battery control for Thinkpads)
  • ndiswrapper
  • av5100 (rfkill for Averatec 5100P)
  • pbe5 (rfkill for Packard Bell EasyNote E5)

Some might get intentionally dropped as they are replaced by other drivers in the Karmic cycle. For the others we need to check whether they

  • are actively maintained someplace
  • they are valid to be placed into the staging tree

Test/Demo Plan

If drivers are only moved from ubuntu to staging, we only need to verify they are still build and included in the package. Replaced drivers need a specific plan, depending on the driver.

Unresolved issues

  • If a driver is maintained somewhere else and the maintainer(s) do not want to see the driver included upstream, would DMKS be a plan B?

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