wants source code of shutdown in C using interrupts ?

[Sweety]

hello,
Is there any code using interrupts .
bye

 

[Dan Pop]

Is there any code using interrupts .

There is no generic C code using interrupts. Such code is heavily
platform and implementation specific, so go to a newsgroup dedicated to
your platform.

Dan

 

[CBFalconer]

Is there any code using interrupts .

No. Not here.

 

[Keith Thompson]

hello,
Is there any code using inter

Not portably.

 

[red floyd]

Not portably.

Does that mean that when you interrupted Sweety, you didn't do it
portably?

 

[Keith Thompson]

Does that mean that when you interrupted Sweety, you didn't do it
portably?

No, it just means I didn't do it in code.

 

[Mark McIntyre]

hello,
Is there any code using interrupts .

You can't do this in Standard C. Didn't someone already tell you that?

Please go to a group specialising in your hardware, and ask there.

 

[Keith Thompson]

You can't do this in Standard C. Didn't someone already tell you that?

Please go to a group specialising in your hardware, and ask there.

Now that I think about it, this might refer to the facilities in
<signal.h>. (Is there a distinction between "signals" and
"interrupts"?)

To the original poster: Read your system's documentation on the
"signal" function. If this is what you're looking for, and you still
have questions after reading the documentation, come back with a more
specific question.

 

[Paul]

Now that I think about it, this might refer to the facilities in
<signal.h>. (Is there a distinction between "signals" and
"interrupts"?)

To the original poster: Read your system's documentation on the
"signal" function. If this is what you're looking for, and you still
have questions after reading the documentation, come back with a more
specific question.

Hello Sweety, we don't do home work or office assignments here. It
would be elegant that you hire some one for that.

-Paul.

 

[Dan Pop]

Now that I think about it, this might refer to the facilities in
<signal.h>. (Is there a distinction between "signals" and
"interrupts"?)

Yup, a fundamental one: an signal handler is an ordinary C function,
treated by the compiler like any other function (the compiler has no
idea it is compiling a signal handler) while an interrupt handler must
save *all* the CPU state it is disturbing upon entry and restore it
before returning. On most CPUs, it must also reenable the interrupt
that invoked it, usually using a different kind of return instruction
("return from interrupt" instead of "return from subroutine").

The declaration of a signal handler is:

void handler(int);

while the typical declaration of an interrupt handler is something like

void interrupt inthandler(void);

where the "interrupt" extension tells the compiler to add all the code
for performing the actions described above.

As interrupt handlers belong to the OS kernel, the need for such an
extension is limited to freestanding implementations and to very
primitive hosted platforms, like MSDOS, where there is no difference
between user code and OS code.

Because the serial port drivers of MSDOS are not interrupt driven,
any user program that needs *reliable* serial communication MUST
provide its own interrupt handler(s) for the serial port(s) it uses.
Easily done in C, because most MSDOS compilers provide the "interrupt"
extension described above along with library support for accessing the
I/O ports.

Dan