Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Michael Haller <mhaller@acm.org>
To: linux-sound@vger.kernel.org
Subject: Re: help needed for cs423x chips
Date: Mon, 14 Dec 1998 04:38:11 +0000	[thread overview]
Message-ID: <marc-linux-sound-91361053406131@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91325015828495@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

> On Sat, 12 Dec 1998, Tony Nugent wrote:
> 
> > options -k cs4232 io=0x530 dma=1 dma2=0 irq=5
> > # no midi yet :(
> >
> > This works for the audio driver, but I have yet to get the midi to work.
> options cs4232 io=0x530 irq=7 dma=1 dma2=0 mpuirq=9 mpuio=0x330
>
> <Crystal audio controller (CS4236)> at 0x530 irq 7 dma 1,0
> <MPU-401 (UART) MIDI> at 0x330 irq 9
>
> ps anyone know how to get the sequencer working on these things?

Audio support of the CS4235 with the existing CS4232 driver will not
work because the 4235 does not support ulaw, alaw or adpcm.  sequencer
support probably doesn't work for any of the crystal chips because of a
code ordering problem in cs4232.c.   I'm attaching a patch file for
2.1.131 which fixes these problems on my CS4235.

As Tony and Keith point out, all the settings must be correct.  I use:

modprobe cs4232 io=0x530 irq=5 dma=0 dma2=1 mpuio=0x330 mpuirq=9
modprobe opl3 io=0x388

Let me know how this works.

Mike Haller

[-- Attachment #2: patch-cs4235.gz --]
[-- Type: application/x-gzip, Size: 1936 bytes --]

  parent reply	other threads:[~1998-12-14  4:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-08 23:49 help needed for cs423x chips moc liamtoh
1998-12-09  0:12 ` moc liamtoh
1998-12-10  0:35 ` Matthew B. Marlowe
1998-12-10  5:28 ` William Law Kar Wai
1998-12-10  7:02 ` Etienne Grossmann
1998-12-11 16:32 ` Tony Nugent
1998-12-12 15:24 ` D Sen
1998-12-13  5:32 ` Keith Duthie
1998-12-14  4:38 ` Michael Haller [this message]
1998-12-15  8:10 ` Keith Duthie
1998-12-16  6:26 ` Keith Duthie
1998-12-16  6:26 ` Keith Duthie

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=marc-linux-sound-91361053406131@msgid-missing \
    --to=mhaller@acm.org \
    --cc=linux-sound@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox