All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: a9830608@unet.univie.ac.at
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: audiophile 192 alsa driver
Date: Wed, 09 Feb 2005 11:07:12 +0100	[thread overview]
Message-ID: <s5hacqet5bj.wl@alsa2.suse.de> (raw)
In-Reply-To: <42099E72.3070105@unet.univie.ac.at>

At Wed, 09 Feb 2005 06:24:02 +0100,
Hartwig Krebitz wrote:
> 
> Hello!
> 
> First of all: Thanks for your mail.
> 
> concerning M-Audio:
> 
> I've posted an inquiry one week ago. I got a standard
> reply: ... can't provide support ... third party
> developers blabla ...
> 
> Today i received another similar reply from the M-Audio support team.
> I wrote back and tried to point out the problem once again - No answer
> so far.

Please give them my address as the contact of ALSA, too.
I knew some people in M-Audio, but lost contact recently.

> concerning codec chips:
> 
> What exactly do you mean by codec chips? - A listing of all chips on the
> board, including all id numbers? - I should be able to provide one then.

Yes, we need to know what chips are equipped on the board.

You might find a similar board with the same chips by searching
through the source codes of pci/ice1712/*.c.  Try model=xxx module
option where xxx is the board model type.

If no existing board type matches, we need to write the codec support
code newly.  For that, the information of pin connections is
required.  That is, which (GPIO) pin of VT172x is wired to which pin
of each codec chip.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      reply	other threads:[~2005-02-09 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05 14:51 audiophile 192 alsa driver Hartwig Krebitz
2005-02-08 20:09 ` Takashi Iwai
2005-02-09  5:24   ` Hartwig Krebitz
2005-02-09 10:07     ` Takashi Iwai [this message]

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=s5hacqet5bj.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=a9830608@unet.univie.ac.at \
    --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 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.