Messages in this thread | | | Date | Wed, 15 May 2002 10:13:29 -0500 | From | Tommy Reynolds <> | Subject | Re: Device driver question |
| |
Uttered "Joe deBlaquiere" <jadb@redhat.com>, spoke thus:
> How about just write a driver that responds to the interrupt, and write > a program that does a blocking read from the driver. The driver read > routine stuff the program on a wait queue... until... interrupt occurs, > wake up the program, program does exec(/sbin/halt) ?
Yup, that could work too. (Classic see-interrupt-from-user-space solution) It all depends on how urgently his embedded system needs to reboot. Choices abound for rebooting: the hard part is not rebooting until you want to reboot.[unhandled content-type:application/pgp-signature] | |