All of lore.kernel.org
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: "Bloch, Jack" <Jack.Bloch@icn.siemens.com>
Cc: "'linux-kernel@vger.kernel.org.'" <linux-kernel@vger.kernel.org>
Subject: Re: Device driver question
Date: Wed, 15 May 2002 17:18:06 -0700	[thread overview]
Message-ID: <20020515171806.L840@pegasys.ws> (raw)
In-Reply-To: <180577A42806D61189D30008C7E632E87938E1@boca213a.boca.ssc.siemens.com>

On Wed, May 15, 2002 at 09:17:21AM -0400, Bloch, Jack wrote:
> I am relatively new to Linux (< 6 months). We have designed an embedded
> system (on compact PCI) running on a Pentium III 700Mhz cPCI machine. This
> machine supports upt to 6 cPCI boards for specific functions (this is our
> own HW). I have already written the device drivers for these boards and the
> system is running. I have a specific case where our HW can generate a
> special interrupt. In this case I simply want the ISR to halt the system
> (i.e. take the same action as if I typed halt from the command line). How
> can I from within my device driver cause a halt? Please CC me specifically
> on any replies.
> 
> Thanks in advance. 

I am assuming you are running more than just the kernel.
You could just post a signal to init (pid 1).
SIGINT would be a top candidate.

Take a look at powerd, init and inittab.


-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

      parent reply	other threads:[~2002-05-16  0:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 13:17 Device driver question Bloch, Jack
2002-05-15 13:36 ` Tommy Reynolds
2002-05-15 15:03   ` Joe deBlaquiere
2002-05-15 15:13     ` Tommy Reynolds
2002-05-15 15:16     ` Tommy Reynolds
2002-05-16  0:18 ` jw schultz [this message]

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=20020515171806.L840@pegasys.ws \
    --to=jw@pegasys.ws \
    --cc=Jack.Bloch@icn.siemens.com \
    --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 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.