lkml.org 
[lkml]   [2002]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 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]
\
 
 \ /
  Last update: 2005-03-22 13:26    [W:0.071 / U:1.600 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site