Hello! I am still trying to understand how to (most easily) integrate Winbond W6692 driver with the HiSax module. I would prefer using the level 1-3 and dss1/1tr6 code available there to avoid writing it all by myself (which would require quite thorough studies of ISDN specification). I have been using telespci.* as an example of a low level HiSax driver. Are there better examples? Like drivers for passive ISDN cards NOT based on the HiSax chipset. I can see that the IsdnCardState structure is used to pass data and control points (function pointers) between the low level driver and the upper level components. The hscx.* seems to do most of the actual low level communication while isdnl?.* are driving the state machine and telling the lower level components what to do. To me it seems that I should replace hscx.* with something W6692 specific and do some minor modifications to other object files. Does this sound reasonable or am I going the wrong way? While looking at the ISDN source code in general I have thought several times that these things could be made more modular. Are there any plans to make the level 1-3 state machine and dss1, 1tr6 and tarif info separate modules which could be used from various low level drivers? For example the generic PPP support is split into several kernel modules and it seems to make the design more clear. Also, the generic CAPI 2.0 kernel interface is now included as a part of the AVM B1 driver. Are there any plans to take that out and make it a separate module? The source being organized the way it is now, I probably have to break the HiSax sertification to take advantage of existing HiSax code. -- Johannes Lehtinen <[EMAIL PROTECTED]>, http://www.iki.fi/jle/
