From: Alex Davis <alex14641@yahoo.com>
To: riesen@synopsys.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.16 alsa 0.5.12 mixer ioctl problem
Date: Tue, 27 Nov 2001 00:49:34 -0800 (PST) [thread overview]
Message-ID: <20011127084934.11076.qmail@web9207.mail.yahoo.com> (raw)
Yeah, they changed/broke (depending on your point of view) the file fs/proc/inode.c in the kernel
source.
You're the third person to post about this problem.
There's a work-around for the problem. (I'm currently running ALSA 0.9beta9, so the file contents
may not exactly match up): in the ALSA driver source, edit the file kernel/info.c. Look for the
following lines
if (p) {
snd_info_device_entry_prepare(p,entry);
#ifdef LINUX_2_3
p->proc_fops = &snd_fops;
#else
p->ops = &snd_info_device_inode_operations;
#endif
} else {
up(&info_mutex);
snd_info_free_entry(entry);
return NULL;
}
}
they should be near line 890 or so.
Next, comment out the line
p->proc_fops = &snd_fops;
Rebuild. Everything should work now.
Hope this helps.
-Alex
Alex Reisen wrote
Hi, all
just tried to compile the mentioned alsa drivers under 2.4.16. Mixer doesnt work, yes. It
compiles, installs, loads. And
any program trying to open mixer (through libasound) get EINVAL.
All is compiled with gcc-2.95.3,
single CPU, with APIC (is any sense to enable it on
uniprocessors?).
Does anybody know what to do about it?
-alex
__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1
next reply other threads:[~2001-11-27 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 8:49 Alex Davis [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 8:23 2.4.16 alsa 0.5.12 mixer ioctl problem Duncan Sands
2001-11-27 7:11 Alex Riesen
2001-11-27 8:05 ` Jochen Eisinger
2001-11-28 7:16 ` Alex Riesen
2001-11-27 9:06 ` Helge Hafting
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=20011127084934.11076.qmail@web9207.mail.yahoo.com \
--to=alex14641@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riesen@synopsys.com \
/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.