ath5k: Add LED support for Acer device

Bug #412039 reported by Steve Magoun
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
Jaunty
Invalid
Undecided
Unassigned
linux-backports-modules-2.6.28 (Ubuntu)
Invalid
Undecided
Unassigned
Jaunty
Won't Fix
Medium
Unassigned

Bug Description

Please add the following to ath5k_led_devices to add LED support for an unreleased device:
 { ATH_SDEVICE(PCI_VENDOR_ID_FOXCONN, 0xe00d), ATH_LED(3, 0) } in ath5k_led_devices[].

This low-impact patch is necessary for hardware enablement of a new device. The patch is not yet upstream. The change is not expected to affect any devices other than the new device being enabled.

Steve Magoun (smagoun)
description: updated
Tim Gardner (timg-tpi)
Changed in linux (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu Jaunty):
status: New → Invalid
Changed in linux-backports-modules-2.6.28 (Ubuntu):
status: New → Invalid
Changed in linux-backports-modules-2.6.28 (Ubuntu Jaunty):
status: New → In Progress
Revision history for this message
Tim Gardner (timg-tpi) wrote :

This patch can be implemented easily enough in Jaunty LBM, but the issue is if LBM is ever updated from upstream. If that happens, then this patch will get lost. Do foresee this package ever needing to be updated?

Changed in linux-backports-modules-2.6.28 (Ubuntu Jaunty):
importance: Undecided → Medium
assignee: nobody → Tim Gardner (timg-tpi)
Revision history for this message
Steve Conklin (sconklin) wrote :

Tim,

It's possible that the package will need updating from upstream since there is new hardware enablement still taking place from the jaunty tree. Perhaps we should go ahead and create the netbook branch in jaunty-lbm and go from there. We can apply the patch before the branch, so main distro gets it too.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

The issue is more about how LBM is updated, e.g., its not a differential update, its a straight copy from upstream which would regress any patches that were applied to previous versions. I don't have any problems applying this patch, but we'll want to be aware of regressions that future updates _will_ cause. One option is to add a patch directory so that its more difficult to lose track of these changes.

Andy Whitcroft (apw)
Changed in linux-backports-modules-2.6.28 (Ubuntu Jaunty):
assignee: Tim Gardner (timg-tpi) → Andy Whitcroft (apw)
Andy Whitcroft (apw)
Changed in linux-backports-modules-2.6.28 (Ubuntu Jaunty):
assignee: Andy Whitcroft (apw) → nobody
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Jaunty reached end-of-life on 23 October 2010, so this bug will not be fixed in that version of Ubuntu. It has been marked as invalid in newer versions.

Changed in linux-backports-modules-2.6.28 (Ubuntu Jaunty):
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.