Ideas for more LED classes/triggers

Ideas for more LED classes/triggers

[Thomas Tuttle]

[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]

Hey.

I saw the new LED subsystem in 2.6.17.1 (maybe earlier, but maybe it's
been expanded?) and I thought of some ideas for more classes and
triggers.

Classes:
	Keyboard LED's
	Various laptop LED's (Asus, others)
Triggers:
	CPU busy (could include varieties such as user, system, IO wait, etc.
	network device transmit/receive
	wireless device state (associated or not)
	per-disk read/write
	RAID array status

I'm willing to try to write some of these, but I've never worked on any
kernel before, and I'm pretty new to C.  If someone's willing to answer
a few annoying questions as I go, I could probably get some of it done.

Anyway, the LED subsystem looks really cool.  I've always wanted the
kernel to be able to control my blinkenlights instead of having to write
shell scripts.  Keep up the good work!

-- 
Thomas Tuttle (thinkinginbinary@gmail.com)
Your ad here! Discount rates for OSS projects. Email me.
aim/y!m:thinkinginbinary; icq:198113263; jabber:thinkinginbinary@jabber.org
msn: thinkinginbinary@hotmail.com; pgp: 0xAF5112C6

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: Ideas for more LED classes/triggers

[Pavel Machek]

Hi!

> I saw the new LED subsystem in 2.6.17.1 (maybe earlier, but maybe it's
> been expanded?) and I thought of some ideas for more classes and
> triggers.
> 
> Classes:
> 	Keyboard LED's

...are handled by input subsystem. Leave them alone for now.

> 	Various laptop LED's (Asus, others)

Yes, this would be very welcome.

> Triggers:
> 	CPU busy (could include varieties such as user, system, IO
> > wait, etc.

That one would be nice.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html