summaryrefslogtreecommitdiff
path: root/hostapd/doc/driver_wrapper.doxygen
diff options
context:
space:
mode:
authorSam Leffler <sam@FreeBSD.org>2009-03-01 22:10:07 +0000
committerSam Leffler <sam@FreeBSD.org>2009-03-01 22:10:07 +0000
commitb2cbddbd4361766d55c5f9dae81f71f44577bb6a (patch)
tree372b16f9e6ccba7284b53135005cc85cc6545185 /hostapd/doc/driver_wrapper.doxygen
parent514fff2b7c1f2e25e5c0611b598797f32aff1042 (diff)
parent22188e6ab4f02f981de3b9f228a40b1e8f98e6a1 (diff)
Diffstat (limited to 'hostapd/doc/driver_wrapper.doxygen')
-rw-r--r--hostapd/doc/driver_wrapper.doxygen20
1 files changed, 20 insertions, 0 deletions
diff --git a/hostapd/doc/driver_wrapper.doxygen b/hostapd/doc/driver_wrapper.doxygen
new file mode 100644
index 0000000000000..0ad196f2d6b6c
--- /dev/null
+++ b/hostapd/doc/driver_wrapper.doxygen
@@ -0,0 +1,20 @@
+/**
+\page driver_wrapper Driver wrapper implementation (driver.h, drivers.c)
+
+All hardware and driver dependent functionality is in separate C files
+that implement defined wrapper functions. Other parts
+of the hostapd are designed to be hardware, driver, and operating
+system independent.
+
+Driver wrappers need to implement whatever calls are used in the
+target operating system/driver for controlling wireless LAN
+devices. As an example, in case of Linux, these are mostly some glue
+code and ioctl() calls and netlink message parsing for Linux Wireless
+Extensions (WE). Since features required for WPA were added only recently to
+Linux Wireless Extensions (in version 18), some driver specific code is used
+in number of driver interface implementations. These driver dependent parts
+can be replaced with generic code in driver_wext.c once the target driver
+includes full support for WE-18. After that, all Linux drivers, at
+least in theory, could use the same driver wrapper code.
+
+*/