Bug 843605 - expresscard test should not use HAL
expresscard test should not use HAL
Product: Red Hat Hardware Certification Program
Classification: Red Hat
Component: Test Suite (tests) (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Caspar Zhang
Red Hat Kernel QE team
Depends On:
Blocks: 851892
  Show dependency treegraph
Reported: 2012-07-26 14:21 EDT by Greg Nichols
Modified: 2013-02-01 13:20 EST (History)
3 users (show)

See Also:
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
Last Closed: 2013-02-01 13:20:52 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
plan from 1.5-32 showing expresscard was planned (1.62 KB, application/octet-stream)
2012-11-09 14:57 EST, Rob Landry
no flags Details
expresscard: add auto-detection (1.39 KB, patch)
2012-11-12 01:05 EST, Caspar Zhang
czhang: review? (gnichols)
Details | Diff

  None (edit)
Description Greg Nichols 2012-07-26 14:21:29 EDT
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 14:57:28 EST
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 14:58:54 EST
Created attachment 641802 [details]
v7-1.6.4-9 info results
Comment 10 Caspar Zhang 2012-11-12 01:05:10 EST
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 13:20:52 EST
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.


Note You need to log in before you can comment on or make changes to this bug.