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 ([email protected]) Your ad here! Discount rates for OSS projects. Email me. aim/y!m:thinkinginbinary; icq:198113263; jabber:[email protected] msn: [email protected]; pgp: 0xAF5112C6
Attachment:
pgp3DqeOGSahG.pgp
Description: PGP signature
- Follow-Ups:
- Re: Ideas for more LED classes/triggers
- From: Pavel Machek <[email protected]>
- Re: Ideas for more LED classes/triggers
- Prev by Date: [RFC] patch [1/1] convert i386 summit subarch to use SRAT data for apicid_to_node
- Next by Date: Re: [PATCH] add synclink_gt custom hdlc idle
- Previous by thread: [RFC] patch [1/1] convert i386 summit subarch to use SRAT data for apicid_to_node
- Next by thread: Re: Ideas for more LED classes/triggers
- Index(es):
 |