Re Le mardi 12 avril 2005 à 19:12 -0400, Farahmand, Farinam a écrit : > The CMV document is attached. The zip file includes a PDF document and > an Excel sheet. The Excel sheet has the latest changes for each CMV and > the PDF file has the general description of the CMVs.
ok thanks a lot, it will really help I hope. Which license do you choose for these documents ? GFDL would be a "natural" choice, it brings the same benefit as your current disclaimer. If you're ok, we (or you) can add it then redistribute the update : It would let us modify the format of the document for example (from pdf to html). BTW, for such file size (your mail is 946 kilo-bytes, nearly 1 MB) - as some people still have less than 10 MB mailboxes - please prefer to upload it on ftp.analog.com and give a link stating the size of the file for example : ftp://ftp.analog.com/pub/broadband/adsl/ or we could provide you with an sftp access to eagle-usb.org (SSH2 is required though and it may not go through your firewall) or to a public web area on another eagle-usb-related domain name. > In the driver, we do the following: > > 1- Load the L1 code ( DSP code ) to the modem. > 2- Configure the modem. > 3- Tell the modem to start negotiation with the CO. > 4- Monitor the negotiation until the modem goes to the operational mode. > 5- After the operational state, monitor the link. (if the link is bad, > we bring down the link and start the negotiation again.) Just in case, would you have an available documentation of this state machine ? (well the current driver implements it anyway...) > - We write CMVs to the modem to configure the modem.(step 2) > - We read CMVS from the modem to monitor the link/ modem activity ( > steps 4 & 5 ) > - CO ( Central Office == DSLAM ). > - Why do we have a CMV.txt file? ISPs have different DSLAMs (from > different CO chip vendors ). In order to get our modem working with all > the DSLAMs, we sometimes need to configure the modem differently. The > best way to handle this is to read the CMVs from a file and write them > to the modem before negotiation. Does it exist a list of supported DSLAM ? All I suppose ;-) Can the model of DSLAM be obtained by a CMV command (in order to send the appropriate CMV file). Sorry, I had only a brief look at your document for the moment... we'll be compiling a list of all our questions so that you can review them. One immediate comment though : only first 15 CMV are described, what about the remaining 84 as CMV can go up to 99 ? > - I had a quick look at the problems reported by the users and in almost > all of the cases, having the driver properly installed, modem goes to > the operational state ( with one exception ??? ). So, with a good > confidence we can assume that the cmv.txt implementation is working > fine. For the cases that the modem does not go to operational, two > possible cases come to my mind: > first, DSP code is not loaded properly(could be OS related). In this > case, we should not be able to read any CMVs. > second, the negotiation with CO fails. Here, we can read cmvs but the > modem does not go to OPERATIONAL. CMV "STAT 0" is used to monitor the > link status ( refer to cmv manual for the details ) > > Please study the document and send me the questions. I will try to > answer them within 5 working days. thanks a lot for your cooperation. If you want to involve directly to the forum, just register at http://forum.eagle-usb.org that's free (as in freedom and as in a free beer ;-) ) What about the other unanswered questions at http://dev.eagle-usb.org/wakka.php?wiki=DevEagleUsbIII could you have a look at them ? We'll be coming back to you by monday for remaining issues. Best regards Ben'. aka baud123
