summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorDave Hansen <haveblue@us.ibm.com>2005-07-30 12:49:58 -0700
committerJeff Garzik <jgarzik@pobox.com>2005-07-30 18:17:22 -0400
commit0cd545d6ba0e0138782eb0ec287d0eb3db529b69 (patch)
tree0039836752d1ae1a3d3aab8b514e9159573fd146 /init
parent0ef79ee22cf5c1b177184c18b6525889bcc6681f (diff)
downloadblackbird-op-linux-0cd545d6ba0e0138782eb0ec287d0eb3db529b69.tar.gz
blackbird-op-linux-0cd545d6ba0e0138782eb0ec287d0eb3db529b69.zip
[PATCH] hostap update
Create sysfs "device" files for hostap I was writing some scripts to automatically build kismet source lines, and I noticed that hostap devices don't have device files, unlike my prism54 and ipw2200 cards: $ ls -l /sys/class/net/eth0/device /sys/class/net/eth0/device -> ../../../devices/pci0000:00/0000:00:1e.0/0000:02:01.0 $ ls -l /sys/class/net/wifi0 ls: /sys/class/net/wifi0/device: No such file or directory $ ls -l /sys/class/net/wlan0 ls: /sys/class/net/wlan0/device: No such file or directory The following (quite small) patch makes sure that both the wlan and wifi net devices have that pointer to the bus device. This way, I can do things like for i in /sys/class/net/*; do if ! [ -e $i/device/drive ]; then continue; fi; driver=$(basename $(readlink $i/device/driver)) case $driver in hostap*) echo -- hostap,$i,$i-$driver break; ipw2?00) echo -- $driver,$i,$i-$driver break; prism54) echo prism54g,$i esac done Which should generate a working set of source lines for kismet no matter what order I plug the cards in. It might also be handy to have a link between the two net devices, but that's a patch for another day. That patch is against 2.6.13-rc1-mm1. -- Dave Signed-off-by: Dave Hansen <haveblue@us.ibm.com> Signed-off-by: Jouni Malinen <jkmaline@cc.hut.fi> Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud