From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: sparclinux@vger.kernel.org
Subject: Re: [sparc32] Kernel module to control front LED
Date: Wed, 28 Sep 2005 00:48:47 +0000 [thread overview]
Message-ID: <39e6f6c705092717484d6cb38@mail.gmail.com> (raw)
In-Reply-To: <20050826192113.02c642a4@huginn.midgard.yggdrasill>
On 9/27/05, Eric Brower <ebrower@gmail.com> wrote:
> On 9/27/05, David S. Miller <davem@davemloft.net> wrote:
> > From: acme@ghostprotocols.net (Arnaldo Carvalho de Melo)
> > Date: Tue, 27 Sep 2005 18:18:59 -0300
> >
> > > Is this in any way similar to what the guardian service processor in
> > > PARISC64 machines provide? I.e. one can see what the leds in the machine
> > > front panel remotely :-)
> >
> > Nah, this is just a physical single LED on the front panel of
> > the machine that you can toggle on an off by flipping a bit
> > in an I/O register.
>
> Arnaldo,
>
> Certain Sun systems do have this sort of feature-- it has been called
> Lights Out Management (LOM), Remote System Control (RSC) and the like.
> Basically, proprietary, pre-IPMI management controllers of varying
> functionality. As DaveM mentions, this isn't it, though... :)
>
> There is ongoing work to support such controllers (e.g. on Sun E250
> and E450 servers).
Thanks for the information! I have to find time to get my SS 10 back to life and
use it to test my kernel hacks :-)
BTW, is 2.6.latest working well on Sparcstation 10s?
- Arnaldo
next prev parent reply other threads:[~2005-09-28 0:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 17:21 [sparc32] Kernel module to control front LED Metalhead
2005-09-27 20:28 ` David S. Miller
2005-09-27 21:18 ` Arnaldo Carvalho de Melo
2005-09-27 22:09 ` David S. Miller
2005-09-28 0:39 ` Eric Brower
2005-09-28 0:48 ` Arnaldo Carvalho de Melo [this message]
2005-09-28 4:38 ` David S. Miller
2005-09-28 7:09 ` Christian Joensson
2005-09-28 14:28 ` Metalhead
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=39e6f6c705092717484d6cb38@mail.gmail.com \
--to=acme@ghostprotocols.net \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.