From: Christian Kroll <christian.kroll@bglug.org>
To: Aric Cyr <acyr@alumni.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_sil 3112 activity LED patch
Date: Fri, 15 Jul 2005 12:34:36 +0200 [thread overview]
Message-ID: <1121423676.4838.23.camel@localhost> (raw)
In-Reply-To: <20050715055743.GA8041@alumni.uwaterloo.ca>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Fri, Jul 15, 2005 at 02:57PM +0900, Aric Cyr wrote:
> Out of curiosity, did the LED
> usage change at all before and after the patch, or was it totally
> unaffected. I would guess the latter.
It was totally unaffected. If the LED is turned on by the BIOS (while it
examines the bus at boot time), it remains on as long as Linux is
running. If it isn't turned on by the BIOS (Silicon Image's reference
BIOS), it doesn't light up under Linux as well.
> Thanks, I will. I have emailed Silicon Image in the (slim) chance
> that they will provide me with the information I require. If they
> come through then I might be able to whip something up and have you
> test it.
Thanks for looking into this!
--
Christian Kroll <christian.kroll@bglug.org>
GnuPG Fingerprint: DA5D 5BFA 5C95 FD09 2A72 517E 10CB DCD5 71ED 7E35
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-15 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 2:15 sata_sil 3112 activity LED patch Christian Kroll
2005-07-15 5:57 ` Aric Cyr
2005-07-15 10:34 ` Christian Kroll [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-06 2:51 Aric Cyr
2005-07-06 15:07 ` Jeff Garzik
2005-07-07 12:47 ` Jens Axboe
2005-07-07 14:23 ` Aric Cyr
2005-07-07 15:11 ` Jens Axboe
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=1121423676.4838.23.camel@localhost \
--to=christian.kroll@bglug.org \
--cc=acyr@alumni.uwaterloo.ca \
--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