Le lundi 01 novembre 2004 à 20:20 +0100, Frederick Ros a écrit : > Benoit Audouard wrote : > | Hi, > | > | In the changelog > | https://mail.gna.org/public/eagleusb-cvs/2004-10/index.html (and 2004-11 > | for November of course) > | I've not seen any updates for remaining Oops from Sl33p3r ? Is it > | normal ? > > It seems that none of my modifs since October 20 are send on the cvs > mailing .. Duno why. http://cvs.gna.org/viewcvs/eagleusb/eagleusb/driver/?sortby=date#dirlist hum you're right, changes are made, mails not sent... to be told to gna admin...
> However it seems that the number of Ooops are minimal now. yep, maybe there's a wondershaper syndrom too ;-) > | - verify the content of file CMVep.txt (the default one) > Not sure if I ever implement it ... It goes against the fact that > implementation of new function in the modem only needs new BNMs + new > CMVs, and if we implement the check, we'll have to also modify eaglectrl > to allow new functions... If we do not implement any check it means that > if we send bogus info to the modem we can stale it ... > The solution would be perhaps to only warn if there's some unknow > functions in the CMV file ... > | - other ? > > Fully implement CMVs. That is: be sure how to inform eaglectrl of the > CMV file it should loaf (link / COUNTRY + ISP variable to construct the > file name or whatever) .. Note that the --cmvs can take an optional file > name... > > > | - stabilize CMV implementation (the "default" choice should be made that > | work 99% of the time without manual action from the end-user) > > Oops .. that was planned for the futur ... by "verify the content", I meant check that "default" values work "most of the time" (those currently in /etc/eagle-usb/eagle-usb.conf in fact) : - we've already identified a problem with OPTN1 => that's a "known problem" we (and the user) can manage - any other problem not yet identified would be problematic, until there's a workaround or a solution @++ Ben'. aka baud123
