Le dimanche 05 décembre 2004 à 14:53 +0100, Gilles Espinasse a écrit : > ----- Original Message ----- > From: "Benoit Audouard" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Sunday, December 05, 2004 2:06 PM > Subject: Re: [Eagleusb-dev] Options hidden for SAGEM FAST 800 > > > [ .. ] > > > GEsp identified as well that not having DSPcode that implement CMV for > > ISDN requires the driver to use : > > - CMV files for POTS > > - eagle-usb.conf for ISDN (as long as DSPcode is not available) > > unfortunately, we only know that the line is ISDN or POTS once > > synchronized :-( not at install/config time > > I don't say exactly that. I was reporting of some problems with ISDN modems > and CMV use. Indeed I made a shortcut ;-) that I inferred directly in term of specification from your report. The impacts of using CMV as currently implemented (which you chose for IPcop GNU/Linux distribution) appeared clearly at reading your report, so I propose this new implementation.
> After looking at the available info, > -the first problem may have be caused by not unloading the previous module > in use when configuration file has changed for CMV support. Modem is no more > in use, so I don't know. We miss some features - "resend the CMV" (for update), - "resynchronize" (after change of VPI/VCI...). Maybe they can be implemented in the modem ? Currently, the only way to force resynchronization is to rmmod eagle-usb and disable usb (rmmod usb-uhci ; rmmod usbcore) then re-enable it : the modem is not alimented (nor any usb device), it forces the module eagle-usb to resend the firmware then DSPcode once usb is again available. That's evidently not satisfactory : to be able to change values "on the fly" and force resynchronization would really be a plus. In a previous mail, https://mail.gna.org/public/eagleusb-dev/2004-11/msg00172.html Farinam suggested "Firmware version number in Eagle products can be obtained by sending "INFO 10" cmv read command. " : maybe it means we can send interactive commands to the modem ? Clearly, we would need some more specifications about this feature ;-) > For the second case, the problem did not appear specially after update and > it should be hardware related because it start to work with another > motherboard. Could you be more precise ? > My primary question was when ADI will send customised CMV files for isdn as > I remember to have seen this subject on a previous post. We miss some planning estimations indeed (on both parts). For the moment, implementing CMV cannot be done for ISDN as long as CMV implementing it are not available, which requires to distinguish POTS and ISDN at install/config time :-( > > The choice of using only eagle-usb.conf for 2.0.0, with > > currently-limited OPTNxx values, was not such a bad choice ;-) at least > > it still works for people having ISDN. > I don't know. I have a few people (with E2T ) reporting disconnections with > CMV use. > I have none reporting the slowdown some have with values in eagle-usb.conf That's OPTN1 that only has an impact for people with ISP "Free dégroupé" : do you have IPcop users having Free dégroupé ? @++ Ben'. aka baud123
