summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorAlan Jenkins <alan-jenkins@tuffmail.co.uk>2010-02-22 16:03:58 +0000
committerGreg Kroah-Hartman <gregkh@suse.de>2010-07-05 11:16:10 -0700
commit8ce881616b79099adc73fe27e5f0aa1ea26354c4 (patch)
treea5005182bd9f82022d1cafb9c211b82386d48f1f /include
parent62008a6b67c40a295086607e34ba5816d6642f88 (diff)
downloadkernel-crypto-8ce881616b79099adc73fe27e5f0aa1ea26354c4.tar.gz
kernel-crypto-8ce881616b79099adc73fe27e5f0aa1ea26354c4.tar.xz
kernel-crypto-8ce881616b79099adc73fe27e5f0aa1ea26354c4.zip
eeepc-laptop: check wireless hotplug events
commit bc9d24a3aeb1532fc3e234907a8b6d671f7ed68f upstream. Before we mark the wireless device as unplugged, check PCI config space to see whether the wireless device is really disabled (and vice versa). This works around newer models which don't want the hotplug code, where we end up disabling the wired network device. My old 701 still works correctly with this. I can also simulate an afflicted model by changing the hardcoded PCI bus/slot number in the driver, and it seems to work nicely (although it is a bit noisy). In future this type of hotplug support will be implemented by the PCI core. The existing blacklist and the new warning message will be removed at that point. Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk> Signed-off-by: Corentin Chary <corentincj@iksaif.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions