On Wed, February 9, 2005 8:19 am, Gilles Espinasse said: > From: "Benoit Audouard" <[EMAIL PROTECTED]> >> Le mardi 08 février 2005 à 19:46 +0100, Gilles Espinasse a écrit : >> > From: "Benoit Audouard" <[EMAIL PROTECTED]>
>> > > Hi, >> > > I think that this 2.1.0rc1 version is stable to be released nearly > "as-is" >> > > (I will only add some CMVepFR04.txt file for Free Dégroupé & Cegetel > ADSL Max...) >> > > >> > To my knowledge, it is stable for POST but broken for ISDN >> > when --enable-cmvs is used. >> yep, by default do not use CMVs as long as we have not DSPcode that work >> with them in ISDN... >> If the user knows s/he is using POTS, s/he can use CMVs > I don't understand why you say that we do not have DSPcode that work with > CMV and ISDN. > DSPcode is not impacted by CMVex.txt use or reading the conf file. > It is the driver wich has a failure to read/decode/send the values when > CMVei.txt is used. ah, ok, sorry. I had not understood it this way so far. > At the user level, you may not have the direct capability to compile the > driver again. > There is no embeded compilator on IPCop distrib, everything is made out > before and only installed on the target machine. so for the moment you should keep OPTNxx in /etc/eagle-usb/eagle-usb.conf... and the user can modify them manually, based on CMV*txt content. That's not satisfying. Releasing this version now, will permit, from now on, to have a better view on CMV. @++ Ben'. aka baud123
