On Thursday 29 January 2009, TL Mieszkowski wrote:
Al Johnson wrote:
On Wednesday 28 January 2009, TL Mieszkowski wrote:
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be
convenient
TL Mieszkowski wrote:
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be convenient
to
pause media player to avoid bothering your neighboors. My other phone
behaves like that
I can see how having the sound info in a stack might be
useful (marginally, really), but I can't see it justifying
the use of D-bus. I wouldn't say never, but I really can't
think of any pressing reasons to want to know when the state
changes.
First example on top of my head : you
and respectful for the other
people.
I'm nobody, but that is so contrived it comes no where near convincing me
that such a non-UNIXy system is the right way.
--
View this message in context:
http://n2.nabble.com/Alsa-state-chooser-tp224p2235224.html
Sent from the Openmoko Community mailing list
On Wednesday 28 January 2009, TL Mieszkowski wrote:
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be convenient
to
pause media player to avoid bothering your neighboors. My other phone
are the simple ways to do it.
Or the alternative, reinvent UNIX poorly
with unnecessarily complex abstractions.
--
View this message in context:
http://n2.nabble.com/Alsa-state-chooser-tp224p2236253.html
Sent from the Openmoko Community mailing list archive at Nabble.com
it's
a
real world example.
Actually, who cares if it's contrived or not? I thought that was what
/dev/input/eventX was for.
--
View this message in context:
http://n2.nabble.com/Alsa-state-chooser-tp224p2236352.html
Sent from the Openmoko Community mailing list archive at Nabble.com
On Tuesday 27 January 2009, TL Mieszkowski wrote:
I'm not sure what the status of the Dbus sound stuff is, but I wrote a
little program to choose the alsa state file with a simple gui. Attached is
the code in anyone is interested. All it is is 1 button for each state
file, very simplistic,
in the Wolfson Codec manual that it is possible, by
monitoring voltages or some such, I imagine that would have to be done in
the alsa plugin or maybe in the driver though.
--
View this message in context:
http://n2.nabble.com/Alsa-state-chooser-tp224p2228688.html
Sent from the Openmoko Community
enabled
Table 15 Mic Bias Current Comparator Circuit Control
--
View this message in context:
http://n2.nabble.com/Alsa-state-chooser-tp224p2229301.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
___
Openmoko community
On Wednesday 28 January 2009, TL Mieszkowski wrote:
WM8753.pdf pg 27:
MICBIAS CURRENT DETECT
The WM8753L includes a microphone bias current detect circuit which allows
the user to set
thresholds for the microphone bias current, above which an interrupt will
be triggered.
I think this
Al Johnson wrote:
I think this appears as /dev/input/eventX and should be available in
FSO's
rules.yaml if it isn't available as a direct notification.
Cool, thanks Al
--
View this message in context:
http://n2.nabble.com/Alsa-state-chooser-tp224p2229815.html
Sent from
would run it like so:
scalpel `ls -1 /usr/share/openmoko/scenarios/`
meh, whatever, works for me
-Tim
http://n2.nabble.com/file/n224/scalpel.c scalpel.c
--
View this message in context:
http://n2.nabble.com/Alsa-state-chooser-tp224p224.html
Sent from the Openmoko Community mailing list
13 matches
Mail list logo