The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Russ Dill <Russ.Dill@asu.edu>
To: Vivek Dasmohapatra <vivek@etla.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Breakage of opl3sax cards since 2.4.3 (at least)
Date: Wed, 02 May 2001 01:50:16 -0700	[thread overview]
Message-ID: <200105020850.BAA03703@smtp.asu.edu> (raw)
In-Reply-To: <Pine.LNX.4.10.10105020918260.18909-100000@www.teaparty.net>

On 02 May 2001 09:30:03 +0100, Vivek Dasmohapatra wrote:

> I have an isapnp opl3sax system [2.4.3-ac5] - the sound card
initialises

> fine, I just have to kick the second logical device with by cat'ing the
> following into /proc/isapnp:
> 
> card 0 YMH0802
> dev 0 YMH0022
> port 0 0x201
> activate
> 
> Which then activates the gameport: What are the contents of your
> /proc/isapnp? 


this sounds similar to my manual running of isapnp

> Of course, you have a YMH0020, and I have a YMH0021, that could be making
> all the difference.



not quite, you seem to have a YMH0802, while I have a YMH0802, what
error were you originally getting?
with mine, it doesn't want to isapnp it, so after I do that on my own, I
get:
russ kernel: opl3sa2: Control I/O port 0x240 is not a YMF7xx chipset!

anyway, I changed the above to:

card 0 YMH0020
dev 0 YMH0022
port 0 0x201
activate

does nothing...the diff between the two /proc/isapnp's are (the second
part of the first chunk and the last chunk are a result of me running
isapnp):

-Card 1 'YMH0020:OPL3-SAX Sound Board' PnP version 1.0
+Card 1 'YMH0802:YAMAHA OPL3-SAx Audio System' PnP version 1.0 
   Logical device 0 'YMH0021:Unknown'
     Device is active
     Active port 0x240,0xe80,0x388,0x300,0x100
-    Active IRQ 10 [0x2]
-    Active DMA 0,3
+    Active IRQ 5 [0x2] 
+    Active DMA 1,3 
     Resources 0
       Priority preferred
       Port 0x220-0x220, align 0xf, size 0x10, 16-bit address decoding
@@ -18,7 +18,7 @@
         Priority acceptable
         Port 0x240-0x240, align 0xf, size 0x10, 16-bit address decoding
         Port 0xe80-0xe80, align 0x7, size 0x8, 16-bit address decoding
-        Port 0x388-0x388, align 0x7, size 0x4, 16-bit address decoding
+        Port 0x388-0x388, align 0x3, size 0x4, 16-bit address decoding 
         Port 0x300-0x300, align 0x1, size 0x2, 16-bit address decoding
         Port 0x100-0xffe, align 0x1, size 0x2, 16-bit address decoding
         IRQ 5,7,2/9,10,11 High-Edge
@@ -49,5 +49,5 @@
         Priority acceptable
         Port 0x203-0x203, align 0x0, size 0x1, 16-bit address decoding
       Alternate resources 0:3
-        Priority functional
+        Priority acceptable 
         Port 0x204-0x20f, align 0x0, size 0x1, 16-bit address decoding




  reply	other threads:[~2001-05-02  8:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02  7:09 Breakage of opl3sax cards since 2.4.3 (at least) Russ Dill
2001-05-02  8:30 ` Vivek Dasmohapatra
2001-05-02  8:50   ` Russ Dill [this message]
2001-05-02  8:55     ` Vivek Dasmohapatra
  -- strict thread matches above, loose matches on Subject: below --
2001-05-01 22:39 David Bronaugh
2001-05-01 23:26 ` Vivek Dasmohapatra

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=200105020850.BAA03703@smtp.asu.edu \
    --to=russ.dill@asu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vivek@etla.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