snd_uaudio.4 (204605) | snd_uaudio.4 (219004) |
---|---|
1.\" $NetBSD: uaudio.4,v 1.15 2002/02/12 19:53:57 jdolecek Exp $ 2.\" 3.\" Copyright (c) 1999 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Lennart Augustsson. 8.\" --- 13 unchanged lines hidden (view full) --- 22.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 23.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 24.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 25.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 26.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 27.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 28.\" POSSIBILITY OF SUCH DAMAGE. 29.\" | 1.\" $NetBSD: uaudio.4,v 1.15 2002/02/12 19:53:57 jdolecek Exp $ 2.\" 3.\" Copyright (c) 1999 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Lennart Augustsson. 8.\" --- 13 unchanged lines hidden (view full) --- 22.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 23.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 24.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 25.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 26.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 27.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 28.\" POSSIBILITY OF SUCH DAMAGE. 29.\" |
30.\" $FreeBSD: head/share/man/man4/snd_uaudio.4 204605 2010-03-02 21:59:03Z joel $ | 30.\" $FreeBSD: head/share/man/man4/snd_uaudio.4 219004 2011-02-24 18:08:23Z hselasky $ |
31.\" | 31.\" |
32.Dd December 15, 2005 | 32.Dd February 24, 2011 |
33.Dt SND_UAUDIO 4 34.Os 35.Sh NAME 36.Nm snd_uaudio | 33.Dt SND_UAUDIO 4 34.Os 35.Sh NAME 36.Nm snd_uaudio |
37.Nd USB audio device driver | 37.Nd USB audio and MIDI device driver |
38.Sh SYNOPSIS 39To compile this driver into the kernel, place the following lines in your 40kernel configuration file: 41.Bd -ragged -offset indent 42.Cd "device sound" 43.Cd "device usb" 44.Cd "device snd_uaudio" 45.Ed --- 4 unchanged lines hidden (view full) --- 50.Bd -literal -offset indent 51snd_uaudio_load="YES" 52.Ed 53.Sh DESCRIPTION 54The 55.Nm 56driver provides support for 57.Tn USB | 38.Sh SYNOPSIS 39To compile this driver into the kernel, place the following lines in your 40kernel configuration file: 41.Bd -ragged -offset indent 42.Cd "device sound" 43.Cd "device usb" 44.Cd "device snd_uaudio" 45.Ed --- 4 unchanged lines hidden (view full) --- 50.Bd -literal -offset indent 51snd_uaudio_load="YES" 52.Ed 53.Sh DESCRIPTION 54The 55.Nm 56driver provides support for 57.Tn USB |
58audio class devices. | 58audio class devices and 59.Tn USB 60MIDI class devices. |
59.Pp 60A 61.Tn USB 62audio device consists of a number of components: 63input terminals (e.g.\& USB digital input), output terminals (e.g.\& 64speakers), and a number of units in between (e.g.\& volume control). 65.Pp 66Refer to the --- 22 unchanged lines hidden (view full) --- 89The 90.Tn PCM 91framework in 92.Fx , 93as of this writing, does not handle device un-registrations in a properly 94abstracted manner, i.e., a detach request is refused by the 95.Tn PCM 96framework if the device is in use. | 61.Pp 62A 63.Tn USB 64audio device consists of a number of components: 65input terminals (e.g.\& USB digital input), output terminals (e.g.\& 66speakers), and a number of units in between (e.g.\& volume control). 67.Pp 68Refer to the --- 22 unchanged lines hidden (view full) --- 91The 92.Tn PCM 93framework in 94.Fx , 95as of this writing, does not handle device un-registrations in a properly 96abstracted manner, i.e., a detach request is refused by the 97.Tn PCM 98framework if the device is in use. |
97For 98.Tn USB 99and supposedly other detach-able busses, it is necessary to allow the 100device un-registration to complete successfully, otherwise the driver 101leaves wild pointers to invalid data structures and thus leading to a panic. | 99It is necessary to allow the device un-registration to complete 100successfully, otherwise the 101.Tn PCM 102layer will panic. |