From: Thomas Graf <[EMAIL PROTECTED]>
Date: Thu, 31 Aug 2006 23:21:29 +0200
> Additionaly exports the following information when providing
> the list of registered generic netlink families:
> - protocol version
> - header size
> - maximum number of attributes
> - list of available operatio
jamal wrote:
> Could you point me to it? I can look at it over the weekend.
I posted it here on netdev, look for nl80211.
> It may be we need to add another feature to genl to accomodate this.
> Example by setting a flag to indicate supportability. However, it does
> sound like this is something
On Fri, 2006-01-09 at 14:25 +0200, Johannes Berg wrote:
> On Fri, 2006-09-01 at 08:22 -0400, jamal wrote:
>
> > Sorry, I havent had time to look at that code (is it in Daves tree?);
>
> No, it's not in any tree yet.
>
Could you point me to it? I can look at it over the weekend.
> > if
> > i
On Fri, 2006-09-01 at 08:22 -0400, jamal wrote:
> Seems you may be talking about capabilities more than filtering?
yes, I had sort of thought filtering would be that, but now that you say
it I get the point :)
> Sorry, I havent had time to look at that code (is it in Daves tree?);
No, it's not
On Thu, 2006-08-31 at 17:46 -0400, jamal wrote:
> I think it would be valuable to specify a set of flags for filtering
> what gets sent to user space instead of unconditionally.
>
> Example,
> filter level 0:
> - what we have before your patch
> filter level 1:
> - protocol version
> - hea
Useful stuff. There are things along these lines that i have been
contemplating myself.
I think it would be valuable to specify a set of flags for filtering
what gets sent to user space instead of unconditionally.
Example,
filter level 0:
- what we have before your patch
filter level 1:
- p
Additionaly exports the following information when providing
the list of registered generic netlink families:
- protocol version
- header size
- maximum number of attributes
- list of available operations including
- id
- flags
- avaiability of policy and doit/dumpit funct
