All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Leonard <jonathan.adams.leonard@gmail.com>
To: alsa-devel@alsa-project.org
Subject: RME HDSPe AIO
Date: Sun, 8 Nov 2009 11:38:08 -0800	[thread overview]
Message-ID: <1401522d0911081138i2ebf7aa8h4467a135c93a526@mail.gmail.com> (raw)

Hello, I am writing in regards to the RME HDSPe AIO card and its support in
ALSA.  The card itself in 64studio is recognized incorrectly as HDSP MADI
rev d4.

Running lspci -nn shows this line for the device:

02:00.0 Multimedia audio controller [0401]: Xilinx Corporation RME
Hammerfall DSP MADI [10ee:3fc6] (rev d4)

ALSA in 64studio 3.0 beta 3 loads snd-hdspm incorrectly when it should be
loading snd-hdsp.

I have reviewed pcitables and pci.ids on this distro, and also the public
pci reference and the above device id is currently assigned to:

Multimedia audio controller: Xilinx Corporation RME Hammerfall DSP MADI (rev
d4)

The AIO is purported to be very similar to the 9632 and should be using the
snd-hdsp module.

I would like to use this card in ALSA, and have begun reviewing the guide
for making ALSA drivers, but am not sure how exactly to fix the matter since
the manufacturer has not incremented the id, or they have not assigned the
same id as a 9632.  This device is recognized and functioning perfectly on
the XP partition.

Besides my individual circumstance I wonder if ALSA should not be
accomodating this great card somehow.

Let me know if I can help by contacting RME developers for info or
otherwise.

Thank you,

jonathan adams leonard

             reply	other threads:[~2009-11-08 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 19:38 Jonathan Leonard [this message]
2009-11-08 19:44 ` RME HDSPe AIO Florian Faber
2009-11-08 20:00   ` Jonathan Leonard
     [not found] <mailman.2708.1257713283.2074.alsa-devel@alsa-project.org>
2009-11-08 21:30 ` Demian Martin
2009-11-09  9:55   ` Florian Faber
2009-11-09 19:56     ` Jonathan Leonard
2009-11-10  9:52     ` Pavel Hofman

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=1401522d0911081138i2ebf7aa8h4467a135c93a526@mail.gmail.com \
    --to=jonathan.adams.leonard@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 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.