All of lore.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 20:20:23 +0200	[thread overview]
Message-ID: <01032920202300.00483@neo> (raw)
In-Reply-To: <01032910124007.00454@neo> <0103291819180K.00454@neo> <20010329112507.A27209@devserv.devel.redhat.com>
In-Reply-To: <20010329112507.A27209@devserv.devel.redhat.com>

Hi,

> > modprobe opl3sa2 io=0x538 mss_io=0x530 mpu_io=0x330 irq=5 dma=1 dma2=0
> > isapnp=0
> It would be what you put in the io= parameter. 0x538 does *not* look
> right.

These are the sound-settings in the BIOS:

WSS I/O: 0x530
SBPro I/O: 0x220
Synth I/O: 0x388
IRQ: 5
WSS (Play) DMA: 1
WSS (Rec) DMA & SBPro-DMA: 0
Control I/O: 0x538
MPU I/O: 0x330

The BIOS does not let me modify the I/O settings for Synth, Control and MPU. 
And as I said: The opl3sa2 module was working perfectly in kernel 2.2.17 with 
these settings. And I wonder why the message in syslog says "0x0", no matter 
what I/O address I have specified with the io= parameter.

-- 
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 18:23 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 [this message]
2001-03-29 18:39         ` Bill Nottingham
2001-03-29 19:13           ` Klaus Reimer
2001-03-29 19:57             ` Klaus Reimer
  -- 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=01032920202300.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.