On Wed, 2015-12-16 at 05:35 -0800, Ben Greear wrote:
> Well, the old code used it as a key, and the old documentation used
> it as a key, so it is a bit of a regression to change the behaviour
> now.
But it's still used as a key, no? Just the value changed. If you treat
it as a key then you'd just have it for a frame incoming and outgoing?
> > I think this is pretty much a done deal by now though since I don't
> > really want to break wmediumd.
>
> It was not the only user-space to use the API :)
So you're saying you have code that broke? How did it break though, I
don't really see it yet. Can you explain?
> Well, that would be fine too. The nice thing about the
> address,though, is that you can query it as part of
> /sys/class/ieee..... and other already-implemented
> interfaces. Finding the radio-id would require new API in this case,
> which is a bit of work.
Well, it was always rather awkward since it was the *second* address :)
You can query the ID/index already through the netlink API, or even
from sysfs since the virtual device name is essentially
sprintf(name, "hwsim%d", idx)
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
