diff options
| author | Tzafrir Cohen <tzafrir.cohen@xorcom.com> | 2010-02-15 09:17:54 +0000 |
|---|---|---|
| committer | Tzafrir Cohen <tzafrir.cohen@xorcom.com> | 2010-02-15 09:17:54 +0000 |
| commit | edb493e06240781ee9ca9fd934d62d60c143aab9 (patch) | |
| tree | daaf64b61201f110aee92e397ef885cac6faf7ac | |
| parent | 85361796beb7477609d6903a27b6da6f06081418 (diff) | |
Don't generate static device files at install time.
* Most users use udev anyway
* Don't attempt to create any device files in the 'install' target.
* Setting DYNFS at build time should no longer be needed
- Though remains harmless.
* In order to create the static device files, use the script:
build_tools/make_static_devs
git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/trunk@8034 a0bf4364-ded3-4de4-8d8a-66a801d63aff
| -rw-r--r-- | Makefile | 32 | ||||
| -rw-r--r-- | README | 21 |
2 files changed, 16 insertions, 37 deletions
@@ -55,10 +55,6 @@ DAHDI_BUILD_ALL:=m KMAKE=$(MAKE) -C $(KSRC) SUBDIRS=$(PWD)/drivers/dahdi DAHDI_INCLUDE=$(PWD)/include DAHDI_MODULES_EXTRA="$(DAHDI_MODULES_EXTRA)" HOTPLUG_FIRMWARE=$(HOTPLUG_FIRMWARE) -ifneq (,$(wildcard $(DESTDIR)/etc/udev/rules.d)) - DYNFS:=yes -endif - ROOT_PREFIX:= ASCIIDOC:=asciidoc @@ -139,40 +135,12 @@ uninstall-include: -rmdir $(DESTDIR)/usr/include/dahdi install-devices: -ifndef DYNFS - mkdir -p $(DESTDIR)/dev/dahdi - rm -f $(DESTDIR)/dev/dahdi/ctl - rm -f $(DESTDIR)/dev/dahdi/channel - rm -f $(DESTDIR)/dev/dahdi/pseudo - rm -f $(DESTDIR)/dev/dahdi/timer - rm -f $(DESTDIR)/dev/dahdi/transcode - rm -f $(DESTDIR)/dev/dahdi/253 - rm -f $(DESTDIR)/dev/dahdi/252 - rm -f $(DESTDIR)/dev/dahdi/251 - rm -f $(DESTDIR)/dev/dahdi/250 - mknod $(DESTDIR)/dev/dahdi/ctl c 196 0 - mknod $(DESTDIR)/dev/dahdi/transcode c 196 250 - mknod $(DESTDIR)/dev/dahdi/timer c 196 253 - mknod $(DESTDIR)/dev/dahdi/channel c 196 254 - mknod $(DESTDIR)/dev/dahdi/pseudo c 196 255 - N=1; \ - while [ $$N -lt 250 ]; do \ - rm -f $(DESTDIR)/dev/dahdi/$$N; \ - mknod $(DESTDIR)/dev/dahdi/$$N c 196 $$N; \ - N=$$[$$N+1]; \ - done -else # DYNFS install -d $(DESTDIR)/etc/udev/rules.d build_tools/genudevrules > $(DESTDIR)/etc/udev/rules.d/dahdi.rules install -m 644 drivers/dahdi/xpp/xpp.rules $(DESTDIR)/etc/udev/rules.d/ -endif uninstall-devices: -ifndef DYNFS - -rm -rf $(DESTDIR)/dev/dahdi -else # DYNFS rm -f $(DESTDIR)/etc/udev/rules.d/dahdi.rules -endif install-modules: modules ifndef DESTDIR @@ -93,11 +93,6 @@ modules. To install to a relative path you can use something like: make install-modules DESTDIR=$PWD/target -The 'install' target might fail if run as a user to a DESTDIR when -attempting to generate device files. In that case, try: - - make install DESTDIR=$PWD/target DYNFS= - Extra Modules ~~~~~~~~~~~~~ @@ -109,6 +104,22 @@ SUBDIRS_EXTRA: make MODULES_EXTRA="mod1 mod2" SUBDIRS_EXTRA="subdir1/ subdir1/" +Static Device Files +~~~~~~~~~~~~~~~~~~~ +Userspace programs communicate with the DAHDI modules through special +device files under /dev/dahdi . Those are normally created by udev, but +if you use an embedded-type system and don't wish to use udev, you can +generate them with the following script, from the source directory: + + ./build_tools/make_static_devs + +This will generate the device files under /dev/dahdi . If you need to +generate them elsewhere (e.g. `tmp/newroot/dev/dahdi`) use the option -d +to the script: + + ./build_tools/make_static_devs -d tmp/newroot/dev/dahdi + + Installing the B410P drivers with mISDN ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DAHDI includes the wcb4xxp driver for the B410P, however, support for the |