Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 11 and Version 12 of DeviceDrivers


Ignore:
Timestamp:
2011-11-12T22:02:33Z (8 years ago)
Author:
Jiri Svoboda
Comment:

locfs

Legend:

Unmodified
Added
Removed
Modified
  • DeviceDrivers

    v11 v12  
    9090== Exposing Driver Services to Clients ==
    9191
    92 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.
     92All 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:
    9393
    94 Often the driver will want to add the function service to one or more service categories. This can be done using the DDF function:
     94{{{
     95/# ls /loc/devices
     96\hw\pci0\00:01.0\com1\a
     97\hw\pci0\00:01.0\ctl
     98\hw\pci0\ctl
     99\virt\lo\port0
     100}}}
     101
     102Often 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:
    95103{{{
    96104int ddf_fun_add_to_category(ddf_fun_t *fun, const char *cat_name)
    97105}}}
     106
     107For example, the input server automatically picks up and opens any device in the categories ''keyboard'' and ''mouse''.
    98108
    99109== Traditional I/O Device Drivers ==