280 The card_number field is the number of the aggregate
281 audio device this mixer is located on. It can be used
282 with the SNDCTL_CARDINFO ioctl.
283
284 The nrext field is the number of mixer extensions
285 available on this mixer. See the SNDCTL_MIX_NREXT
286 description.
287
288 The priority is used by the framework to assign a
289 preference that applications can use in choosing a
290 device. Higher values are preferable. Mixers with
291 priorities less than -1 should never be selected by
292 default.
293
294 The devnode field contains the actual full path to the
295 device node for the physical mixer, such as
296 /dev/sound/audio810:0mixer. Applications should open
297 this file to access the mixer settings.
298
299 Mixer Extension IOCTLs
300 The pseudo /dev/mixer device supports ioctls that can change the oarious
301 settings for the audio hardware in the system.
302
303 Those ioctls should only be used by dedicated mixer applications or
304 desktop olumme controls, and not by typical ordinary audio applications
305 such as media players. Ordinary applications that wish to adjust their
306 own volume settings should use the SNDCTL_DSP_SETPLAYVOL or
307 SNDCTL_DSP_SETRECVOL ioctls for that purpose. See dsp(7I) for more
308 information. Ordinary applications should never attempt to change master
309 port selection or hardware settings such as monitor gain settings.
310
311 The ioctls in this section can only be used to access the mixer device
312 that is associated with the current file descriptor.
313
314 Applications should not assume that a single /dev/mixer node is able to
315 access any physical settings. Instead, they should use the ioctl
316 SNDCTL_MIXERINFO to determine the device path for the real mixer device,
317 and issue ioctls on a file descriptor opened against the corresponding
318 devnode field.
319
320 When a dev member is specified in each of the following ioctls, the
321 application should specify -1, although for compatibility the mixer
322 allows the application to specify the mixer device number.
323
324 SNDCTL_MIX_NRMIX The argument is a pointer to an integer, which
530
531 EINVAL The parameter changes requested in the ioctl are invalid or are
532 not supported by the device.
533
534 ENXIO The device or extension referenced does not exist.
535
536 ARCHITECTURE
537 SPARC x86
538
539 INTERFACE STABILITY
540 The information and mixer extension IOCTLs are Uncommitted. The
541 Compatibility IOCTLs are Obsolete Uncommitted. The extension names are
542 Uncommitted.
543
544 SEE ALSO
545 close(2), ioctl(2), open(2), read(2), attributes(5), dsp(7I)
546
547 BUGS
548 The names of mixer extensions are not guaranteed to be predictable.
549
550 illumos February 1, 2019 illumos
|
280 The card_number field is the number of the aggregate
281 audio device this mixer is located on. It can be used
282 with the SNDCTL_CARDINFO ioctl.
283
284 The nrext field is the number of mixer extensions
285 available on this mixer. See the SNDCTL_MIX_NREXT
286 description.
287
288 The priority is used by the framework to assign a
289 preference that applications can use in choosing a
290 device. Higher values are preferable. Mixers with
291 priorities less than -1 should never be selected by
292 default.
293
294 The devnode field contains the actual full path to the
295 device node for the physical mixer, such as
296 /dev/sound/audio810:0mixer. Applications should open
297 this file to access the mixer settings.
298
299 Mixer Extension IOCTLs
300 The pseudo /dev/mixer device supports ioctls that can change the various
301 settings for the audio hardware in the system.
302
303 Those ioctls should only be used by dedicated mixer applications or
304 desktop volume controls, and not by typical ordinary audio applications
305 such as media players. Ordinary applications that wish to adjust their
306 own volume settings should use the SNDCTL_DSP_SETPLAYVOL or
307 SNDCTL_DSP_SETRECVOL ioctls for that purpose. See dsp(7I) for more
308 information. Ordinary applications should never attempt to change master
309 port selection or hardware settings such as monitor gain settings.
310
311 The ioctls in this section can only be used to access the mixer device
312 that is associated with the current file descriptor.
313
314 Applications should not assume that a single /dev/mixer node is able to
315 access any physical settings. Instead, they should use the ioctl
316 SNDCTL_MIXERINFO to determine the device path for the real mixer device,
317 and issue ioctls on a file descriptor opened against the corresponding
318 devnode field.
319
320 When a dev member is specified in each of the following ioctls, the
321 application should specify -1, although for compatibility the mixer
322 allows the application to specify the mixer device number.
323
324 SNDCTL_MIX_NRMIX The argument is a pointer to an integer, which
530
531 EINVAL The parameter changes requested in the ioctl are invalid or are
532 not supported by the device.
533
534 ENXIO The device or extension referenced does not exist.
535
536 ARCHITECTURE
537 SPARC x86
538
539 INTERFACE STABILITY
540 The information and mixer extension IOCTLs are Uncommitted. The
541 Compatibility IOCTLs are Obsolete Uncommitted. The extension names are
542 Uncommitted.
543
544 SEE ALSO
545 close(2), ioctl(2), open(2), read(2), attributes(5), dsp(7I)
546
547 BUGS
548 The names of mixer extensions are not guaranteed to be predictable.
549
550 illumos February 17, 2020 illumos
|