On Thu, March 3, 2005 12:53 pm, Gilles Espinasse said:
> Selon Olivier Blin <[EMAIL PROTECTED]>:
>
>> Benoit Audouard <[EMAIL PROTECTED]> writes:
>> > blino : I think you can use enable-cmvs for Mdk both in kernel module
>> & eaglectrl
>> I'll do it right now for eaglectrl, it will be available
fine, I hope it can work with kernel module compiled with different
configure (sl33p3r you confirm ?)
>> > (it would require to implement CMV choice in drakconnect - if you have
>> > time ;-) but it can remain manual currently).
>>>> Not a problem, quite easy.
>> Should we enable CMV for all POTS providers ?
well in fact, that's global
>> > We'll stay with what
>> > there's in /etc/eagle-usb/eagle-usb.conf that seem to work "most of
>> the
>> > time". The "only" manual change required is to change Linetype to 0x0a
>> > (with leading 0 I think) to use CMVs and choose the correct CMVep
>> > ${ISP}.txt file
>> So, when drakconnect enables CMV for a provider, it will do this :
>> - Look for the provider id
>> - If CMVep${id}.txt exists, copy it as CMVep.txt
Don't copy, make a link (have a look at eagleconfig, that's what is done).
rm -f /etc/eagle-usb/CMVep.txt ; ln -s
/usr/share/eagle-usb/CMVep${CMVep}.txt /etc/eagle-usb/CMVep.txt (nearly
the same for ISDN)
In perl, in the adsl_consts.pm, if the variable CMVep is not available for
the ISP chosen, just take CMVep=WO (see isp_adsl_db.pl).
>> Else if CMVep${country}.txt exists, copy it as CMVep.txt
>> Else, restore original CMVep.txt (is it CMVepWO.txt ?)
>> Is this right ?
It's too complicated to copy back and forth depending on the ISP... just
make a link that will do it, choosing CMVepWO.txt (or CMVeiWO.txt) =>
that's what's done in eagleconfig.
>> What to do for ISDN lines ?
>> And how can we know if the line is an ISDN line ?
>> Should we disable CMV for ISDN ? (Linetype=00000001 ?)
> I think it is not possible in the same time :
> - to use CMV for pots
> - to use eagleusb.conf for isdn
> As the use of CMV change the way the compilation is done, it is a one way
> ticket. No return
That's what I was afraid of... I'm quite sure only one configuration is
available, that's the reason why I asked for testing : if you compile with
--enable-cmvs then put Linetype=0000000A for all cases so
Any other feedback ?
> Concerning isdn, it should work now that /r are removed.
> I had at least one feedback it's work with a v2.0.0 after removing /r.
> http://www.ipcop-forum.de/forum/viewtopic.php?t=4343
cool. I've added to
http://dev.eagle-usb.org/wakka.php?wiki=FeedBack220
>> > I hope we can have a 3.0.0 version by next Monday.
>> Why a 3.0.0 version ? Any big change ?
> Same question
well, corrections ;-) (even if minor)
The version numbering is just there to say "well there has been *some*
modifications : Switching from non CMV to --enable-cmvs is not a minor
change from a functional point of view (the reason why I only published
this version for "testing" with not much hype...).
I think we may put --disable-cmvs ;-) for backward compatibility in the
3.0.0 version, *if* there's suficient feedback. Otherwise we'll wait till
suficient feedback and find another "good reason" to make the jump to
3.0.0 ;-) (translations for example, or <dream on>free - as in freedom -
firmware and/or DSPcode<dream off>).
@++
Ben'. aka baud123
