Date: Mon, 30 May 2005 12:22:02 +0900 From: Pyun YongHyeon <yongari@rndsoft.co.kr> To: Panagiotis Astithas <past@ebs.gr> Cc: freebsd-multimedia@freebsd.org Subject: Re: maestro3 hardware volume control Message-ID: <20050530032202.GC892@rndsoft.co.kr> In-Reply-To: <4298F0AB.2090404@ebs.gr> References: <4298F0AB.2090404@ebs.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 29, 2005 at 01:28:59AM +0300, Panagiotis Astithas wrote: > Weird, on my HP Omnibook XE3, the on-board maestro3 has been working > flawlessly all along without any entry in /boot/device.hints. If I add: > hint.pcm.0.hwvol_config="0" > then the hardware volume controls on the laptop stop functioning. > Setting it to "1" makes it working again. > Hmm, I didn't know that due to a comment in the driver and failure on my laptops. > Does that mean that GPIO pin 4,5 was selected as the default by some > other means on my system? Could ACPI be doing it? > > I guess your system use GD pins to control hardware volume. Stock maestro3 driver uses hint.pcm.0.hwvol_config="0" : select GPIO pin hint.pcm.0.hwvol_config="1" : select GD pin (This is reverse of my previous posting, sorry, I'm confused.) If there is no hint then it will use GD pin. Having a quirk table for sytems would be better solution. But it's hard to build a complete table for this. Since there is a system that works with current driver's behavior it would be useless to change default to use GD pin. I can live with the hint mechanism. However the drawback is the hint mechanism works only at boot time for staticlly linked driver, so it's not apply to dynamically loaded driver. :-( -- Regards, Pyun YongHyeon http://www.kr.freebsd.org/~yongari | yongari@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050530032202.GC892>