Hi All, Some more thoughts. The IDE activity LED trigger is currently triggered when a function is called in the IDE writing/reading routines.
In a similar way, we could call the trigger function in net/core/dev.c in netif_receive_skb and netif_rx ? I was also thinking that some network NIC already have LEDs, so it is not necessary for those models to "overload" the user with lights everywhere. Regars, Florian Le jeudi 1 mars 2007, Florian Fainelli a écrit : > Hi All, > > I have been talking a bit with Richard, who is the LED API maintainer, and > a LED trigger based on network activity would be something great. > > There are somethings that concern the network stack : > > - should we specify if the network driver is allowed to contribute to > the LED activity, just like it is done for random generation, at compile > time > > - I would like to trigger the LED based on one or several network > interfaces, maybe specify via sysfs which interface triggers which LED, > and also maybe differentiate the layer-2 activity from the layer-3 > activity for instance > > - A led driver could by default be bound to a network driver, or an > interface name > > As it could be very intrusive in the network stack, you might want to > specify a bit more how you imagine a network activity trigger. > > Thanks - 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
