Messages in this thread | | | Date | Fri, 6 Jan 2006 12:46:20 +0100 | From | Dominik Brodowski <> | Subject | Re: State of the Union: Wireless |
| |
On Fri, Jan 06, 2006 at 12:31:24PM +0100, Johannes Berg wrote: > On Fri, 2006-01-06 at 12:00 +0100, Michael Buesch wrote: > > > * "master" interface as real device node > > * Virtual interfaces (net_devices) > > I didn't want to spam the netdev wiki with this (yet) so I collected > some more structured things outside. Anyone feel free to edit: > http://softmac.sipsolutions.net/802.11
From someone who has no idea at all (yet) about 802.11: why character device, and not sysfs or configfs files? Like
TASK: get list of MAC addresses available to hardware device (usually only one for current hw)
cat /sys/devices/path/to/device/wireless/address
TASK: get list of virtual devices including (some of) their properties
ls -l /sys/devices/path/to/device/wireless/ ... wlan0 -> /sys/class/net/wlan0 wlan1 -> /sys/class/net/wlan1
TASK: create virtual device (with arbitrary type, netdev name and mac address) ^^^^^^ isn't nameif / udev for that?
echo "$type" > /sys/devices/path/to/device/wireless/new_if ... we get uevents for this new interface; in this we can set the mac adress doing: echo "$mac" > /sys/class/net/wlan0/wireless/address
TASK: configure virtual device (key is the device name since that needs to be unique anyway)
echo "$some_config_option_for_virtual_device" > /sys/class/net/wlan0/wireless/some_option echo "$some_config_option_for_physical_device"> /sys/devices/path/to/dev/wireless/some_other_option
Of course the configuration userspace tool would use libsysfs for that, not "echo" scripts... but they'd work too.
Dominik - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |