Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 843605

Summary: expresscard test should not use HAL
Product: [Retired] Red Hat Hardware Certification Program Reporter: Greg Nichols <gnichols>
Component: Test Suite (tests)Assignee: Caspar Zhang <czhang>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.6.4CC: czhang, qcai, rlandry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: expresscard test uses udev instead of HAL for hardware detection in test planning and execution. Reason: HAL is deprecated in RHEL6. Result (if any):
 Story Points: ---
Clone Of: 843604 Environment:
Last Closed: 2013-02-01 18:20:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 851892    
Attachments:
Description Flags
plan from 1.5-32 showing expresscard was planned
none
expresscard: add auto-detection czhang: review? (gnichols)

Description Greg Nichols 2012-07-26 18:21:29 UTC 
Description of problem:

The expresscard test should not use HAL for test planning or execution.


Version-Release number of selected component (if applicable):

v7 1.6.4
Comment 7 Rob Landry 2012-11-09 19:57:28 UTC 
Created attachment 641801 [details]
plan from 1.5-32 showing expresscard was planned

No extra parameters were passed, just 'v7 plan'
Comment 8 Rob Landry 2012-11-09 19:58:54 UTC 
Created attachment 641802 [details]
v7-1.6.4-9 info results
Comment 10 Caspar Zhang 2012-11-12 06:05:10 UTC 
Created attachment 643241 [details]
expresscard: add auto-detection

patch to add auto-detection back.

self-tested on my T400 + expresscard.
Comment 14 errata-xmlrpc 2013-02-01 18:20:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0222.html