From: Thomas Charbonnel <thomas@undata.org>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: HDSP 9632 driver and expansion cards
Date: Wed, 21 Jan 2004 16:08:34 +0100 [thread overview]
Message-ID: <400E95F2.2070103@undata.org> (raw)
In-Reply-To: <200401211316.i0LDGmqh009083@dhin.linuxaudiosystems.com>
Paul Davis a écrit :
>>Anyone using the latest RME HDSP 9632 driver in ALSA, while also using
>>the expansion cards? I mean, the newer AI4S-192 and/or AO4S-192 which
>>are required to get the 192kHz sampling on all analogs.
>>
>>Do the latest expansion cards (192kHz) work with the latest ALSA driver?
>
>
> i doubt it. RME have not given us any information about this new
> hardware. i suggest that you write to them and ask that they give me
> and/or thomas charbonnel the required information.
>
>
>>In general, are the ALSA drivers ready to support any kind of expansion
>>cards on the HDSP 9632 / HDSP 9652?
>
>
> they are "ready to support" in the sense that it probably isn't that
> much work, but they do not currently do so.
>
> --p
>
To clarify the situation : I already asked for and got this information
while working on the H9632 driver. The code to support those expansion
boards is already in the driver, and also in hdspmixer and hdspconf, the
only thing is that this is untested. I also added traditional (old)
expansion boards support for H96xx cards (you have to activate the board
using hdspconf or amixer).
Thomas
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
prev parent reply other threads:[~2004-01-21 15:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 2:07 HDSP 9632 driver and expansion cards Florin Andrei
2004-01-21 12:47 ` Thomas Charbonnel
2004-01-21 18:41 ` Ed Wildgoose
2004-01-21 18:55 ` Florin Andrei
2004-01-22 15:06 ` Ed Wildgoose
2004-01-23 6:27 ` Florin Andrei
2004-01-21 19:20 ` Paul Davis
2004-01-21 21:23 ` Thomas Charbonnel
2004-01-22 15:32 ` Ed Wildgoose
2004-01-22 22:46 ` Edward Wildgoose
2004-01-23 10:20 ` Thomas Charbonnel
2004-01-23 17:16 ` Ed Wildgoose
2004-01-23 20:19 ` Edward Wildgoose
2004-01-24 12:56 ` Thomas Charbonnel
2004-01-24 11:51 ` Thomas Charbonnel
2004-01-24 21:10 ` Edward Wildgoose
2004-01-21 13:16 ` Paul Davis
2004-01-21 15:08 ` Thomas Charbonnel [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=400E95F2.2070103@undata.org \
--to=thomas@undata.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.com \
/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.