public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Tuttle <thinkinginbinary@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Ideas for more LED classes/triggers
Date: Wed, 21 Jun 2006 22:20:06 -0400	[thread overview]
Message-ID: <20060622022006.GA17754@phoenix> (raw)

[-- 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 --]

             reply	other threads:[~2006-06-22  2:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22  2:20 Thomas Tuttle [this message]
2006-06-22 23:25 ` Ideas for more LED classes/triggers Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060622022006.GA17754@phoenix \
    --to=thinkinginbinary@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox