1*4882a593SmuzhiyunGobi3000 network driver 2011-07-29-1026 2*4882a593Smuzhiyun 3*4882a593SmuzhiyunThis readme covers important information concerning 4*4882a593Smuzhiyunthe Gobi Net driver. 5*4882a593Smuzhiyun 6*4882a593SmuzhiyunTable of Contents 7*4882a593Smuzhiyun 8*4882a593Smuzhiyun1. What's new in this release 9*4882a593Smuzhiyun2. Known issues 10*4882a593Smuzhiyun3. Known platform issues 11*4882a593Smuzhiyun 12*4882a593Smuzhiyun 13*4882a593Smuzhiyun------------------------------------------------------------------------------- 14*4882a593Smuzhiyun 15*4882a593Smuzhiyun1. WHAT'S NEW 16*4882a593Smuzhiyun 17*4882a593SmuzhiyunThis Release (Gobi3000 network driver 2011-07-29-1026) 18*4882a593Smuzhiyuna. Signal the device to leave low power mode on enumeration 19*4882a593Smuzhiyunb. Add "txQueueLength" parameter, which will set the Tx Queue Length 20*4882a593Smuzhiyunc. Send SetControlLineState message during driver/device removal 21*4882a593Smuzhiyund. Change to new date-based versioning scheme 22*4882a593Smuzhiyun 23*4882a593SmuzhiyunPrior Release (Gobi3000 network driver 1.0.60) 06/29/2011 24*4882a593Smuzhiyuna. Add UserspacePoll() function, to support select() 25*4882a593Smuzhiyunb. Fix possible deadlock on GobiUSBNetTXTimeout() 26*4882a593Smuzhiyunc. Fix memory leak on data transmission 27*4882a593Smuzhiyun 28*4882a593SmuzhiyunPrior Release (Gobi3000 network driver 1.0.50) 05/18/2011 29*4882a593Smuzhiyuna. Add support for kernels up to 2.6.38 30*4882a593Smuzhiyunb. Add support for dynamic interface binding 31*4882a593Smuzhiyun 32*4882a593SmuzhiyunPrior Release (Gobi3000 network driver 1.0.40) 02/28/2011 33*4882a593Smuzhiyuna. In cases of QMI read errors, discard the error and continue reading. 34*4882a593Smuzhiyunb. Add "interruptible" parameter, which may be disabled for debugging purposes. 35*4882a593Smuzhiyun 36*4882a593SmuzhiyunPrior Release (Gobi3000 network driver 1.0.30) 01/05/2011 37*4882a593Smuzhiyuna. Fix rare kernel PANIC if a process terminates while file handle close 38*4882a593Smuzhiyun or device removal is in progress. 39*4882a593Smuzhiyun 40*4882a593SmuzhiyunPrior Release (Gobi3000 network driver 1.0.20) 11/01/2010 41*4882a593Smuzhiyuna. Fix possible kernel WARNING if device removed before QCWWANDisconnect(). 42*4882a593Smuzhiyunb. Fix multiple memory leaks in error cases. 43*4882a593Smuzhiyun 44*4882a593SmuzhiyunPrior Release (Gobi3000 network driver 1.0.10) 09/17/2010 45*4882a593Smuzhiyuna. Initial release 46*4882a593Smuzhiyun 47*4882a593Smuzhiyun------------------------------------------------------------------------------- 48*4882a593Smuzhiyun 49*4882a593Smuzhiyun2. KNOWN ISSUES 50*4882a593Smuzhiyun 51*4882a593SmuzhiyunNo known issues. 52*4882a593Smuzhiyun 53*4882a593Smuzhiyun------------------------------------------------------------------------------- 54*4882a593Smuzhiyun 55*4882a593Smuzhiyun3. KNOWN PLATFORM ISSUES 56*4882a593Smuzhiyun 57*4882a593Smuzhiyuna. Enabling autosuspend: 58*4882a593Smuzhiyun Autosuspend is supported by the Gobi3000 module and its drivers, 59*4882a593Smuzhiyun but by default it is not enabled by the open source kernel. As such, 60*4882a593Smuzhiyun the Gobi3000 module will not enter autosuspend unless the 61*4882a593Smuzhiyun user specifically turns on autosuspend with the command: 62*4882a593Smuzhiyun echo auto > /sys/bus/usb/devices/.../power/level 63*4882a593Smuzhiyunb. Ksoftirq using 100% CPU: 64*4882a593Smuzhiyun There is a known issue with the open source usbnet driver that can 65*4882a593Smuzhiyun result in infinite software interrupts. The fix for this is to test 66*4882a593Smuzhiyun (in the usbnet_bh() function) if the usb_device can submit URBs before 67*4882a593Smuzhiyun attempting to submit the response URB buffers. 68*4882a593Smuzhiyunc. NetworkManager does not recognize connection after resume: 69*4882a593Smuzhiyun After resuming from sleep/hibernate, NetworkManager may not recognize new 70*4882a593Smuzhiyun network connections by the Gobi device. This is a system issue not specific 71*4882a593Smuzhiyun to the Gobi device, which may result in dhcp not being run and the default 72*4882a593Smuzhiyun route not being updated. One way to fix this is to simply restart the 73*4882a593Smuzhiyun NetworkManager service. 74*4882a593Smuzhiyun 75*4882a593Smuzhiyun------------------------------------------------------------------------------- 76*4882a593Smuzhiyun 77*4882a593Smuzhiyun 78*4882a593Smuzhiyun 79