|
|
@@ -18,7 +18,7 @@
|
|
|
|
|
|
<h2 class='titleHead'>The Linux Kernel Module Programming Guide</h2>
|
|
|
<div class='author'><span class='ecrm-1200'>Peter Jay Salzman, Michael Burian, Ori Pomerantz, Bob Mottram, Jim Huang</span></div><br />
|
|
|
-<div class='date'><span class='ecrm-1200'>September 23, 2022</span></div>
|
|
|
+<div class='date'><span class='ecrm-1200'>October 4, 2022</span></div>
|
|
|
|
|
|
|
|
|
|
|
|
@@ -4904,7 +4904,7 @@ requests. Another job, which is every bit as important, is to speak to the hardw
|
|
|
connected to the machine.
|
|
|
</p><!-- l. 1805 --><p class='indent'> There are two types of interaction between the CPU and the rest of the
|
|
|
computer’s hardware. The first type is when the CPU gives orders to the hardware,
|
|
|
-the order is when the hardware needs to tell the CPU something. The second, called
|
|
|
+the other is when the hardware needs to tell the CPU something. The second, called
|
|
|
interrupts, is much harder to implement because it has to be dealt with when
|
|
|
convenient for the hardware, not the CPU. Hardware devices typically have a very
|
|
|
small amount of RAM, and if you do not read their information when available, it is
|
jserv