public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Klaus Reimer <k@ailis.de>
To: Bill Nottingham <notting@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: opl3sa2 in 2.4.2 on Toshiba Tecra 8000
Date: Thu, 29 Mar 2001 21:57:12 +0200	[thread overview]
Message-ID: <01032921571206.00483@neo> (raw)
In-Reply-To: <01032910124007.00454@neo> <20010329133927.A9950@devserv.devel.redhat.com> <01032921132002.00483@neo>
In-Reply-To: <01032921132002.00483@neo>

Hi,

> > Hm, OK, then never mind. :) I don't have an opl3sa2 here to test
> > how well the current driver works.
> I have the feeling that there is going something wrong with the parameters.
> I modified the opl3sa2 driver and manually set the hw_config->io_base
> variable to 0x538 and now THIS part of the sound card initialization is
> working. But now it says that there is an I/O conflict with MSS. Maybe this
> parameter is also 0x0 and not  0x530 as I specified with the mss_io
> parameter... I will investigate further...

Hm... I found this somewhere near line 920 in opl3sa2.c. I am not a kernel 
hacker and this is first time I took a look into a kernel source code but 
this first "if" statement is not looking right to me. The initialization of 
the cfg[card] struct is what I need to be executed, but it is never executed 
because the variable "io" is never -1. I have removed the io == -1 condition 
from the first if-statement and now the driver is working. But it's still not 
the same quality as the one in kernel 2.2.17: I have no access to the mixer 
settings "bass" and "treble". But better than nothing and better than the 
8Bit-Soundblaster emulation. I hope this is working better in the next 
release.

                if(!isapnp && io == -1 ) {
                        if(io == -1 || irq == -1 || dma == -1 ||
                           dma2 == -1 || mss_io == -1) {
                                printk(KERN_ERR
                                       "opl3sa2: io, mss_io, irq, dma,  [...]
                                return -EINVAL;
                        }
 
                        cfg[card].io_base = io;
                        cfg[card].irq     = 0;
                        cfg[card].dma     = -1;
                        cfg[card].dma2    = -1;
                        [....]

-- 
Bye, K
[a735 47ec d87b 1f15 c1e9 53d3 aa03 6173 a723 e391]
(Finger k@ailis.de to get public key)

  reply	other threads:[~2001-03-29 20:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-29  8:12 opl3sa2 in 2.4.2 on Toshiba Tecra 8000 Klaus Reimer
2001-03-29 11:57 ` Jens Taprogge
2001-03-29 15:47 ` Bill Nottingham
2001-03-29 16:19   ` Klaus Reimer
2001-03-29 16:25     ` Bill Nottingham
2001-03-29 18:20       ` Klaus Reimer
2001-03-29 18:39         ` Bill Nottingham
2001-03-29 19:13           ` Klaus Reimer
2001-03-29 19:57             ` Klaus Reimer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-30 10:39 arobertson

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=01032921571206.00483@neo \
    --to=k@ailis.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=notting@redhat.com \
    /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