From: Mike Jagdis <jaggy@purplet.demon.co.uk>
To: Philip Graham Willoughby <pgw99@doc.ic.ac.uk>
Cc: Kent Borg <kentborg@borg.org>, John Bradford <john@grabjohn.com>,
linux-kernel@vger.kernel.org
Subject: Re: PATCH : LEDs - possibly the most pointless kernel subsystem ever
Date: Wed, 30 Jul 2003 22:44:33 +0100 [thread overview]
Message-ID: <3F283C41.1070301@purplet.demon.co.uk> (raw)
In-Reply-To: <20030729214404.GB21517@bodmin.doc.ic.ac.uk>
Strangely (and perhaps sadly) enough a couple of years ago I wrote
an LED, um, "pattern generator" because, ah, someone insisted that
it would be "really cool" if the kit we were (going to) build had
a Knight Rider / Cylon "sweep"...
It had drivers for parport (I did initial development using LEDs
hanging off the back of a Thinkpad), a 5.25" SBC made by WinEnt
(LEDs on the PIIX4 GPO pins), an i2c I/O chip (used in the semi-custom
PC we eventually chose), and a test stub that just output bit patterns.
Since running patterns from user space is anti-social (and it's
difficult to get the timing good enough) there was a kernel space
"interpreter" that you could load scripts in to. Sweeps, scans,
blinks, ping-pong etc. Plus you could have multiple scripts with
LEDs "owned" by different scripts so you could do knock outs,
fill ins etc. And, of course, change scripts to reflect system
status on the fly :-)
Ok, it was a sunday afternoon hack so I got carried away a bit...
Like I say it was a couple of years ago so it probably needs some
work. But I'm quite happy to mail it to anyone that's curious. And
if any hardware manufacturers still think sweeping LEDs are cool
and trendy they're welcome to talk to me. Discreetly :-).
Mike
--
Mike Jagdis
Eris Associates Limited
next prev parent reply other threads:[~2003-07-30 21:44 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 [this message]
2003-07-30 12:15 ` Pavel Machek
-- 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=3F283C41.1070301@purplet.demon.co.uk \
--to=jaggy@purplet.demon.co.uk \
--cc=john@grabjohn.com \
--cc=kentborg@borg.org \
--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®