Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001326]: ISA cards (opl3sa2 in particular) are not detected properly on 2.6 kernels
Date: Fri, 12 Aug 2005 16:08:01 +0200	[thread overview]
Message-ID: <151b2daf7d8031b79d3b3954f97781f7@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1326> 
======================================================================
Reported By:                ahaning
Assigned To:                perex
======================================================================
Project:                    ALSA - utils
Issue ID:                   1326
Category:                   alsaconf
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
======================================================================
Date Submitted:             08-10-2005 03:39 CEST
Last Modified:              08-12-2005 16:08 CEST
======================================================================
Summary:                    ISA cards (opl3sa2 in particular) are not detected
properly on 2.6 kernels
Description: 
When brute-force detecting my OPL3SA2 card, the IRQ and DMA1/DMA2 settings
are incorrectly detected by alsaconf from alsa-utils. For example, the
default BIOS settings are IRQ=11, DMA1=0, DMA2=1, but alsaconf detects
IRQ=5, DMA1=1, DMA2=0. No matter the BIOS settings, alsaconf always
detects those settings (IRQ=5, DMA1=1, DMA2=0). If I set the BIOS settings
to that, then the card will make sound (after touching the mixer while
playing audio).

According to perex (author of the opl3sa2 driver):

"The alsaconf tries to gather free resources (irq/dma/ports) from the
/proc filesystem. It might be extended to gather this information also
from /sys filesystem."
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0000879 (snd_)opl3sa2 (isa) doesn't work (fails...
======================================================================

----------------------------------------------------------------------
 perex - 08-12-05 15:56 
----------------------------------------------------------------------
takashi: See the previous bug (related to). The BIOS disables ISA PnP
feature of the opl3sa2 card. It is not visible with the ISA PnP subsystem
or pnpdump from the isapnptools package. So, it behaves like a legacy ISA
card.

ahaning: You have a driver provided by vendor for Windows, right? Then it
might do some magic which we don't know. Or you may try, if the driver
resources in windows follows the BIOS settings. Perhaps, you'll have
similar problems with non-default values.

The datasheet for your chip says that the ISA PnP subsystem should detect
the card even if it is configured in manual mode.

----------------------------------------------------------------------
 perex - 08-12-05 16:08 
----------------------------------------------------------------------
Okay, I got it. The pnpbios lists this device as:

NMX2210
state = active
io 0x220-0x22f
io 0x530-0x537
io 0x388-0x38f
io 0x330-0x331
io 0x370-0x371
irq 7
dma 0
dma 1

We need to add support for these devices to snd-opl3sa module and for
other ISA modules. And yes, the bug 
http://bugzilla.kernel.org/show_bug.cgi?id=4561 is definitely related.
Actually ALSA drivers support only ISA PnP devices not BIOS PnP devices.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-10-05 03:39 ahaning        New Issue                                    
08-10-05 03:39 ahaning        Distribution              => Slackware 9.1 (but
it's not distribution-specific)
08-10-05 03:39 ahaning        Kernel Version            => 2.6.12.2        
08-10-05 13:26 perex          Status                   new => assigned     
08-10-05 13:26 perex          Assigned To               => perex           
08-10-05 13:26 perex          File Added: alsaconf                         
08-10-05 13:28 perex          Note Added: 0005747                          
08-10-05 13:29 perex          Project                  ALSA - driver => ALSA -
utils
08-10-05 13:30 perex          Relationship added       related to 0000879  
08-10-05 13:31 perex          Category                 1_OTHERS => alsaconf
08-10-05 14:55 ahaning        Note Added: 0005748                          
08-11-05 00:24 ahaning        Note Added: 0005752                          
08-11-05 23:59 ahaning        Note Added: 0005763                          
08-12-05 00:00 ahaning        Note Edited: 0005763                         
08-12-05 03:09 ahaning        Note Added: 0005764                          
08-12-05 09:29 perex          Note Added: 0005766                          
08-12-05 12:54 ahaning        Note Added: 0005767                          
08-12-05 15:11 perex          Summary                  ISAPNP cards (opl3sa2 in
particular) are not detected properly on 2.6 kernels => ISA cards (opl3sa2 in
particular) are not detected properly on 2.6 kernels
08-12-05 15:14 perex          Note Added: 0005768                          
08-12-05 15:35 tiwai          Note Added: 0005769                          
08-12-05 15:36 ahaning        Note Added: 0005770                          
08-12-05 15:44 tiwai          Note Added: 0005771                          
08-12-05 15:45 tiwai          Note Added: 0005772                          
08-12-05 15:56 perex          Note Added: 0005777                          
08-12-05 16:08 perex          Note Added: 0005778                          
======================================================================




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

             reply	other threads:[~2005-08-12 14:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12 14:08 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-23 12:32 [ALSA - utils 0001326]: ISA cards (opl3sa2 in particular) are not detected properly on 2.6 kernels bugtrack
2005-08-23  3:19 bugtrack
2005-08-22 13:18 bugtrack
2005-08-22 10:32 bugtrack
2005-08-19  2:51 bugtrack
2005-08-19  1:02 bugtrack
2005-08-19  0:35 bugtrack
2005-08-18 14:36 bugtrack
2005-08-18 10:56 bugtrack
2005-08-18 10:51 bugtrack
2005-08-15 11:55 bugtrack
2005-08-13 17:06 bugtrack
2005-08-13 13:11 bugtrack
2005-08-12 16:52 bugtrack
2005-08-12 16:03 bugtrack
2005-08-12 14:44 bugtrack
2005-08-12 13:56 bugtrack
2005-08-12 13:45 bugtrack
2005-08-12 13:44 bugtrack
2005-08-12 13:36 bugtrack
2005-08-12 13:35 bugtrack
2005-08-12 13:14 bugtrack
2005-08-12 13:11 bugtrack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=151b2daf7d8031b79d3b3954f97781f7@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox