From: Paul Davis <paul@linuxaudiosystems.com>
To: alsa-devel@lists.sourceforge.net
Cc: thomas@undata.org
Subject: hdsp driver status
Date: Wed, 7 May 2003 22:04:08 -0400 [thread overview]
Message-ID: <200305080204.h48248c05344@linuxaudiosystems.com> (raw)
i finally got the information from RME to enable the mixer on the
hdsp-9652. i updated CVS, and the hdsp driver is totally
incompilable. somebody ripped out the definition of HDSP_IO_Type, and
then we have stuff like this:
../../alsa-kernel/pci/rme9652/hdsp.c:403: `HDSP_MATRIX_MIXER_SIZE' undeclared he
re (not in a function)
../../alsa-kernel/pci/rme9652/hdsp.c: In function `hdsp_read_gain':
../../alsa-kernel/pci/rme9652/hdsp.c:655: `HDSP_MATRIX_MIXER_SIZE' undeclared (f
irst use in this function)
../../alsa-kernel/pci/rme9652/hdsp.c:655: (Each undeclared identifier is reporte
d only once
../../alsa-kernel/pci/rme9652/hdsp.c:655: for each function it appears in.)
../../alsa-kernel/pci/rme9652/hdsp.c: In function `hdsp_write_gain':
../../alsa-kernel/pci/rme9652/hdsp.c:692: `HDSP_MATRIX_MIXER_SIZE' undeclared (f
irst use in this function)
../../alsa-kernel/pci/rme9652/hdsp.c: In function `snd_hdsp_set_defaults':
../../alsa-kernel/pci/rme9652/hdsp.c:3029: `HDSP_MATRIX_MIXER_SIZE' undeclared (
first use in this function)
../../alsa-kernel/pci/rme9652/hdsp.c: In function `snd_hdsp_hwdep_ioctl':
../../alsa-kernel/pci/rme9652/hdsp.c:3729: `hdsp_firmware_t' undeclared (first u
se in this function)
../../alsa-kernel/pci/rme9652/hdsp.c:3729: `firmware' undeclared (first use in t
his
can some fill me in on what is going on? why is the driver so totally broken?
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next reply other threads:[~2003-05-08 2:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 2:04 Paul Davis [this message]
2003-05-08 6:36 ` hdsp driver status Jaroslav Kysela
2003-05-08 9:15 ` Thomas Charbonnel
-- strict thread matches above, loose matches on Subject: below --
2003-07-03 11:12 Thomas Charbonnel
2003-07-03 11:45 ` Takashi Iwai
2003-07-03 13:55 ` Mark Knecht
2003-07-03 15:47 ` Patrick Shirkey
2003-07-03 16:15 ` Patrick Shirkey
2003-07-03 16:34 ` Patrick Shirkey
2003-07-03 16:42 ` Patrick Shirkey
2003-07-03 17:08 ` Justin Cormack
2003-07-03 17:23 ` jfm3
2003-07-03 18:57 ` Patrick Shirkey
2003-07-03 20:20 ` jfm3
2003-07-03 20:22 ` Thomas Charbonnel
2003-07-03 20:37 ` Mark Knecht
2003-07-04 1:20 ` Thomas Charbonnel
2003-07-04 3:07 ` Mark Knecht
2003-07-03 20:15 ` Thomas Charbonnel
2003-07-04 12:43 ` Justin Cormack
2003-07-04 13:18 ` Thomas Charbonnel
[not found] ` <1057325373.10858.77.camel@lotte>
[not found] ` <35748.217.128.161.242.1057327134.squirrel@www.undata.org>
2003-07-04 15:03 ` Justin Cormack
2003-07-05 3:35 ` jfm3
2003-07-05 8:29 ` Thomas Charbonnel
2003-07-05 15:19 ` jfm3
2003-07-06 3:15 ` jfm3
2003-07-06 9:33 ` Thomas Charbonnel
2003-07-09 4:24 ` Jesse Chappell
2003-07-09 4:49 ` Thomas Charbonnel
2003-07-03 20:13 ` Thomas Charbonnel
2003-04-14 9:55 Thomas Charbonnel
2003-04-14 13:00 ` Jeremy Hall
2003-04-14 13:16 ` Thomas Charbonnel
2003-04-14 13:24 ` Paul Davis
2003-04-14 19:51 ` Mark Knecht
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=200305080204.h48248c05344@linuxaudiosystems.com \
--to=paul@linuxaudiosystems.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=thomas@undata.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