linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: "Joseph P. Garcia" <jpgarcia@execpc.com>,
	Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: powermac (other ppc?) events
Date: Thu, 19 Jul 2001 23:36:44 +0100	[thread overview]
Message-ID: <20010719223636.DAB40DBB56@atlas.valhalla.net> (raw)


> work as well.  As is, volume keys seem to rank low in the priority queue.
> something to get practice on.

Look, I don't have a proper opinion on how the keys are achieved ...

---

all I want is that the sound driver is:

1/ called through the standard ioctl() for volume - however many "volumes"
you want to adjust.

This is so that *your* interface will work with *any* dmasound-supported
hardware (without hacking dmasound for each chipset).

We currently support 3 1/2 chipsets - with two more in the pipeline + Apple
is releasing sound hardware variants faster than we can keep up with the
driver already ;-))

also think about how it might interact with USB audio ...

you ***really*** ***don't*** want to go down the road of hacking every sound
driver for volume keys.


2/ Let dmasound handle the headphone insertion - it is already dealing with
the hardware and the appropriate interrupts.

By all means - if there is a consensus that we *need* User Control over
whether headphone insertion disables the internal speaker (or not) - then I
am happy to use one of the OSS "special purpose" ioctl() values to control
this as a PMac-specific feature - which will work properly via the proper
ioctl().

just my 0.02 euro ...

but I am (at least unofficially) maintaining the driver at the moment.

ciao,
Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-07-19 22:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19 22:36 Iain Sandoe [this message]
2001-07-20  9:22 ` powermac (other ppc?) events Michael Schmitz
  -- strict thread matches above, loose matches on Subject: below --
2001-07-20 10:23 Iain Sandoe
2001-07-20 12:17 ` Michael Schmitz
     [not found] <20010718230301.7A05C2F0F9@apollo.valhalla.net>
2001-07-18 23:22 ` Joseph P. Garcia
2001-07-18 22:36 Iain Sandoe
2001-07-18 20:10 2.4 - buttons, temperature, ictc Michael Schmitz
2001-07-18 21:11 ` Bastien Nocera
2001-07-18 21:54   ` powermac (other ppc?) events Joseph P. Garcia
2001-07-19 11:20     ` Michael Schmitz
2001-07-19 14:28       ` Joseph P. Garcia
2001-07-19 16:34         ` Michael Schmitz
2001-07-19 17:17           ` Joseph P. Garcia

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=20010719223636.DAB40DBB56@atlas.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=jpgarcia@execpc.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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;
as well as URLs for NNTP newsgroup(s).