|
Lines 49-55
Link Here
|
| 49 |
changes.</para> |
49 |
changes.</para> |
| 50 |
|
50 |
|
| 51 |
<para>The kld interface is used through the following |
51 |
<para>The kld interface is used through the following |
| 52 |
administrator commands : |
52 |
privileged commands : |
| 53 |
|
53 |
|
| 54 |
<itemizedlist> |
54 |
<itemizedlist> |
| 55 |
<listitem><simpara><command>kldload</command> - loads a new kernel |
55 |
<listitem><simpara><command>kldload</command> - loads a new kernel |
|
Lines 123-130
Link Here
|
| 123 |
<para>Simply running <command>make</command> with this makefile |
123 |
<para>Simply running <command>make</command> with this makefile |
| 124 |
will create a file <filename>skeleton.ko</filename> that can |
124 |
will create a file <filename>skeleton.ko</filename> that can |
| 125 |
be loaded into your system by typing : |
125 |
be loaded into your system by typing : |
| 126 |
<screen> &prompt.root |
126 |
<screen>&prompt.root; <userinput>kldload -v ./skeleton.ko</userinput></screen> |
| 127 |
kldload -v ./skeleton.ko</screen> |
|
|
| 128 |
</para> |
127 |
</para> |
| 129 |
</sect2> |
128 |
</sect2> |
| 130 |
</sect1> |
129 |
</sect1> |
|
Lines 138-144
Link Here
|
| 138 |
accesses a device node. The <command>/dev/MAKEDEV</command> |
137 |
accesses a device node. The <command>/dev/MAKEDEV</command> |
| 139 |
script makes most of the device nodes for your system but if you |
138 |
script makes most of the device nodes for your system but if you |
| 140 |
are doing your own driver development it may be necessary to |
139 |
are doing your own driver development it may be necessary to |
| 141 |
create your own device nodes with <command>mknod</command> |
140 |
create your own device nodes with <command>mknod</command>. |
| 142 |
</para> |
141 |
</para> |
| 143 |
|
142 |
|
| 144 |
<sect2> |
143 |
<sect2> |
|
Lines 146-152
Link Here
|
| 146 |
|
145 |
|
| 147 |
<para>The <command>mknod</command> command requires four |
146 |
<para>The <command>mknod</command> command requires four |
| 148 |
arguments to create a device node. You must specify the name |
147 |
arguments to create a device node. You must specify the name |
| 149 |
of this device node, the type of device, the major number of |
148 |
of the device node, the type of device, the major number of |
| 150 |
the device, and the minor number of the device.</para> |
149 |
the device, and the minor number of the device.</para> |
| 151 |
</sect2> |
150 |
</sect2> |
| 152 |
|
151 |
|
|
Lines 158-164
Link Here
|
| 158 |
This eliminates the problems of potentially having a device |
157 |
This eliminates the problems of potentially having a device |
| 159 |
driver without a static device node, or a device node without |
158 |
driver without a static device node, or a device node without |
| 160 |
an installed device driver. Devfs is still a work in |
159 |
an installed device driver. Devfs is still a work in |
| 161 |
progress, but it is already working quite nice.</para> |
160 |
progress, but it is already working quite nicely.</para> |
| 162 |
</sect2> |
161 |
</sect2> |
| 163 |
|
162 |
|
| 164 |
</sect1> |
163 |
</sect1> |
|
Lines 337-349
Link Here
|
| 337 |
<para>To install this driver you will first need to make a node on |
336 |
<para>To install this driver you will first need to make a node on |
| 338 |
your filesystem with a command such as : </para> |
337 |
your filesystem with a command such as : </para> |
| 339 |
|
338 |
|
| 340 |
<screen>&prompt.root mknod /dev/echo c 33 0</screen> |
339 |
<screen>&prompt.root; <userinput>mknod /dev/echo c 33 0</userinput></screen> |
| 341 |
|
340 |
|
| 342 |
<para>With this driver loaded you should now be able to type |
341 |
<para>With this driver loaded you should now be able to type |
| 343 |
something like :</para> |
342 |
something like :</para> |
| 344 |
|
343 |
|
| 345 |
<screen>&prompt.root echo -n "Test Data" > /dev/echo |
344 |
<screen>&prompt.root; <userinput>echo -n "Test Data" > /dev/echo</userinput> |
| 346 |
&prompt.root cat /dev/echo |
345 |
&prompt.root; <userinput>cat /dev/echo</userinput> |
| 347 |
Test Data</screen> |
346 |
Test Data</screen> |
| 348 |
|
347 |
|
| 349 |
<para>Real hardware devices in the next chapter..</para> |
348 |
<para>Real hardware devices in the next chapter..</para> |