alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Kletschke <konsti@ku-gbr.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: A: VIA Technologies Inc. VT1720/24
Date: Thu, 25 Jan 2007 13:36:21 +0100	[thread overview]
Message-ID: <20070125123620.GA8634@synertronixx3> (raw)
In-Reply-To: <20070125101319.GA3340@titan.lahn.de>

Well actually I am fiddling around with the same card also. Since
nobody responded here in this mailing list anymore I went into

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2384

and evolved a separate prodigy_hifi.c which is quite redundant due to
the simialirities but I have to get know to als coding and wanted to
clean up later. This here looks clean and seems to work though.

I went back here Raymond pointing me to the alsa-devel archive. This
is the first mail which arrives at my mail account so I answer now
here.

I applied your stuff onto alsa-driver-1.0.14rc2.

Am 2007-01-25 11:13 +0100 schrieb Philipp Matthias Hahn:

> Yes, see below. Three more questions:
> 1. Since the "Aureon7.1", "Prodigy7.1" and my "Prodigy7.1HiFi"; as well
> as the "Prodigy7.1LT" and the "Prodigy7.1XT" respectively seem so share
> the same EEPROM-Date, wouldn't it be better to re-use/share those
> eeprom-data instead of declaring them 3 respectively 2 times?

In my opinion Prodigy7.1HiFi eeprom_ data has to be slightly
different, I need to put 

[ICE_EEP2_SYSCONF] = 0x4b

instead of

[ICE_EEP2_SYSCONF] = 0x0b

Otherwise I got speeded up sound playback.
See note (0014172) in this thread by me.

What I am currently fiddling about is the CS8415A Chip:

ALSA /XXX/alsa-kernel/pci/ice1712/aureon.c:1921: No CS8415
chip. Skipping CS8415 controls.

In the note (0014176) I am trying to search it at the i2c address it
should appear at. Still I did not found it :-)

Regards, Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2007-01-25 12:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45AFE785.6020307@informatik.uni-oldenburg.de>
2007-01-24 12:10 ` A: VIA Technologies Inc. VT1720/24 Philipp Matthias Hahn
2007-01-24 15:12   ` [Alsa-devel] " Takashi Iwai
2007-01-25 10:13     ` Philipp Matthias Hahn
2007-01-25 11:19       ` Takashi Iwai
     [not found]         ` <20070126202950.GA5721@titan.lahn.de>
2007-01-29 14:41           ` Takashi Iwai
2007-01-29 15:30             ` Konstantin Kletschke
2007-01-29 15:33               ` Konstantin Kletschke
2007-01-29 15:55                 ` Subject: Does anyone know if this chipsset VT82C686 will output 24 bit, 96 kHz to USB 1.1 or pcmcia card...using a Linux 2.4 platform marion rundell
2007-01-29 15:43               ` A: VIA Technologies Inc. VT1720/24 Takashi Iwai
2007-01-29 16:45                 ` Konstantin Kletschke
2007-02-14 15:30             ` Takashi Iwai
2007-02-14 15:49               ` Konstantin Kletschke
2007-01-25 12:36       ` Konstantin Kletschke [this message]
2007-01-25 14:22         ` Konstantin Kletschke
2007-01-25 19:58       ` Konstantin Kletschke

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=20070125123620.GA8634@synertronixx3 \
    --to=konsti@ku-gbr.de \
    --cc=alsa-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).