|
From: Henrique de M. H. <hm...@hm...> - 2007-03-08 00:38:17
|
On Wed, 07 Mar 2007, Tobin Davis wrote: > Another question comes to mind. Why would the volume need to be > controlled if there is no sound driver to generate sound? I'm trying > to understand the usage model here for that aspect. Because the firmware will happly beep away, and you may want to control the volume of those beeps. And it also controls the volume of the PC buzzer (the BIOS makes sure whatever sound hardware is in the machine lets that one through by default). > As to the firmware controlling the sound mixer when drivers are loaded, > what about creating an unsolicited event situation that is specifically > masked to each control? That would be an easy addition to the hda codec > drivers (not sure about AC'97). I can deal with that just fine, but I'd still need to somehow tell all codecs (not just hda, ac97 -- let's make this generic) that I am providing such an interface, and that I want an extra (monoaural in the case of thinkpads, others might want stereo) global (volume/tone/whatever) mixer control, that can produce such events. And the interface needs to be bidirectional, so that I can update the control. And I need to be able to pinpoint which card should add this interface, so that I can track down the correct embedded card (using model-specific knowledge) and, e.g., exclude USB and CardBus sound cards... that means I need to somehow access for every card in the system what bus and busID it is hanging off. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh |
