Opened 18 years ago
Last modified 16 years ago
#38 closed defect
UniAud32 does not report correct IRQ flags to the resource_manager's database — at Version 4
| Reported by: | Steve Wendt | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | MMPM/2 Compatibility |
| Component: | UNIAUD32 | Version: | 1.1.4 |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by )
Uniaud32 does not report correct IRQ settings to the resource_manager's database.
Functions affected: request_irq() RMRequestIRQ() ALSA_SetIrq()
In RMRequestIRQ() the "PCIIrqPin" variable is always set to "none". Actually it should reflect the irq pin value taken from the sound device's pci configuration space. In RMRequestIRQ() the "IRQFlags" variable is always set to shared. Actually this flag should not be set before having called ALSA_SetIRQ(). The "IRQFlags" variable should reflect what type of IRQ (shared/exclusive) ALSA_SetIRQ() was able to connect.
Change History (4)
comment:1 by , 18 years ago
| Status: | new → assigned |
|---|
comment:2 by , 17 years ago
| Milestone: | → milestone1 |
|---|---|
| Version: | → 1.1.4 |
comment:3 by , 17 years ago
| Owner: | removed |
|---|---|
| Severity: | minor → normal |
| Status: | assigned → new |
As far as I know, this is not currently fixed, but if I'm not mistaken it would be fixed by the acpidrv stuff we need the source for. Not completely sure about that.
comment:4 by , 16 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | ALSA Hardware Compatibility → MMPM/2 Compatibility |
Who reported this? Can we get more information about how to observe this? Or, given the apparent understanding of the problem, how about a patch? :)
Does any1 know, if this has been fixed ?