Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Alexandru Pirvulescu" <Pirvulescu_Alexandru@telemobil.ro>
To: "Alex deVries" <adevries@linuxcare.com>,
	"Grant Grundler" <grundler@cup.hp.com>
Cc: <parisc-linux@puffin.external.hp.com>
Subject: Re: [parisc-linux] case LEDs
Date: Wed, 22 Nov 2000 09:36:58 +0200	[thread overview]
Message-ID: <006001c05456$febb1cd0$6811620a@sigxcpu> (raw)
In-Reply-To: 3A1B2F27.D08EC2AF@linuxcare.com

I think that the heartbeat LED is software because it starts with the kernel
boot and if the kernel stops the LED stops
blinking too. Is better to implement a software monitoring tool because you
have to watch the software for hanging.

Alex

PS. There is a function in the kernel source in
linux/arch/parisc/kernel/process.c named machine_heartbeat(). Any connection
with the heartbeat from the chassis?


----- Original Message -----
From: "Alex deVries" <adevries@linuxcare.com>
To: "Grant Grundler" <grundler@cup.hp.com>
Cc: "Alexandru Pirvulescu" <Pirvulescu_Alexandru@telemobil.ro>;
<parisc-linux@puffin.external.hp.com>
Sent: Wednesday, November 22, 2000 4:27 AM
Subject: Re: [parisc-linux] case LEDs


> Grant Grundler wrote:
> > Yes.
> > I was already asked this weekend to dig up technical info on LED
> > and soft power control. I guess this is my reminder to do that. :^)
>
> Isn't there a PDC call (pdc_chassis?) to do this?  Or is the heartbeat
> LED done by hardware?
>
> - Alex
>
> --
> Alex deVries, Principal Solutions Architect, The Puffins at Linuxcare
> 613.562.2759 tel
> alex@linuxcare.com, http://www.linuxcare.com/
> Linuxcare, Support for the revolution.
>
>

  parent reply	other threads:[~2000-11-22  7:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-21 18:49 [parisc-linux] case LEDs Alexandru Pirvulescu
2000-11-21 18:55 ` Grant Grundler
2000-11-22  2:27   ` Alex deVries
2000-11-22  5:32     ` Bas Valkema
2000-11-22  7:36     ` Alexandru Pirvulescu [this message]
2000-11-27  6:12     ` Grant Grundler

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='006001c05456$febb1cd0$6811620a@sigxcpu' \
    --to=pirvulescu_alexandru@telemobil.ro \
    --cc=adevries@linuxcare.com \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@puffin.external.hp.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