Bug 1098436

1.OEM: Briefly summarize the purpose of the DUP request.
Lenovo laptop ThinkPad W540 Redhat hardware certification is blocked by O2Micro card reader. This is a laptop GAed in 2013, and certification must be done to strengthen competitiveness.

2a. OEM: Please provide the name of the hardware device for which you are requesting a DUP package. Please list PCI ID(s) in addition to hardware name(s) and specific model(s). 
Hardware Name: O2Micro card reader Id 8520
Hardware ID: 1217:8520
2b. When will the hardware system(s) that require(s) the DUP package be shipped? Please provide calendar dates.
N/A

3a. OEM and IHV: What is the name and version of the new or updated driver for which you are requesting a DUP package? 
Name: sdhci-pci
3b. Is the driver accepted upstream?
Yes
3c. Please provide the git commit for the upstream driver.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=01acf6917aed934388609177605d54ad1463b252
3d. If the driver is not yet accepted upstream, when do you anticipate it will be accepted? 
Accepted

4. OEM: What is the Bugzilla ticket number(s) that contain(s) the request(s) for the new/updated driver(s) in RHEL 6.6?
1089109

5. OEM: Is the driver in the RHEL install path (such as a SAS or Ethernet controller)? If you are uncertain, please contact your HPM for assistance. 
Path: a card reader controller(drivers/mmc/host/sdhci-pci)

6. OEM: What is the exact date by which you require the DUP package? Please consider any internal QA, product readiness reviews, or manufacturing milestones, as well as the amount of time it has historically taken you to complete Red Hat hardware certification. 
N/A

7. Red Hat: When is the kernel code submission deadline for the next RHEL update release(s)? 
Code for RHEL 6.6 is due by the Partner Code Submission Deadline. Please check the RHEL 6.6 schedule sent to you by Red Hat for the exact date. Note that if the driver code is not received on or before this date, Red Hat may reject the request. 

8a. OEM or IHV: Will hardware be sent to Red Hat for development and testing of the DUP package?
N/A
8b. If sample hardware is available, who will be providing it to Red Hat for testing purposes? 
8c. If sample hardware is not yet available, when will it be provided to Red Hat?
N/A

9. OEM and IHV: If hardware is unavailable for shipment to Red Hat, Red Hat will allow the OEM and IHV to perform all DUP package testing as long as the test strategy and results are submitted to Red Hat for review. Please provide the names and email addresses of the testers who can provide this information to Red Hat only if hardware cannot be sent to Red Hat.
OEM Name: OEM Email:
IHV Name: IHV Email:

10. OEM and IHV: Red Hat requires that the OEM and IHV test the RHEL 6.6 alpha, beta, and release candidate that include the new or updated device driver for the new hardware. Testing is also required for the DUP package (see below). Please provide the name and email address of the person at each organization who will be testing the driver in RHEL 6.6. 
OEM Name: Garrick Yang	OEM Email:garrickyang
IHV Name: IHV Email:

11. OEM and IHV: OEMs and IHVs must also test the DUP package for RHEL 6.5. Please provide the name and email address of the person at each organization who will be testing the DUP driver package on RHEL 6.5. If hardware is unavailable for shipment to Red Hat, please provide the name and email address of the person at each organization who can provide Red Hat with the test strategy information as well as test results. 
OEM Name: Garrick Yang	OEM Email:garrickyang
IHV Name: IHV Email:

12. Red Hat: By what date must the requested DUP package be built?
DUP packages for RHEL 6.5 must be built and finalized by the RHEL 6.6 Beta Snapshot 2 release date. Please check the RHEL 6.6 schedule sent to you by Red Hat for the exact date. 
Since DUP need to be test by Lenovo, and all certification must be done by May, please provide DUP by 5/30.

13. OEM and IHV: Before work on the DUP request can begin, the OEM and IHV must provide the name and contact information for the person responsible for the DUP request. By providing this information, the OEM and IHV confirm that they agree to the dates and requirements listed in the completed DUP request template. 

OEM 
Representative: Peter Zhang
Date:2014/5/16
IHV
Representative:
Date: