Skip to contentSkip to conversation

rt2x00/rt2500 support

DISCUSSION Jiri Benc 1 participant 1 message Jul 14, 2006 10 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): op.tcib4hf2r1uuuo@localhost

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): op.tcjngot1r1uuuo@localhost

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): op.tcjobte7r1uuuo@localhost

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): op.tclk82o1r1uuuo@localhost

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): op.tcm55p06r1uuuo@localhost

A message that is not in the archive (sent off-list or not yet received): [email protected]

Jiri Benc

author
#10 lore raw
Quoted 9 lines · Dan Williams

Ok; this is because d80211 (at least as included in rt2x00 driver) isn't setting the wireless stats handler, which I believe makes the device show up in /proc/net/wireless.
(...)

Jiri, what's involved here? The actual handler for get_wireless_stats is quite simple; see below. It returns a 'struct iw_statistics' for which it looks like all the information is available in d80211 elsewhere.

There is no specific reason, nobody just have cared so far.

I think HAL is broken if it requires /proc/net/wireless to recognize wireless device. There are better ways to achieve this (e.g. WE-specific ioctls).

I put this request to the TODO list; that means it will be fixed but not in a near future. Feel free to send a patch if you want it earlier.

Thanks,

Jiri

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

AFAIK, HAL looks at /proc/net/wireless, parses the interface names, and uses that to determine whether or not the device is a wireless device. Since it appears that /proc/net/wireless is eventually going away, HAL may need to get changed to recognize the /sys/class/ieee80211 directory that dscape presents, or something like that.

Signature · 2 lines
Jiri Benc
SUSE Labs