Hi, I send this on our public ML, with Analog / Sagem in BCC (so you can choose to answer privately or publicly) > Dear all, > > ADI released an update of the BNM code. This new code "44e2ea17" > should be used instead of "44e2ea16". This new code is compatible > with any hardware version of Eagle chipset. > > (See attached file: RTBLD_44e2ea17.BNM) ok I may have time to look at this, this evening. I'll put online a new version with these BNM included. I hope some more testing can be done with current BNM, to be sure that Oops are eradicated. > This code should be used in conjunction with the following CMVs. > > (See attached file: CMVep_Spain.txt)(See attached file: > CMVep_other.txt) > (See attached file: CMVep_Italy.txt) Hence a proposal I made before : - wouldn't it be better to have a directive FILEPOTS / FILEISDN in /etc/eagle-usb/eagle-usb.org to indicate which CMV file to use ? - or eagleconfig can make a symbolic link on the appropriate file (that could be put in /usr/share/eagle-usb... well to be defined to be compliant with LSB, I'm not the specialist in this area)
And several questions : - in Spain there are at least two kinds of ISP : - Telefonica based : using IPoA (RFC 1483 bridge LLCsnap) or PPPoE LLC (RFC2516) - "Wanadoo/Eresmas" based : same configuration as in France (PPPoA VCmux) => do those CMV work for both ? - does it exist a "default configuration" that works in every country / for every ISP ? - how will be informed of appropriate configuration when today it's already very difficult to obtain VPI / VCI / Encapsulation for every ISP... Is it depending only on the country or the ISP ? - I'm not yet convinced of an existing "default configuration" as OPTN1 has already caused problems of download rate divided by 10 (we have to guess from experience) To answer previous mail from ludovic on the public ML (tuxfamily.org seems currently down) : - eagle-usb.conf.template is created by make install, then eagle-usb.conf is recreated by eagleconfig from values entered and eagle-usb.conf.template (the correction for blinking LED is by using only eagle-usb.conf (not CMV) and latest CVS *or* using only CMV (comment OPTNxx from eagle-usb.conf, which had the bug corrected by sl33p3r) - eagleconfig can put Linetype to 0x0a as soon as we have properly defined the implementation. Using CMV being clearly : - more efficient (as the user should not have to modify it... nor need to edit it, which is not yet sure) and does not require to change the module. - adapted to POTS / ISDN (already implemented) - adapted to country (ISP ?) => we need more info to put it in eagleconfig (it will cause difficulties for tools like Mandrakelinux' Drakconnect that do not yet use our eagleconfig to put appropriate parameters in config files...) - The release candidate can be validated once tests are suficient and I know what to put in http://faq.eagle-usb.org/wakka.php?wiki=InfoCMVEn => What's your planning for availability ? Depending on this, we can implement (or not) what's necessary in eagleconfig (or keep it manual for the moment). Currently we only have testers from France :-( I think the "default behaviour" could be to work without CMV... (as we did before) and then we can begin a "testing" 2.1 branch with CMV and newer BNM to take into account newer functionalities (but we'll have to discuss this as sl33p3r does not like branching, which means supporting two versions... that has not been necessary so far). For info, I will be unavailable next week-end (if I find time to buy a train ticket). @++ Ben'. aka baud123 WebMail / Magic OnLine http://www.magic.fr
