So I haven't seen a response from you guys: I have no major objections to this. However, a few things: 1) are you planning to add support for this into a kernel driver at all, anyway? 2) are you planning to have a driver upstream that contains the now necessary parsing? Depending on the answers, I suppose we could/should merge this: no * : don't merge yes no : merge yes yes: don't merge, put parsing into cfg80211 I guess? We don't have to always draw a too rigid line for non-upstream things, but it's still disappointing that you keep proposing things that are only used for non-upstream drivers. johannes
