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