On Tue, 2005-15-11 at 08:17 +0100, Stefan Rompf wrote: > Am Dienstag 15 November 2005 03:43 schrieb jamal: > > I'll have more time for a comment this evening, but let me ask one question > until then: > > > 1) I dont think operstare_useroverride is needed. > > You said the same to Thomas on IFF_WAIT. Both operstate_useroverride and > IFF_WAIT exist to allow userspace 802.1X/wpa supplicant interaction. > > As I neither can read your mind nor want to guess it, can you outline your > ideas on supplicant interaction? One goal is to avoid changing existing > ethernet drivers. > > This is both important and invasive enough to be solved in issue #0. >
I apologize i did miss the discussion you guys had on why this would be different from say admin status changes or didnt understand what the locking issues are - so there may be a hole in my thinking. I didnt see this issue as any different than setting any other current netdevice flags which goes via dev_change_flags; i gave the example of IFF_UP in my email because it sets the dev->state (invoked via dev->open/close). In the case of user space 802.1x - i assume the user space code is going to drive the state transitions by changing the netdevice->flags, no? cheers, jamal - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
