On Tuesday 27 January 2004 02:56, Muli Ben-Yehuda wrote:
> The first draft of the slides for this one are now available at
>http://www.mulix.org/lectures/intro_to_linux_device_drivers/intro_linux_device_drivers.pdf.
Very good. Small remarks/questions:
- I assume they learn the actual build procedure elsewhere. If not, than at
least some pointers are needed.
- The idea to patch the core for hooking into timer interrupts is very
good for learning (the power of open source...). However, because
the interrupt you talk about is (by incident) the timer, people may
get the wrong idea that in Linux patching is needed for timing...
(which is a very common task). You may want to mention the existance
of the simple timer_* API.
- Some mention (maybe verbally) about kernel versioning (which is used
for their exercise?) -- Understanding the Linux kernel API's are
a moving target (intentionally...)
- Are they getting (maybe in their lectures) some orderly view about:
* Different locking schemes? (spinlocks, reader-writers, semaphores,...)
* Different schemes for defering work? (softirqs, tasklet API,
work-queues, timer API's)
Bye,
--
Oron Peled Voice/Fax: +972-4-8228492
[EMAIL PROTECTED] http://www.actcom.co.il/~oron
Linux lasts longer!
-- "Kim J. Brand" <[EMAIL PROTECTED]>
--------------------------------------------------------------------------
Haifa Linux Club Mailing List (http://www.haifux.org)
To unsub send an empty message to [EMAIL PROTECTED]
