Milan Jurik wrote:
> Hi Garrett,
>
> V po, 01. 12. 2008 v 18:15, Garrett D'Amore píše:
>
>> Milan Jurik wrote:
>>
>>> Hi,
>>>
>>> is some way how to manage /dev/audio symlink? I have usb webcam (working
>>> in OSol) with audio profile (probably microphone) and as the result
>>> devfsadm symlink /dev/audio to usb/audio device. Which is wrong, of
>>> course. I need to stay with sound/0 (audio chip on board).
>>>
>>> For now I'm excluding usb audio driver, but that isnt' nice solution.
>>>
>>> I looked at devfsadm source code and it looks like usb audio (because
>>> loaded after audiohd) replaces symlink, no config option available. Is
>>> it truth?
>>>
>>>
>> Yes, that's correct.
>>
>> The idea was that a USB headset should trump the default built in device.
>>
>>
>
> It make sense in some cases, not so in my (with this webcam, it could be
> chalenge to add USB headset).
>
>
>> However, if you want your audio applications to always use /dev/sound/0
>> instead, you can put the following in your environment:
>>
>> AUDIODEV=/dev/sound/0
>> export AUDIODEV
>>
>>
>
> I saw this variable, but then it's unclear for me why mixerctl(1)
> manpage says that "If the AUDIODEV variable is not set, /dev/audioctl
> is used."
>
> So, /dev/audioctl vs. /dev/audio
>
If $AUDIODEV is set, then most Sun audio apps will append "ctl" when
they want to access the control device.
So you'll wind up using /dev/sound/0 and /dev/sound/0ctl
I'm going to take this issue under advisement for boomer -- perhaps this
issue (which is the primary device, or the desire to "lock in" a primary
device) is something we can make better in Boomer with a user tunable.
> Some tool to make "switch" can be nice :-)
>
Yeah, probably a new mixectl command in Boomer to do the "lock-in" I
alluded to above.
-- Garrett
> Best regards,
>
> Milan
>
> _______________________________________________
> driver-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss