doc/019-device-drivers/DeviceDriver.tex

62 This document describes how we write device drivers in Barrelfish. It will walk
70 There are three main entities when discussing drivers:
73     \item[Driver Domain] Is a domain that executes one or more drivers. It is
92 domain can be found in \pathname{usr/drivers/domain/main.c}, with most of the
115 \pathname{usr/drivers/domain/drivertpl.c}. The driver is then statically linked
121 For an example, take a look at \pathname{usr/drivers/domain/Hakefile}.
157 \chapter{Legacy device drivers}
160 Legacy drivers live within a 9single) domain and the structure, as well as the control
164 device drivers are still legacy drivers. So in order to understand what is going
173 \pathname{usr/drivers/omap44xx/fdif/}. In order to get an idea of what the
184 \varname{cFiles}. If you go and look at \pathname{usr/drivers/omap44xx/fdif}
232 Now let's have a look at \pathname{usr/drivers/omap44xx/fdif/fdif.c}, the
262 our device drivers all run in user-space this function ensures that you can
285 glimpse of the user-level side on writing device drivers for ARM. It consists
292 teach students about the basic concepts of device drivers. However, if you
322 the periperhals of a system. That encompasses starting the correct drivers,
338 discovering what drivers are available and how we start them remains the same.
340 and how you can program it to start drivers the right way in your system.
366 \section{Starting PCI drivers on x86}
385 Octopus and propagated to Kaluga which will start individual device drivers to
396 Barrelfish has a number of drivers for PCI cards. Mostly for network
397 interfaces. Barrelfish drivers, including the ones for PCI, are located in the
398 source tree in \pathname{usr/drivers/}.
400 \section{Writing PCI drivers}
421 the drivers address space. You can use the defined in helper functions in
454 \section{Writing drivers for ARM and System-on-Chip platforms}
458 drivers in the overview in Chapter~\ref{chap:overview}. This section
460 drivers in Kaluga.
467 the \fnname{find\_module} function and hardwire the start-up of these drivers
519 pass on to the device drivers.
522 user-space drivers for your own platform. We have not covered yet how we
526 \section{Kernel support for user-space drivers}
530 want to write user-level device drivers on a new, unsupported platform. We
556 series of smaller capabilities for device drivers from an initial, huge
565 subsystem and does the memory book keeping for PCI drivers. On an ARM
616 Altough we currently have the necessary support for user-space drivers