From: Ben Pfaff <pfaffben@msu.edu>
To: Alan Cox <alan@redhat.com>
Cc: lukas@edeal.de (Lukas Schroeder),
zab@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] ess maestro, support for hardware volume control
Date: 09 Jun 2001 17:23:13 -0400 [thread overview]
Message-ID: <87elst2vr2.fsf@pfaffben.user.msu.edu> (raw)
In-Reply-To: <200106091931.f59JVw731673@devserv.devel.redhat.com>
In-Reply-To: Alan Cox's message of "Sat, 9 Jun 2001 15:31:58 -0400 (EDT)"
Alan Cox <alan@redhat.com> writes:
> > this patch applies to (at least) 2.4.3 up to and including 2.4.6-pre2.
> > It enables the hardware volume control feature of the maestro.
>
> it doesnt apply to the current version of the maestro driver (2.4.5-ac)
> however. I think it is clashing with the docking station support
Yeah, it does--I included support for the hwv control in the
docking patch. I used a different technique though because I
couldn't get the technique used by Lukas's patch to work properly
for me.
I now have a patch that will output the hwv buttons pressed (up,
down, mute) to a new dynamically allocated misc device as letters
u, d, m, instead of directly modifying the mixer. Anyone want
that? It's more flexible than either the patch that's currently
in -ac or Lukas's patch, but you need a little userspace daemon
for it to do anything useful.
BTW, what is the officially approved way to open a device on a
dynamic misc minor? Reading /proc/misc for the minor number,
then mknod'ing a device and opening it seems to me to have a
nasty race condition, am I missing something here?
next prev parent reply other threads:[~2001-06-09 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 17:09 [patch] ess maestro, support for hardware volume control Lukas Schroeder
2001-06-09 17:25 ` Zach Brown
2001-06-09 18:16 ` Lukas Schroeder
2001-06-09 18:50 ` Zach Brown
2001-06-09 18:58 ` Alan Cox
2001-06-09 19:31 ` Alan Cox
2001-06-09 21:23 ` Ben Pfaff [this message]
2001-06-09 22:52 ` Zach Brown
2001-06-10 10:10 ` Abramo Bagnara
2001-06-09 23:36 ` Alan Cox
2001-06-10 3:43 ` Ben Pfaff
2001-06-10 13:08 ` Alan Cox
2001-06-10 17:53 ` Riley Williams
2001-06-12 12:31 ` Lukas Schroeder
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=87elst2vr2.fsf@pfaffben.user.msu.edu \
--to=pfaffben@msu.edu \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@edeal.de \
--cc=zab@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox