From: Frans Pop <elendil@planet.nl>
To: saeed bishara <saeed.bishara@gmail.com>
Cc: Lennert Buytenhek <buytenh@wantstofly.org>,
linux-arm@vger.kernel.org, linux-ide@vger.kernel.org,
Mark Lord <liml@rtr.ca>, Nicolas Pitre <nico@cam.org>
Subject: Re: [regression] sata_mv: harddisk activity led no longer responsive on QNAP TS-109
Date: Fri, 29 Aug 2008 00:40:06 +0200 [thread overview]
Message-ID: <200808290040.08447.elendil@planet.nl> (raw)
In-Reply-To: <c70ff3ad0808281508q46ef7a8ahca5d0c2a325b2d2e@mail.gmail.com>
On Friday 29 August 2008, saeed bishara wrote:
> > $ sudo devmem2 0xf108002c w 1
> > /dev/mem opened.
> > Memory mapped at address 0x4001f000.
> > Value at address 0xF108002C (0x4001f02c): 0x0
> > Written 0x1; readback 0x1
> >
> > After that the HDD led does react again to io activity.
>
> do you mean it's blinking on io activity?
Yes.
> is it off when no io running?
No. It is on when there is no activity, but that is how it has always
been. Same as the LAN led which is also always on when there is a
connection and blinks on activity.
I don't know if that's how that's intended, but IMHO it makes sense for an
embedded device to have the led on by default to show the device is
"present and recognized" and to blink when there is activity.
Cheers,
FJP
next prev parent reply other threads:[~2008-08-28 22:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 8:45 [regression] sata_mv: harddisk activity led no longer responsive on QNAP TS-109 Frans Pop
2008-08-27 17:29 ` saeed bishara
2008-08-28 9:25 ` Frans Pop
2008-08-28 10:53 ` saeed bishara
2008-08-28 11:17 ` Frans Pop
2008-08-28 15:53 ` Grant Grundler
2008-08-28 17:11 ` Frans Pop
2008-08-28 17:26 ` Grant Grundler
2008-08-28 18:03 ` Frans Pop
2008-08-29 1:47 ` Harald Welte
2008-08-28 18:11 ` Lennert Buytenhek
2008-08-28 18:43 ` Frans Pop
2008-08-28 22:08 ` saeed bishara
2008-08-28 22:40 ` Frans Pop [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-26 9:24 Frans Pop
2008-08-26 10:25 ` Frans Pop
2009-01-24 14:57 ` Mark Lord
2008-08-26 14:03 ` Mark Lord
2008-08-27 14:56 ` Martin Michlmayr
2008-08-27 17:06 ` saeed bishara
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=200808290040.08447.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=buytenh@wantstofly.org \
--cc=liml@rtr.ca \
--cc=linux-arm@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=nico@cam.org \
--cc=saeed.bishara@gmail.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;
as well as URLs for NNTP newsgroup(s).