Created attachment 361418 [details]
qcserial.c backport for RHEL 5
There are a laptops which have Qualcomm WWAN devices which need the qcserial module for it to work.
This module was recently added to upstream kernel and it would be great if it could be added to the RHEL 5 kernel.
I have back ported the kernel module from upstream to RHEL5. and is attached in the patch below.
I verified that the attached patch
- does not step on any IDs e.g. from option.c
- uses APIs in a correct way for our 2.6.18 base (num_bulk_in and friends
are normally filled, but they are not actually used, so can be omitted).
Stand by for a test build.
Created attachment 386966 [details]
Test patch 1
Same code for driver, but also patches necessary build control files
(except the config-generic - out of kernel tree).
Please test the kernel 2.6.18-185.el5.bz523888.1 from this location:
Ok, so i got a card to test finally.
However if i do a modprobe qcserial what happens is this:
drivers/usb/serial/usb-serial.c: USB Serial support registered for Qualcomm USB modem
Shouldnt it be exposing a /dev/ttyUSB0 interface so that i can upload the firmware using it?
Or am i doing something wrong here.
You can download this test kernel from http://people.redhat.com/jwilson/el5
Please update the appropriate value in the Verified field
(cf_verified) to indicate this fix has been successfully
verified. Include a comment with verification details.
This is not a blocker for RHEL 5.5, anyone who wants to block on this issue needs to make a statement as to why. The extent of QE will be to just verify that the kernel driver loads in RHEL 5.5 as we wait for the firmware issue to be resolved, (which should be tracked in a separate BZ).
If QE agrees then they can move the bug back into ON_QA.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.