From: Takashi Iwai <tiwai@suse.de>
To: Benny Sjostrand <gorm@cucumelo.org>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Hercules Game Theater - cs4630
Date: Thu, 04 Jul 2002 09:35:15 +0200 [thread overview]
Message-ID: <s5h65zwrln0.wl@alsa2.suse.de> (raw)
In-Reply-To: <3D23675F.7070204@cucumelo.org>
At Wed, 03 Jul 2002 23:06:39 +0200,
Benny Sjostrand wrote:
>
> My first thought was that it would be a easy match to make the
> Hercules Game Theater XP sound card work on Linux. My goal is to make
> the SPDIF IN-OUT interface work, and the multichannel PCM improving the
> current alsa cs46xx driver, and then go on with other advanced codec
> stuffs (hopefully finish before i die ...)
> Now a couple of days browsing the alsa source code and reading a lot
> of borring HW datasheet of must all Cirrus CS4xxx chips it just dont
> feel possible to find any easy solution.
> In the Cirrus collection of manuals and datasheet i have found a lot
> HW specifications and reference design documents for the CS4630 chip,
> and the codecs CS4694, CS4697 and so on. But what about the programmers
> guide, does it not exist any open document like "CS4630 Programmers
> Manual", or something similar, where it explain how to program the DSP
> ?? or is that not public ???
no.
> Then i've sent mail to Cirrus and Hercules, of course without any
> response (yet) ....
i've been asking to cirrus logic many times, but no responce, too.
apparently cirruslogic has no interest in this chip at all, since
they stopped producing this chip.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Caffeinated soap. No kidding.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-04 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 21:06 Hercules Game Theater - cs4630 Benny Sjostrand
2002-07-04 7:35 ` Takashi Iwai [this message]
2002-07-05 21:16 ` Benny Sjostrand
2002-07-04 9:20 ` Jaroslav Kysela
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=s5h65zwrln0.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=gorm@cucumelo.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.