From: terminator356@users.sourceforge.net
To: alsa-devel@lists.sourceforge.net
Subject: A FIX FOR alsa-lib emu10k1.h (IT FIXES ld10k1)
Date: Wed, 17 Jan 2007 00:12:07 -0500 [thread overview]
Message-ID: <200701170012.07474.terminator356@users.sourceforge.net> (raw)
Hi, ld10k1 doesn't work, crashes. Lots of people saying it.
In the alsa-kernel/include emu10k1.h,
union {
snd_kcontrol_tlv_rw_t *c;
unsigned int *p;
} tlv;
was added to struct 'snd_emu10k1_fx8010_control_gpr'.
But alsa-lib/include/sound/emu10k1.h was not changed.
So I did this:
...
unsigned int min; /* minimum range */
unsigned int max; /* maximum range */
unsigned int *p; // <----- ADDED THIS <----------------
unsigned int translation; /* translation type (EMU10K1_GPR_TRANSLATION*) */
} emu10k1_fx8010_control_gpr_t;
which is in alsa-lib/include/sound/emu10k1.h
For me, it fixes ld10k1. *p acts as a placeholder because it is useless
(at this point) to ld10k1.
----Can you tell me what those changes were for? What are *c and *p ? ---
Thanks. Tim.
terminator356 -> users -> sourceforge -> net
(Developer on ld10k1 project).
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2007-01-17 5:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 5:12 terminator356 [this message]
2007-01-17 12:35 ` A FIX FOR alsa-lib emu10k1.h (IT FIXES ld10k1) Takashi Iwai
2007-01-18 11:08 ` Takashi Iwai
2007-01-19 1:17 ` Tim
2007-01-19 11:13 ` Takashi Iwai
2007-01-19 23:14 ` Tim
2007-01-22 9:50 ` Takashi Iwai
2007-01-18 22:58 ` James Courtier-Dutton
2007-01-19 17:41 ` Takashi Iwai
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=200701170012.07474.terminator356@users.sourceforge.net \
--to=terminator356@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
/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.