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.
--=.a1bh0ytlOWXb2B
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
iEYEARECAAYFAjziex8ACgkQWEn3bOOMcurNiACgqOhb4MAibiALiXSAR49haOQa
XmIAoJIaNFb6zMN8OUUtcOR0k9un0J4m
=3lzP
-----END PGP SIGNATURE-----
--=.a1bh0ytlOWXb2B--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/