From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: [PATCH 10/11] LED: Add IDE disk activity LED trigger
Date: Sat, 4 Feb 2006 10:54:14 +0100 [thread overview]
Message-ID: <20060204095414.GT18336@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0602011707460.22529@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On Wed, 2006-02-01 17:09:06 +0100, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> >Add an LED trigger for IDE disk activity to the IDE subsystem.
>
> Since I am not a real user of the led subsystem - what LED should be lit
> anyway? only the motherboard one does, and it seems to be connected
> directly to the IDE chip - I would want this as a compile-time option so I
> don't pay any extra time for any led stuff.
Well, look at PARISC. These machines do have a HDD LED, but it needs
to be manually driven by the I/O subsystem.
The same would be for PCMCIA-attached ATA drives, where some embedded
stuff has a HDD LED, which is GPIO-connected.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-02-04 9:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 13:41 Richard Purdie
2006-01-31 14:46 ` Bartlomiej Zolnierkiewicz
2006-01-31 16:21 ` Richard Purdie
2006-01-31 17:44 ` Bartlomiej Zolnierkiewicz
2006-01-31 20:29 ` Jens Axboe
2006-01-31 22:08 ` Benjamin Herrenschmidt
2006-01-31 23:39 ` Richard Purdie
2006-02-04 15:29 ` Richard Purdie
2006-01-31 20:35 ` Jens Axboe
2006-01-31 21:22 ` Jordan Crouse
2006-02-01 0:12 ` Matt Reimer
2006-02-02 1:32 ` Adrian Bunk
2006-01-31 22:03 ` [PATCH 10/11] " Richard Purdie
2006-02-02 11:07 ` Pavel Machek
2006-02-01 16:09 ` Jan Engelhardt
2006-02-04 9:54 ` Jan-Benedict Glaw [this message]
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=20060204095414.GT18336@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=bzolnier@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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
Powered by JetHome