On Wed, 12 Jul 2006 10:09:32 -0400, Dan Williams wrote: > Can you run "tree /sys", tar up and compress that output, and send it to > me? I'd like to see how the d80211 devices present themselves in sysfs.
The interesting part is under /sys/class/ieee80211/ and /sys/class/net/*/. Dan, feel free to ask me any questions about it. Suggestions are welcomed as well; I don't know what is useful for NetworkManager. > For _each_ actual network interface (as shown with iwconfig or ifconfig > -a), you'll need an entry in /sys/class/net/<device name> that contains > a "device" link, like so: > > | |-- net > | | |-- eth0 > | | | |-- addr_len > | | | |-- address > | | | |-- broadcast > | | | |-- carrier > | | | |-- device -> > ../../../devices/pci0000:00/0000:00:1e.0/0000:02:01.0 d80211 interfaces have also 'wiphy' symlink there, pointing to appropriate /sys/class/ieee80211/phyX device. > So, Jouni/Michael/Jiri; for d80211, how should SET_NETDEV_DEV get called > to assign each 'struct net_device' that d80211 creates with the > appropriate 'struct device' item so that the right sysfs links show up? The driver is responsible for setting it between ieee80211_alloc_hw and ieee80211_register_hw call. It has to be fixed in drivers. There is also a bug in d80211 - that pointer is not copied to other d80211 interfaces. I will fix that. Thanks for the report, Jiri -- Jiri Benc SUSE Labs _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
