Bug 679135

Summary: Novatel Wireless Device Id missing from qcserial.c
Product: [Fedora] Fedora Reporter: tracyde
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: rawhideCC: cpuobsessed, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, tracyde
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-30 21:18:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Adds known Novatel Wireless device id's to qcserial.c none

Description tracyde 2011-02-21 17:32:36 UTC 
Created attachment 479966 [details]
Adds known Novatel Wireless device id's to qcserial.c

Description of problem:
Gobi 2000 chipset for the Google Cr-48 laptop and (and others with Gobi 2000 chipset packaged by Novatel Wireless) does not get enumerated by the qcserial module.

Version-Release number of selected component (if applicable):
latest Fedora 14 released 2.6 kernel as well as Fedora 15 kernel found at http://repos.fedorapeople.org/repos/kyle/kernel/

How reproducible:
always

Steps to Reproduce:
1. `modprobe qcserial` on a computer that has a Novatel Wireless Gobi 2000 chipset
2. `ls /dev/ttyUSB0`
3.
  
Actual results:
the ttyUSB0 device does not get enumerated after the qcserial module gets loaded

Expected results:
the ttyUSB0 device should be created and accessible

Additional info:
I have attached a patch that adds the needed USB_DEVICE lines to the qcserial.c file.  The patch has been proven to work on the Google Cr-48 laptop.
Comment 1 Chuck Ebbert 2011-02-24 18:27:40 UTC 
The IDs (0x05c6, 0x9208) and (0x05c6, 0x920b) are already in 2.6.35. The other four are not upstream and you need to submit them there first.
Comment 2 Josh Boyer 2011-08-29 18:11:11 UTC 
Derek, this still isn't fixed in the upstream kernel.  You should submit your patch to the linux-usb list and make sure to follow SubmittingPatches in the Documentation directory.
Comment 3 Josh Boyer 2012-04-30 21:18:41 UTC 
All of these devices are in the driver now, as of 3.4-rc1.