Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: CAG <cag@fsk-hh.org>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: M-Delta Audiophile 192 (ice1724) Recording
Date: Mon, 04 Feb 2008 18:37:48 +0100	[thread overview]
Message-ID: <47A74D6C.9030100@fsk-hh.org> (raw)
In-Reply-To: <s5hejbs3gqm.wl%tiwai@suse.de>



Takashi Iwai schrieb:
> At Mon, 04 Feb 2008 15:31:10 +0100,
> CAG wrote:
>> hi,
>>
>> Takashi Iwai schrieb:
>>> At Thu, 31 Jan 2008 23:51:19 +0100,
>>> Computer AG im FSK wrote:
>>>> Hi,
>>>>
>>>> I  forget to mention that we patched
>>>> /usr/local/src/alsa-driver-1.0.16rc2/alsa-kernel/pci/ice1712/revo.c
>>>> instead of
>>>> /usr/local/src/alsa-driver-1.0.16rc2/pci/ice1712/revo.c
>>>>
>>>> because /usr/local/src/alsa-driver-1.0.16rc2/pci/ice1712/revo.c is just
>>>> 3 lines long or so and looks like including
>>>> /usr/local/src/alsa-driver-1.0.16rc2/alsa-kernel/pci/ice1712/revo.c.
>>>>
>>>> Does this matter ?
>>> No, it's the right place to apply.
>>>
>>> So far, I have no further idea what could be wrong.  It's really hard
>>> to debug remotely without hardware and without any datasheet... >
>>>
>>> Takashi
>> We get this card working with O.S.S., recording works now. Anyway, OSS 
>> is not our preferred sound system...
> 
> If the GPL'ed version of OSS works, then we can see the driver code.
> Could you check whether it works?  If we have a reference source, it
> will be greatly helpful to debug.
Ok, we will check this this week. I found a link to "Envy24 under 
FreeBSD", where details specs and the driver code are listed:
http://envy24.svobodno.com/driver/envy24ht/

But I will get back to you as soon as we tested the GPL Version.

> 
>> We would like to know if there will be future development for this card. 
>> We bought 4 cards for our studio, it really would help us out.
>>
>> Is there any way to support the alsa project to fix this issue ? What 
>> about our offer to lend a card for development ? Our finances aren't 
>> very well but  we could also think about a small donation for hardware 
>> i.e.
> 
> Well, the problem is another one - the lack of the hardware
> information such as datasheet.  The codec chip itself is known but the
> connection of the chip is unknown.  This is what M-audio knows at
> best.  Or you can track the pin connections on your board...
> 
> Above all, the most missing thing for me is the time.  I'm willing to
> help you but have likely too little time.  I hope someone else could
> help more intensively...
Well I can imagine... :)

Toast
> 
> 
> Takashi

  reply	other threads:[~2008-02-04 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 22:06 M-Delta Audiophile 192 (ice1724) Recording Computer AG im FSK
2008-01-31 22:51 ` Computer AG im FSK
2008-02-01 12:17   ` Takashi Iwai
2008-02-04 14:31     ` CAG
2008-02-04 15:04       ` Takashi Iwai
2008-02-04 17:37         ` CAG [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-28 12:29 CAG
2008-01-30 12:07 ` Takashi Iwai
2008-01-30 13:52   ` CAG
2008-01-31 15:44   ` CAG
2008-01-31 16:16     ` Takashi Iwai
2008-01-31 17:12       ` CAG
     [not found]       ` <47A2014A.1040107@fsk-hh.org>
2008-01-31 17:26         ` Takashi Iwai
2008-01-31 17:33           ` CAG
2008-01-31 17:36             ` Takashi Iwai

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=47A74D6C.9030100@fsk-hh.org \
    --to=cag@fsk-hh.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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