Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Jul 2005 22:16:51 +0800
From:      Ariff Abdullah <skywizard@MyBSD.org.my>
To:        Alexander Leidinger <Alexander@Leidinger.net>
Cc:        freebsd-multimedia@freebsd.org, mat@cnd.mcgill.ca
Subject:   Re: Massive sound changes / fix (24/32bit pcm support, new sampling rate converter, various fixes)
Message-ID:  <20050713221651.10c6ca19.skywizard@MyBSD.org.my>
In-Reply-To: <20050713142157.99y2jio3dw0sc404@netchild.homeip.net>
References:  <20050707064603.6c295451.skywizard@MyBSD.org.my> <20050712204404.GA3835@trimind.de> <20050713061347.61f719c8.skywizard@MyBSD.org.my> <20050713142157.99y2jio3dw0sc404@netchild.homeip.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 Jul 2005 14:21:57 +0200
Alexander Leidinger <Alexander@Leidinger.net> wrote:
> Ariff Abdullah <skywizard@MyBSD.org.my> wrote:
> 
> > More good news is, I've already added sysctl controller to tune
> > vchan rate on the fly, something like sysctl
> > hw.snd.pcm0.vchanrate=xxx. Stay tuned.
> 
> While a sysctl is an easy solution, I don't think we should go this
> route. A sysctl is only settable by root, but such device specific
> sound tuning (or more abstract: user changeable parts) should be
> made user configurable, e.g. with a .ctl device in /dev and an ioctl
> interface (or maybe an extended ioctl interface for /dev/dsp*). A
> sndctl application (or the mixer application in case of switching to
> spdif output) can then change it without the need for superuser
> privileges.
>
I do agree with you, in fact, I have few ideas in mind to implement
something like user personal configs (yuck!, not my preferences). I
think we should go with sndctl, at the cost of adding few more ioctls
and perhaps incompatibilities. Talking about incompatibilities,
first, our mixer infrastructure need to be revamped. It's just too
old, too crude to handle modern soundcards. Pretty hard to tame it,
really, yet possible.

Currently all these sysctls and knobs are just to aid debugging,
something for developers to tinker with. I believe this will be
changed in near future.

Thanks for that suggestion.

> In case the user should be able to modify parts where he may cause a
> DoS (e.g. because a setting results in allocating memory depending
> on the value of the setting), a sysctl to limit the range of values
> makes sense (additionally to sanity checking of the values in the
> kernel).
> 
> Bye,
> Alexander.
> 


--

Ariff Abdullah
MyBSD

http://www.MyBSD.org.my (IPv6/IPv4)
http://staff.MyBSD.org.my (IPv6/IPv4)
http://tomoyo.MyBSD.org.my (IPv6/IPv4)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050713221651.10c6ca19.skywizard>