Changes between Version 11 and Version 12 of DeviceDrivers

Timestamp:

2011-11-12T22:02:33Z (13 years ago)

Author:

Jiri Svoboda

Comment:

locfs

DeviceDrivers

@@ -90 +90 @@
 == Exposing Driver Services to Clients ==
 
-All driver services are provided to clients (applications) via the location service. For each bound function node the device framework creates a service whose name is based on the physical path of that function.
+All driver services are provided to clients (applications) via the location service. For each bound function node the device framework creates a service whose name is based on the physical path of that function. The services are created in the ''devices'' namespace. This is mapped to the {{{/loc/devices}}} directory via ''locfs''. For example:
 
-Often the driver will want to add the function service to one or more service categories. This can be done using the DDF function:
+{{{
+/# ls /loc/devices
+\hw\pci0\00:01.0\com1\a
+\hw\pci0\00:01.0\ctl
+\hw\pci0\ctl
+\virt\lo\port0
+}}}
+
+Often the driver will want to add the function service to one or more service categories. Service categories imply the protocol spoken by a service (and possibly also the intended use). This can be done using the DDF function:
 {{{
 int ddf_fun_add_to_category(ddf_fun_t *fun, const char *cat_name)
 }}}
+
+For example, the input server automatically picks up and opens any device in the categories ''keyboard'' and ''mouse''.
 
 == Traditional I/O Device Drivers ==