summaryrefslogtreecommitdiffstats
path: root/sys/i4b/capi
Commit message (Collapse)AuthorAgeFilesLines
* Use __FBSDID().obrien2003-06-107-14/+21
|
* Continue de-counting i4b. Devices i4bctl, i4bcapi, iavc, i4bq921,brooks2002-09-027-43/+0
| | | | | | | | i4bq931, i4b, isic, iwic, ifpi, ifpi2, ifpnp, ihfc, and itjc are no longer count devices. Also remove a few other instances of N<DEVICE> being used to control compilation of whole files. Reviewed by: hm
* Remote pci.h/NPCI usage from i4b code.brooks2002-06-133-4/+1
| | | | Approved by: hm
* Fixed printf format errors which apparently crept in while -Wformat wasbde2002-05-251-1/+2
| | | | disabled for gcc-3.
* Change callers of mtx_init() to pass in an appropriate lock type name. Injhb2002-04-043-4/+4
| | | | | | | most cases NULL is passed, but in some cases such as network driver locks (which use the MTX_NETWORK_LOCK macro) and UMA zone locks, a name is used. Tested on: i386, alpha, sparc64
* Clean up the i4b kernel part: remove unmaintained #if(def)s for NetBSD,hm2002-03-174-11/+2
| | | | | OpenBSD and BSD/OS and respective code, remove pre $FreeBSD CVS id's, remove #if(def)s and respective code for FreeBSD versions < 5 .
* Protect mtx_init() invocations with mtx_intialized() checks to avoid agj2001-12-303-4/+8
| | | | | | | reported panic. Submitted by: Alexander Leidinger <Alexander@Leidinger.net> (partly) MFC after: 4 weeks
* It seems that I slipped a nasty bug into the CAPI support. The messagehm2001-10-211-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | lengths for CONNECT_REQ and CONNECT_IND are incorrect, which causes dialouts to fail after certain error situations (an invalid -- not wrong! -- number has been dialed). Since these messages are tagged as too short, the device reads trailing garbage as the B protocol parameters; this is OK as long as the garbage consists of zero bytes, which it usually does, except after the said error. Another change we have taken into use is to send an explicit Q.850 "normal call clearing" code when a call is ignored using PRI equipment (specifically AVM T1); the CAPI pseudo-code for ignore, 1, translates into something at least Ericsson exchanges interpret oddly (message "this area is not reachable from your number"). NCCLR makes the exchange give a busy signal, which is the behaviour at least we prefer (conceivably, the ignore code could be made a sysctl variable). The attached patch corrects the message length issue. It also includes a somewhat unpretty solution for the PRI ignore code (if device's number of channels equals 30, assume PRI and send NCCLR, otherwise send CAPI ignore). Tested using AVM B1 PCI and T1 PCI. Submitted by: Juha-Matti Liukkonen <jml@cubical.fi> Reviewed by: hm MFC after: 1 month
* make driver compile under 4.3-STABLEhm2001-07-221-0/+4
|
* Submitted by: Juha-Matti Liukkonen (Cubical Solutions Ltd) (jml@cubical.fi)hm2001-05-2511-0/+4515
Add a CAPI (hardware independent) driver i4bcapi(4) and hardware driver iavc (4) to support active CAPI-based BRI and PRI cards (currently AVM B1 and T1 cards) to isdn4bsd.
OpenPOWER on IntegriCloud