alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: ALSA developers <alsa-devel@lists.sourceforge.net>
Subject: Re: A: VIA Technologies Inc. VT1720/24
Date: Mon, 29 Jan 2007 16:30:12 +0100	[thread overview]
Message-ID: <20070129153011.GA2831@synertronixx3> (raw)
In-Reply-To: <s5hbqkhq4i6.wl%tiwai@suse.de>

I am here *wink* :-)

Am 2007-01-29 15:41 +0100 schrieb Takashi Iwai:

> But the patch for Prodigy 7.1 Hifi is still pending since another
> deveopment by Konstantin is ongoing, too.  Could you both of you
> cooperate to make more solid support for that hardware?

Well, I strongly recommend. As I asked before, I am still wondering
how the initial patch works on Philipps Computer. 

While the wm8776 is implementend as a SPI device in aureon.c (and used
this way in the Prodigy 7.1 Hifi driver in aureon.c here) I use it in
i2c mode with success. What still missing is spi read/write stuff for
the wm8766 I am currently working on. Also there is a cs8415a in i2c
mode connected, whereas aureon.c expects it in SPI mode currently. 

Due to that essential differences I started a (quite good working!)
skeleton based on a Hercules fortissmo4 approach I discovered in
bugtrack.alsa-project.org. There I went into a prodigy hifi thread 
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2384
and put in my prodigy_hifi.c (which envolved meanwhile) for discussion.

> Of course, I can take one of your patches as a prototype, and make
> it

I really wonder how/if Philipps stuff works. It gives a working card,
but (as I expected) the main volume mixers are not working. All
essential chips known to be connected in SPI mode need to be
initialized to speak i2c on this board.

> merged to the standard tree as a start up.  Anyway, I'd like hear the
> opinions from both of you at first.

May be Philps patch needs only slight work, my approach of a
completely additional file prodigy_hifi.c might be most probably work
of greenhorn in hacking alsa device drivers, so I am here for
discussion. At the moment I am trying to get hands onto the wm8766
chip, which needs proper SPI functions. I can nowhere adopt existing
ones as far as I can see.

Kind Regards, Konstantin Kletschke

PS.: Takashi, the mail you are replying to, has this gone to this ml
or to you directly?


-- 
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

  reply	other threads:[~2007-01-29 15:30 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 [this message]
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
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=20070129153011.GA2831@synertronixx3 \
    --to=lists@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).