From: "Herbert Pötzl" <herbert@13thfloor.at>
To: Pavel Machek <pavel@suse.cz>
Cc: John Bradford <john@grabjohn.com>,
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 20:56:59 +0200 [thread overview]
Message-ID: <20030730185659.GA7260@www.13thfloor.at> (raw)
In-Reply-To: <20030730174457.GI10276@atrey.karlin.mff.cuni.cz>
On Wed, Jul 30, 2003 at 07:44:57PM +0200, Pavel Machek wrote:
> Hi!
>
> > > But this kind of blinkenlights needed pretty fast LEDs. (At 486 time
> > > I decided that parport on ISA is fast enough..)
> >
> > I'll buy some LEDs and build a parallel port connected LED panel
> > tomorrow... Do you think the overhead of driving the LEDs would have
> > too much of a negative effect on system performance? If so, or if
> > we
>
> I'm not sure. At 486 days I was pretty sure it did not matter. These
> days you might get 10% slowdown on some microbenchmark, or something
> like that. I do not think it can slow down common tasks.
>
> My construction of LED lights is extremely flaky, and I'm afraid of
> burning printer port. At 486 days ports were expected to survive such
> abuse. Not sure if todays EPP/wtf ports can handle that.
parport uses 5V (actually a little less) so if you
use normal (not extra super duper bright) leds and
put a 1kOhm resistor in front of each led, then it
will drain 5mA per led, which gives a total of 40mA
for eight leds (for example)
now for the parport: depending on the technology
and the age of the circuit, it provides between
2 and 14mA output at >2.4V (the led usually requires
less than 1.5V to operate) so this would be within
the range ... but, if you want either extra brightness
or extra security, you could provide +5V and use
the outputlines as sink, which then is between
15 and 25mA ...
anyway, parport should be short circuit safe, so
the worst what could happen is, that the leds are
not working ;) ...
HTH,
Herbert
PS: I usually use 220Ohm and no external power ...
> --
> Horseback riding is like software...
> ...vgf orggre jura vgf serr.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-07-30 18:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 18:50 John Bradford
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 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
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=20030730185659.GA7260@www.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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®