Windows Certification Newsletter - January 29, 2013
New Windows Hardware Certification blog!
The Windows Certification Newsletter has been replaced by the Windows Hardware Certification blog. Go to the blog for the updates and info you’re used to seeing in the newsletter. Subscribe today!
In this issue
UEFI submission review process revised
UEFI submissions no longer go through an automated signing process. Instead, submissions are reviewed manually twice a week and take about 5 business days to complete. To avoid delays, please follow the guidelines posted on the UEFI submission page on the Hardware Dashboard.
Remember when submitting to the UEFI signing portal to follow the package requirements:
Products must have production names, like "XYZ123 GOP Driver".
Modules must be ship-quality and should have already been tested using the Secure Boot Windows HCK manual tests.
Modules must not allow untrusted code to execute.
Modules must not be licensed under GPLv3 or similar open source licenses.
UEFI Secure Boot isn't supported by Windows for Itanium platforms, so signing IPF drivers via the Hardware Development Center isn't required.
By clicking "Submit", you agree that your submission adheres to package requirements.
If your company is new to UEFI submissions, you also need to provide some extra info. After you create your submission, answer these questions in a text file and email it to Sysdev@mnicrosoft.com.
Does your company have an external website? If so, include the URL.
Does the UEFI submission contain product-quality code?
What's the purpose or goal for the submission?
Is the submission associated with another program?
Does the submission include license terms that would mandate the transmission of keys used for signing, like GPLv3?
Does your submission load and execute any other code prior to ExitBootServices()? If so, how the code is loaded, authorized, and executed? For example, "All images are loaded by EFI LoadImage() and executed by EFI StartImage(), and a prompt is displayed to the user requesting authorization (see attached screenshot)."
What's the submission ID?
How to submit multiple UEFI submissions at one time
If you have a large number of UEFI submissions for devices in the same family, you can combine them to save time and steps. For example, if you have the May 2013 release of UEFI GOP drivers for Video Card Family X, all of those EFI modules can be bundled into a single UEFI submission.
Here's an example of code you might use:
Cabarc.exe N 2013-05-GOP-X.cab *.efi
Then sign this single .cab file and create a UEFI submission with Product Name "Family X GOP drivers for May 2013". Bundling your submissions not only saves time up front, it also helps speed the approval process.
Logo License Agreement updates are coming
A new Logo License Agreement 2013 Style Guidelines specification is scheduled to release at the end of February. Watch for more info in the February 26 newsletter.
Windows Touch Test Lab closed for Chinese New Year
We'd like to remind our partners that Windows Touch Test Lab will be closed from February 9–17 for Chinese New Year. There will be no device delivery or submission processing during those 9 days.
Partners who want to ensure device certification prior to the holiday should:
Email the lab at firstname.lastname@example.org with submission ID and stack-up details.
Submit physical hardware to the lab no later than January 31, 2013.
Submissions made or devices delivered after January 31 might not be processed before the holiday. We also expect submission volume to be heavy, so plan for a 5–10 business day turnaround, in addition to the holiday break.
Please join us in our online forum
We'd like to invite you to the brand new Windows Hardware Testing and Certification forum on MSDN.
The forum is a place for engineers testing and certifying Windows hardware, drivers, and systems to share knowledge, get questions answered, and learn from shared experiences. To begin leveraging the collective knowledge of the community, just post a question on your topic of interest.
The forums are public, so please don't post questions or comments about prerelease versions of the Hardware Certification Kit. As with all other online discussions, be mindful of your privacy — never post info that can personally identify you, like your email address or company name.
We monitor the forum, so if you have any suggestions or feedback for us on the kit, tests, or certification process, please feel free to post that, too!