summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorTzafrir Cohen <tzafrir.cohen@xorcom.com>2012-03-15 14:39:15 +0000
committerTzafrir Cohen <tzafrir.cohen@xorcom.com>2012-03-15 14:39:15 +0000
commit0e97657da8bc55ab2cd77fbcf68027f4b50616ed (patch)
treea2a7528bb043f3f346e2cae845652612a0bba01f /README
parent2910f9b13bb127987b3f9db4fa0e45a386976e2b (diff)
README: note on DKMS
git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/trunk@10480 a0bf4364-ded3-4de4-8d8a-66a801d63aff
Diffstat (limited to 'README')
-rw-r--r--README18
1 files changed, 18 insertions, 0 deletions
diff --git a/README b/README
index f1d3e6c..50979aa 100644
--- a/README
+++ b/README
@@ -163,6 +163,24 @@ to the script:
./build_tools/make_static_devs -d tmp/newroot/dev/dahdi
+DKMS
+----
+DKMS, Dynamic Kernel Module Support, is a framework for building Linux
+kernel modules. It is used, among others, by several distributions that
+package the DAHDI kernel modules.
+
+DKMS is designed to provide updates over drivers installed from original
+kernel modules tree. Thus it installed modules into /lib/modules/updates
+or /lib/modules/VERSION/updates . This is generally not an issue on
+normal operation. However if you try to install DAHDI from source on
+a system with DAHDI installed from DKMS this way (potentially of an
+older version), be sure to remove the DKMS-installed modules from the
+updates directory. If you're not sure, the following command will give
+you a clue of the versions installed:
+
+ find /lib/modules -name dahdi.ko
+
+
Installing the B410P drivers with mISDN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DAHDI includes the wcb4xxp driver for the B410P, however, support for the