| 2009-04-30 20:11:16 |
Stefan Bader |
description |
We now have the staging tree in Jaunty kernels. (I was a little bit surprised, so any pointers to the plans, policies or discussion about this would be awesome). I discovered that my prism2_usb device now was picked up by the staging driver.
I guess it was not planned that we now are shipping two prism2_usb.ko modules, one in staging and another in misc/wireless. But the good news is that the staging module seems to perform better than the old:
- my wlan always come up at boot. Previously I often had USB problems if it was plugged in, and I would have to unplug and replug it once or many times.
- after heavy usage (dist-upgrades etc) it would previously often get stuck (like if it was overheated) but now it seems stable, from my testing so far. YMMV.
So maybe we can delete the old misc/wireless version, which was also a nightmare to have synced and maintained, at least from my experience dealing with the kernel team.
I don't know if you have tools to detect other driver conflicts with staging. |
SRU justification:
Impact: Due to a build race there was a chance to get the prism2_usb driver from ubuntu or staging being built. Looking at some released packages the staging driver won the race most of the time.
Fix: Make sure only the staging driver will be built in future by removing the unwanted driver completely.
Testcase: check prism2_usb driver in the package.
---
We now have the staging tree in Jaunty kernels. (I was a little bit surprised, so any pointers to the plans, policies or discussion about this would be awesome). I discovered that my prism2_usb device now was picked up by the staging driver.
I guess it was not planned that we now are shipping two prism2_usb.ko modules, one in staging and another in misc/wireless. But the good news is that the staging module seems to perform better than the old:
- my wlan always come up at boot. Previously I often had USB problems if it was plugged in, and I would have to unplug and replug it once or many times.
- after heavy usage (dist-upgrades etc) it would previously often get stuck (like if it was overheated) but now it seems stable, from my testing so far. YMMV.
So maybe we can delete the old misc/wireless version, which was also a nightmare to have synced and maintained, at least from my experience dealing with the kernel team.
I don't know if you have tools to detect other driver conflicts with staging. |
|
