Attention is currently required from: manawyrm, roox, laforge, tnt.

laforge uploaded patch set #2 to this change.

View Change

Introduce virtual DAHDI trunk device

This virtual trunk device is a new character device. Contrary to
the per-channel devices, this is a per-span device for virtual E1
spans.  Userspace reads and writes 32-byte E1 frames on it.

ioctl's are added to create and delete such virtual trunk devices
at runtime.  Each virtual trunk device is limited to one span.

Opening trunkdev is similar to opening channels via /dev/dahd/chanw
works:  All users open the same generic device node but then issue
an ioctl to specify which (named) trundev they actually want to open.

This avoids having to dynamically register minor device ids, creating
device nodes, etc.

The trunkdev is in RED + LOS alarm after creation.  Only once a userspace
process opens the E1 frame side, those alarms cease.

Change-Id: Iffd9a1a09d835b29927acd374364cab56745fb74
---
M drivers/dahdi/Kbuild
M drivers/dahdi/Kconfig
M drivers/dahdi/dahdi-base.c
A drivers/dahdi/trunkdev/Kbuild
A drivers/dahdi/trunkdev/frame_fifo.c
A drivers/dahdi/trunkdev/frame_fifo.h
A drivers/dahdi/trunkdev/trunkdev.c
M include/dahdi/kernel.h
M include/dahdi/user.h
9 files changed, 939 insertions(+), 0 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/dahdi-linux refs/changes/10/34010/2

To view, visit change 34010. To unsubscribe, or for help writing mail filters, visit settings.