10-26-2015
The IBM PC has had a pulse generator/timer from the beginning (which also used to drive the PC speaker.) In the olden days, before LSI, it was its own separate chip attached to the data bus. It was very flexible, but generally configured to generate hardware interrupts at 18ms intervals. This hardware interrupt is an IRQ, pretty much hardwired into the CPU, causing it to stop whatever it's doing and jump to a hardwired location in RAM. The OS can do whatever it pleases with that interrupt by putting code in that location.
The hardware is going to be very different on non-PC architectures but the idea is the same, a pulse generator wired to the CPU.
If you're really curious about historical PC architecture, and have a bent towards electronics, I suggest
The 8088 book. The 8088 as much as anything else is responsible for why the PC is the way it is.
Last edited by Corona688; 10-26-2015 at 04:21 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Anyone ever write a unix clock program that display the clock out in 7 segment LCD style.
I tried doing one with case statements:
!/usr/bin/ksh
clock=`date`
case $clock in
#This prints out the number 0
0)
echo " -"
echo "| |"
echo
echo "| |"
echo " -"
;;
... (4 Replies)
Discussion started by: Astudent
4 Replies
2. UNIX for Dummies Questions & Answers
This is on our Ultra 5/10 Sparc with Solaris 9.
I need to store the following (stty) keys in the .profile and /etc/profile files as
shown here.
erase "Back Space Key"
Interrupt "Ctrl + C"
I need the exact syntax/procudure as I have to set these two keys whenever I login to the terminal... (1 Reply)
Discussion started by: chrs0302
1 Replies
3. UNIX for Dummies Questions & Answers
hi all...
how i can sincronization clock solaris server with windows server....both servers i connected in the same network...
thank you....
Best Regards... (4 Replies)
Discussion started by: chanfle
4 Replies
4. UNIX for Dummies Questions & Answers
hello all
since a process running in kernel mode cannnot be preempted by any other process what would be the status of Timer interrupt that occurs when the time quantum of a process is elapsed?
thanks (2 Replies)
Discussion started by: compbug
2 Replies
5. UNIX for Dummies Questions & Answers
Hey everyone! Can someone help me, i need to make a program using awk, that displays the current time (hh/mm/ss), i would really apreciate it! Thanks!
Alex. (4 Replies)
Discussion started by: alex_omul
4 Replies
6. Shell Programming and Scripting
Is it possible to sent a ^C interrupt via the command line? For example if I want to tail a log for 10 minutes at a time, kill the tail and then start it again is there a way to go about that? I would imagine there would be some way to do it by finding and killing the PID, but I'm curious if... (2 Replies)
Discussion started by: DeCoTwc
2 Replies
7. UNIX for Dummies Questions & Answers
hi can any one guide me on how to display real time of a clock in unix for every 60 seconds (2 Replies)
Discussion started by: ramnadh_babu
2 Replies
8. UNIX for Advanced & Expert Users
I receive the following warning messages on a very new machine which has FreeBSD 8.1 x64 installed on it:
Interrupt storm detected on "irq 20" throttling interrupt source
It is unclear what this means and what its origins are (motherboard? CPU? RAM?).
I can start the desktop and the message is... (4 Replies)
Discussion started by: figaro
4 Replies
9. UNIX for Advanced & Expert Users
Hi, all:
Is there any shell command to show which interrupt handler handle which interrupt number in the system?
li,kunlun (5 Replies)
Discussion started by: liklstar
5 Replies
10. UNIX for Advanced & Expert Users
Hi, I've got an issue which I've been 'google-fu'ing without much luck. We have a legacy program which has been plagued by an issue for a long time and I've been tasked to investigate/fix.
The program uses XMotif2.1 (required due to dependency on an old GUI designer) and runs on a RHEL7... (4 Replies)
Discussion started by: altrefrain
4 Replies
LEARN ABOUT MINIX
ddi_intr_get_supported_types
ddi_intr_get_supported_types(9F) ddi_intr_get_supported_types(9F)
NAME
ddi_intr_get_supported_types - return information on supported hardware interrupt types
SYNOPSIS
#include <sys/types.h>
#include <sys/conf.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
int ddi_intr_get_supported_types(dev_info_t *dip, int *typesp);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
dip Pointer to dev_info structure
typesp Pointer to supported interrupt types
The ddi_intr_get_supported_types() function retrieves the interrupt types supported by a particular hardware device and by the system soft-
ware. Upon successful return, the supported types are returned as a bit mask in the integer pointed to by the typesp argument. See
<sys/ddi_intr.h> for a list of interrupts that can be returned by a hardware device.
For PCI devices that support MSI and/or MSI-X based hardware, this interface returns only the interrupt types that are supported by all the
hardware in the path to the hardware device.
An interrupt type is usable by the hardware device if it is returned by the ddi_intr_get_supported_types() function. The device driver can
be programmed to use one of the returned interrupt types to receive hardware interrupts.
The ddi_intr_get_supported_types() function returns:
DDI_SUCCESS On success.
DDI_EINVAL On encountering invalid input parameters.
DDI_INTR_NOTFOUND Returned when the hardware device is found not to support any hardware interrupts.
CONTEXT
The ddi_intr_get_supported_types() function can be called from user or kernel non-interrupt context.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
pci(4), attributes(5), pcmcia(7D), sysbus(4), ddi_intr_add_handler(9F), ddi_intr_alloc(9F), ddi_intr_enable(9F)
The ddi_intr_get_supported_types() function can be called by the device driver even at any time if the driver has added an interrupt han-
dler for a given interrupt type.
Soft interrupts are always usable and are not returned by this interface.
Any consumer of this interface should verify that the return value is not equal to DDI_SUCCESS. Incomplete checking for failure codes could
result in inconsistent behavior among platforms.
07 Apr 2005 ddi_intr_get_supported_types(9F)