public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Mudama <edmudama@gmail.com>
To: Matt Domsch <matt_domsch@dell.com>
Cc: Adrian Yee <brewt-linux-kernel@brewt.org>,
	Robert Hancock <hancockr@shaw.ca>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: HDD LED doesn't light.
Date: Sun, 5 Sep 2004 18:50:13 -0600	[thread overview]
Message-ID: <311601c9040905175023ae280f@mail.gmail.com> (raw)
In-Reply-To: <20040831195902.GA3945@lists.us.dell.com>

On Tue, 31 Aug 2004 14:59:02 -0500, Matt Domsch <matt_domsch@dell.com> wrote:
> On Tue, Aug 31, 2004 at 12:44:08PM -0700, Adrian Yee wrote:
> > But this doesn't explain why I have two motherboards here where the HDD
> > activity LED does not light up in linux (for SATA drives) but does in
> > windows .  Note that it only starts working in windows *after* the
> > driver has loaded.
> 
> I've heard of implementations of the drive light on SATA where it is
> controlled through a general-purpose I/O pin somewhere else in the
> chipset.  If that's the case, then the Windows driver may well know
> how to drive the GPIO to indicate drive activity for you...

That would be my guess too.

This is all part of the initial hiccups in a brand new interface. 
Within another year or two, everything will stabilize out and work "as
intended" (crosses fingers)

--eric

  reply	other threads:[~2004-09-06  0:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.j6vg864.plk4g8@ifi.uio.no>
     [not found] ` <fa.e807bv7.klg10f@ifi.uio.no>
2004-08-25  3:40   ` HDD LED doesn't light Robert Hancock
2004-08-27 16:10     ` Eric Mudama
2004-08-31 19:44       ` Adrian Yee
2004-08-31 19:59         ` Matt Domsch
2004-09-06  0:50           ` Eric Mudama [this message]
2004-08-24  5:26 Ben Skeggs
2004-08-24 13:05 ` "Fernando O. Korndörfer"

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=311601c9040905175023ae280f@mail.gmail.com \
    --to=edmudama@gmail.com \
    --cc=brewt-linux-kernel@brewt.org \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt_domsch@dell.com \
    /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