mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org, pgw99@doc.ic.ac.uk
Subject: Re: PATCH : LEDs - possibly the most pointless kernel subsystem ever
Date: Wed, 30 Jul 2003 14:15:54 +0200	[thread overview]
Message-ID: <20030730121554.GG2601@openzaurus.ucw.cz> (raw)
In-Reply-To: <200307291915.h6TJF6YB000421@81-2-122-30.bradfords.org.uk>

Hi!

> I haven't had chance to test this yet, but I really like the idea - by
> an amasing co-incidence, I was actually thinking about the possibility
> of doing a parallel port connected front panel earlier today!
> 
> Does anybody have any suggestions for recommended standard uses for
> parallel port connected LEDs?
> 
> Disk spinning up/disk ready
> Root login active
> 
> Any other suggestions?

At one point I had 12 LEDs on parport. LEDs were fast enough to be drive at interrupt entry/exit.
They were: 
Yellow not idle task
Green interrupt
" bh
" pagefault
Red lowest 4 bits of PID
Red, low intensity serial i/o
" network i/o

It actually looked very good. Glow of interrupt led
told you interrupt load, pid LEDs told you about what kind of load
it is experiencing (you could tell shell script from make and from computation, and
if machine hard-died, you at least knew if it
was interrupt or process context).
But this kind of blinkenlights needed pretty fast LEDs. (At 486 time I decided that parport on ISA is fast enough..)
				Pavel
-- 
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...


  parent reply	other threads:[~2003-07-30 12:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 19:15 John Bradford
2003-07-29 19:51 ` Tim Hockin
2003-07-29 20:09 ` Joel Jaeggli
2003-07-29 21:20 ` Kent Borg
2003-07-29 21:44   ` Philip Graham Willoughby
2003-07-30 21:44     ` Mike Jagdis
2003-07-30 12:15 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-30 18:50 John Bradford
2003-07-30 16:08 John Bradford
2003-07-30 17:44 ` Pavel Machek
2003-07-30 18:50   ` Marc Giger
2003-07-30 19:05     ` Herbert Pötzl
2003-07-30 22:22     ` Brian McGroarty
2003-07-30 18:56   ` Herbert Pötzl
2003-07-30 19:02     ` Pavel Machek
2003-07-30 19:06     ` Marc Giger
2003-07-30 19:16       ` Herbert Pötzl
2003-07-31  8:31 ` jw schultz
2003-07-30 15:50 John Bradford
2003-07-30 12:27 "Andrey Borzenkov" 
2003-07-29 20:38 John Bradford
2003-07-29 20:37 ` Andries Brouwer
2003-07-29 21:34   ` Philip Graham Willoughby
2003-07-29 20:40 ` Randolph Bentson
2003-07-29 21:15   ` Ryan Flowers
2003-07-29 20:43 ` Eli Carter
2003-07-30  6:09   ` Tomas Szepe
2003-07-30  6:37   ` Helge Deller
2003-07-29 15:17 Philip Graham Willoughby
2003-07-29 18:00 ` Pavel Machek
2003-07-30 11:45   ` Jamey Hicks
2003-07-30 12:27     ` Pavel Machek
2003-07-30  6:36 ` CaT
2003-07-30 13:00   ` Andries Brouwer
2003-07-30 13:20     ` CaT
2003-07-30 23:28 ` Greg KH

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=20030730121554.GG2601@openzaurus.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgw99@doc.ic.ac.uk \
    /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

all inboxes | Powered by JetHome®