All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Nottingham <notting@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: opl3sa2 in 2.4.2 on Toshiba Tecra 8000
Date: Thu, 29 Mar 2001 11:25:08 -0500	[thread overview]
Message-ID: <20010329112507.A27209@devserv.devel.redhat.com> (raw)
In-Reply-To: <01032910124007.00454@neo> <20010329104710.A18159@devserv.devel.redhat.com> <0103291819180K.00454@neo>
In-Reply-To: <0103291819180K.00454@neo>; from k@ailis.de on Thu, Mar 29, 2001 at 06:19:18PM +0200

Klaus Reimer (k@ailis.de) said: 
> If I am doing this, I can't even load the module and I get the following 
> message in syslog:
> 
> 2001-03-29 18:13:14.184156500 {kern|err} kernel: opl3sa2: Control I/O port 
> 0x0 not free
> 
> What is that "control i/o port"? Is this normally 0x100?

I believe it can be, but I remember it usually being something
like 0x370 or so.

> What is the module 
> parameter to specify this io port? The documentation only mentions "io", 
> "mpu_io" and "mss_io" but I have specified these parameters already:
> 
> 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.

Bill

  reply	other threads:[~2001-03-29 16:27 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 [this message]
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
  -- 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=20010329112507.A27209@devserv.devel.redhat.com \
    --to=notting@redhat.com \
    --cc=linux-kernel@vger.kernel.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 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.