From: Roman Haefeli <reduzent@gmail.com>
To: Fons Adriaensen <fons@linuxaudio.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: hdsp rpm support
Date: Wed, 18 Jan 2012 11:54:00 +0100 [thread overview]
Message-ID: <1326884040.18308.6.camel@yoyo4> (raw)
In-Reply-To: <20120118102658.GA5351@linuxaudio.org>
Hi Fons
I'm glad to hear about people having success with this issue.
On Wed, 2012-01-18 at 10:26 +0000, Fons Adriaensen wrote:
> On Wed, Jan 18, 2012 at 10:05:59AM +0100, Roman Haefeli wrote:
>
> > I would like to know current state of the RME HDSP RPM support. There
> > was a thread [1] in 2008 on this list about the issue and things looked
> > promising back then. However, I'm still unable to upload the firmware
> > with alsa-driver from git on my Ubuntu 11.04 (32bit) machine with a
> > 2.6.38 kernel. I posted a detailed description of the issue on the
> > alsa-user list here [2].
>
> It seems that the developer of the driver - Adrian Knoth - has
> two versions: one that works for me, and one that works for
> another user.
>
> AFAICS, the problem is with the code that identifies the card
> as an RPM, Multiface or Digiface, and that triggers ths HW into
> accepting the firmware. Once past this point everything works
> perfectly, including switching the phone preamps etc.
I can confirm this. When I upload the firmware with Windows, I can fully
use the card and a recent 'hdspmixer' shows me the correct number of
channels. However, the culprit seems to be uploading the firmware.
> I've use it with both Cardbus and ExpressCard.
Good to hear.
May I ask kindly for the 'other' version of the driver, which I would be
happy to test?
>
> One more user would probably help...
I'm willing to test and report back (as much as I can as a non-dev).
Roman
next prev parent reply other threads:[~2012-01-18 10:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 9:05 hdsp rpm support Roman Haefeli
2012-01-18 10:26 ` Fons Adriaensen
2012-01-18 10:54 ` Roman Haefeli [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-05-26 7:33 Martin Tufnel
2008-05-26 8:19 ` 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
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=1326884040.18308.6.camel@yoyo4 \
--to=reduzent@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=fons@linuxaudio.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).