|[Home] [Credit Search] [Category Browser] [Staff Roll Call]||The LINUX.COM Article Archive|
|Originally Published: Monday, 30 April 2001||Author: Cherry George Mathew|
|Published to: featured_articles/Featured Articles||Page: 1/5 - [Printable]|
Creating a Kernel Driver for the PC Speaker
Take a jaunty look at the basics of driver development as Cherry George Mathew guides us through the process of creating a driver for the PC speaker under Linux.
|Page 1 of 5 >>|
I decided to make the PC speaker (That invisible little thing under the PC hood that beeps) spew rock music. I wanted it to play real music. I couldn't bother to write all the code from scratch, to decode MP3, etc. So I got a little lazy and decided to play games with the most documented, most sophisticated OS ever: Linux.
How do you go about it, when you are new to a city and want to get from point 'a' to 'b' with confidence? I'd take a deep breath and start walking downtown. I'd start gleaning information and discovering places. Foolhardy? Just try it in the city of the Linux kernel. It's a maze of code, a dizzy labyrinth of cross-linked directories and makefiles. When I started off, I knew that this was going to be a long project. But I had the 'staff' of DOS and the 'rod' of "Peter Norton's guide to the IBM PC and Compatibles" with me to lend me courage. So off I strode with my chin in the air, and ready to take on the worst d(a)emons.
The PC-speaker driver patches that are available for download from MITs FTP site require you to have the kernel recompiled if they are to work. When I started off, I was ready to play foul, and get quick results. That's why you'll find inline assembly in the code. Anyways, here is how it works...
The PC speaker: A backgrounder.
The internal speaker is tied to the buffered output of the 8254 timer chip on all PCs. The output of the 8254 timer is further latched through the integrated system peripheral chip, through port 61h. A little ASCII art should help, I think. Here goes:
PIC stands for programmable interrupt controller
The base clock frequency of the 8254 is 1193180Hz which is 1/4 the standard NTSC frequency, incidentally. The counters have the values of the divisors, which, roughly speaking, are used to divide the base frequency. Thus the output of channel 0 will be at a frequency of 1193180Hz if counter0=1, 596590Hz if counter0=2 and so on. Therefore counter0=0 => a frequency of approximately 18.2 Hz, which is precisely the frequency at which the PIC is made to interrupt the processor. In DOS, the PIC is programmed to call the Interrupt Service Routine (ISR), at vector 8.
Effectively this means that the value of counter0 will determine the frequency of the timer ISR (Vector 8 in DOS) is called. Changing counter 0 changes the rate at which the timer ISR is called. Therefore if the same person wrote both the code for the ISR, and that for programming counter 0 of the 8254 timer chip, then he could get his ISR called at a predetermined rate as required.
All this is leading to another aside.
|Page 1 of 5 >>|