From: "Martin Tufnel" <martin.tufnel@gmail.com>
To: alsa-devel@alsa-project.org
Subject: hdsp rpm support
Date: Mon, 26 May 2008 17:33:53 +1000 [thread overview]
Message-ID: <c62722740805260033t68f1ab1cu7ed5908f803fbacd@mail.gmail.com> (raw)
Hi All
I was wondering if there is any more news in regard to the development
effort toward supporting the RME HDSP RPM?
The last couple of emails I could find on the development were from
Karl Grill (please see below).
Does anyone know if Karl (or anyone else) is still working on this?
Thanks in advance for any help anyone can provide.
Regards, Martin
On Mon, 2008-02-25 at 08:45 +0100, Karl Grill wrote:
>* Dear Roman and all,
*>* I'm sorry i promised a little too much - in fact I was too busy with
*>* other things to get back to the rpm stuff in time; last night, I started
*>* to check the current state of affairs, and it looks quite promising; in
*>* the next three weeks, I won't have too much time to devote to this
*>* project, but then there's the University's easter break which I hope
*>* will give me the time to get things done, so, if all goes well, at least
*>* an experimental version should be ready by the end of March.
*
*
*On Tue, 2008-02-26 at 21:58 +0100, Karl Grill wrote:
> *Hi all,
> as a first step towards implementing support for the hdsp rpm, I've
> uploaded a patch to the alsa-firmware branch as bug report #3810.
> Besides the patch, I've put up the firmware binaries in .tar.gz format.
> This contains replacements for the rev.11 firmware for the
> digiface/multiface and also for the rpm. The latter is of little use
> right now, but I'd be very happy if anybody could try those for the
> digiface/multiface and report if it works, so I know if my assumptions
> on the drivers are correct.
>
> best regards
> kg
>
> PS. sorry I didn't file this report in the firmware section, but the web
> form there doesn't give me any usable choice for Category yet insists
> that I supply one.*
next reply other threads:[~2008-05-26 7:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 7:33 Martin Tufnel [this message]
2008-05-26 8:19 ` hdsp rpm support Roman Haefeli
2008-05-26 12:27 ` Martin Tufnel
[not found] ` <47321.137.248.1.11.1211815832.squirrel@webmail.naturestudies.eu>
2008-05-27 3:00 ` Martin Tufnel
2008-05-27 6:14 ` Florian Faber
2008-05-27 12:59 ` Martin Tufnel
2008-05-27 13:08 ` Florian Faber
2008-05-28 12:58 ` Martin Tufnel
2008-05-27 13:46 ` Roman Haefeli
2008-05-28 13:01 ` Martin Tufnel
2008-05-30 16:15 ` Karl Grill
2008-05-27 11:45 ` Roman Haefeli
2008-05-27 13:02 ` Martin Tufnel
-- strict thread matches above, loose matches on Subject: below --
2012-01-18 9:05 Roman Haefeli
2012-01-18 10:26 ` Fons Adriaensen
2012-01-18 10:54 ` Roman Haefeli
2012-02-13 15:06 ` Adrian Knoth
2012-02-14 23:07 ` Roman Haefeli
2012-05-17 13:21 ` Roman Haefeli
2012-12-30 12:09 ` Adrian Knoth
2013-01-24 23:21 ` Roman Haefeli
2012-09-30 23:04 ` Roman Haefeli
2012-10-01 8:05 ` Florian Faber
2012-10-01 20:00 ` Roman Haefeli
2012-11-18 17:30 ` Karl Grill
2012-11-20 7:57 ` Roman Haefeli
2007-12-11 11:21 kgrill
2007-12-11 17:01 ` Roman Haefeli
2008-02-25 7:45 ` Karl Grill
2008-02-25 15:50 ` Roman Haefeli
2008-02-20 13:54 ` Roman Haefeli
2007-12-10 0:48 Roman Haefeli
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=c62722740805260033t68f1ab1cu7ed5908f803fbacd@mail.gmail.com \
--to=martin.tufnel@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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).