[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200703012241.49165.florian.fainelli@int-evry.fr>
Date: Thu, 1 Mar 2007 22:41:48 +0100
From: Florian Fainelli <florian.fainelli@...-evry.fr>
To: netdev@...r.kernel.org, Richard Purdie <rpurdie@...ys.net>
Subject: Network activity LED trigger
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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists