[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101117105925.GC1574@ucw.cz>
Date: Wed, 17 Nov 2010 12:05:16 +0100
From: Pavel Machek <pavel@....cz>
To: Eric Cooper <ecc@....edu>
Cc: linux-kernel@...r.kernel.org, Richard Purdie <rpurdie@...ys.net>,
Greg KH <greg@...ah.com>
Subject: Re: [PATCH] add netdev led trigger
Hi!
> Add a netdev LED trigger for all Blinkenlights lovers...
> Originally taken from https://dev.openwrt.org/ticket/2776
> Slightly updated for 2.6.24 by Mickey Lauer <mickey@...nmoko.org>
> and for 2.6.36 by Eric Cooper <ecc@....edu>
Nice!
> +/*
> + * Configurable sysfs attributes:
> + *
> + * device_name - network device name to monitor
> + *
> + * interval - duration of LED blink, in milliseconds
This needs to go to Doc/ somewhere.
> + * mode - either "none" (LED is off) or a space separated list
> + * of one or more of:
> + * link: LED's normal state reflects whether the link is up (has carrier)
> + * or not
> + * tx: LED blinks on transmitted data
> + * rx: LED blinks on receive data
> + *
> + * Some suggestions:
> + *
> + * Simple link status LED:
> + * $ echo netdev >someled/trigger
> + * $ echo eth0 >someled/device_name
> + * $ echo link >someled/mode
> + *
> + * Ethernet-style link/activity LED:
> + * $ echo netdev >someled/trigger
> + * $ echo eth0 >someled/device_name
> + * $ echo "link tx rx" >someled/mode
One value per file?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists