From: "moc liamtoh" <mackilla@hotmail.com>
To: linux-sound@vger.kernel.org
Subject: Re: Crystal CS4235 with 2.2.0-pre7
Date: Mon, 18 Jan 1999 12:05:26 +0000 [thread overview]
Message-ID: <marc-linux-sound-91669060300940@msgid-missing> (raw)
i have the same chip (aopen MB) and i had problems too, (i use the
2.0.36) but i got it to werk by swapping the dma's so that i had 534,
irq 5, dma=1 and dma2=0 and that, oddly enough, seemed to work...and not
that bad either...altough i have on board video also and when i was
trying to use that it would get very bad sound....
regards,
Josh
<SNIP>
>Hi,
>
>Alan Cox stated a few weeks ago that there is support for the Crystal
>soundchip CS4235 in kernel 2.1.132ac1. I have an Acer motherboard with
>this chip and so decided to make the latest available kernel
>linux-2.2.0-pre7.
>
>I found no references to CS4235 and so took the closest config option
>CS4232.
>
>Unfortunately
>
>cat /usr/lib/xemacs-20.4/etc/sounds/im_so_happy.au > /dev/audio
>
>simply gave silence.
>
>I would be very glad if someone out there could give me advice.
>
>Kind regards
>
>Gerd
>
>Here are the details:
>
>To avoid module trouble I made a kernel with builtin support for
>CS4232. These are my defines:
>
>CONFIG_SOUND_CS4232=y
>CONFIG_CS4232_BASES4
>CONFIG_CS4232_IRQ=5
>CONFIG_CS4232_DMA=0
>CONFIG_CS4232_DMA2=1
>CONFIG_CS4232_MPU_BASE:8
>CONFIG_CS4232_MPU_IRQ=9
>
<SNIP>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
next reply other threads:[~1999-01-18 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-18 12:05 moc liamtoh [this message]
1999-01-18 18:54 ` Crystal CS4235 with 2.2.0-pre7 Gerd Bavendiek
1999-01-19 3:16 ` Tony Nugent
1999-01-19 7:57 ` Gerd Bavendiek
1999-01-19 8:02 ` Gerd Bavendiek
1999-01-22 7:53 ` Gerd Bavendiek
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-91669060300940@msgid-missing \
--to=mackilla@hotmail.com \
--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