Bug 49942
Summary: | opl3sa2 isapnp activation broken | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Gerald Teschl <gt> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-06-04 16:04:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Gerald Teschl
2001-07-25 15:48:06 UTC
*** Bug 49948 has been marked as a duplicate of this bug. *** This defect is considered SHOULD-FIX for the Fairfax release. How is the card identified BEFORE you set values into it ? You mean the content of /proc/isapnp ? Created attachment 28695 [details]
/proc/isapnp befor setting up the card
Still broken in 7.3. I debugged this problem: The cause is that the card requires dma=0 to work but isapnp.c excludes "0" for dma values. I have sent a proposed patch to the kernel mailing list. Created attachment 59528 [details]
patch to opl3sa2.c
This is the patch which fixes the problem (it has been discussed on the kernel/sound mailing list). Added for the next errata build I had some further discussions with the maintainer of the opl3sa2 driver and we decided that a better fix is to add this as a quirk to the isapnp driver. I'll attach the two necessary patches. Sorry... Created attachment 60004 [details]
patch which makes the use of dma channel 0 configurable
Created attachment 60005 [details]
patch which fixes the isapnp activation of newer opl3sa4 cards which only accept dma channel 0
|