From: Jeremy White <jwhite@codeweavers.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: RFC: Appropriate device detection for Wine (more advice needed)
Date: Mon, 13 Jun 2005 07:23:56 -0500 [thread overview]
Message-ID: <42AD7ADC.8090102@codeweavers.com> (raw)
In-Reply-To: <Pine.HPX.4.33n.0506130919470.20036-100000@studcom.urz.uni-halle.de>
> This is the SPDIF output.
>
> I don't know what the problem is, especially if the PCM output _does_
> work. Does your machine actually have an SPDIF output?
No, I don't believe it does; it's a Dell Latitude D600 notebook.
>
>
>>So I'd like some advice: Have I just been utterly
>>unrealistic in trying to scan for all PCM devices
>>on all cards?
>
>
> No, you cannot do more. The user has to decide which device to use.
Yah. I'm feeling a bit stuck; the Wine regression tests require
that all discovered devices pass a very basic set of tests.
So I've made a change that I think is a Good Thing (TM),
but it doesn't pass the regression tests...
>
>
>>Is there some way I can detect that this device is psycho and
>>automatically strip it out?
>
>
> There are many reason why a device could be temporarily unavailable,
> so Wine shouldn't try to be too intelligent. :-)
Good point :-/.
Thanks,
Jeremy
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
next prev parent reply other threads:[~2005-06-13 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 3:52 RFC: Appropriate device detection for Wine Jeremy White
2005-06-07 7:32 ` Jaroslav Kysela
2005-06-07 12:27 ` Jeremy White
2005-06-07 12:48 ` Jaroslav Kysela
2005-06-07 14:25 ` Jeremy White
2005-06-13 2:43 ` RFC: Appropriate device detection for Wine (more advice needed) Jeremy White
2005-06-13 7:24 ` Clemens Ladisch
2005-06-13 12:23 ` Jeremy White [this message]
2005-06-13 12:35 ` Takashi Iwai
2005-06-13 14:00 ` Jeremy White
2005-06-13 14:23 ` Takashi Iwai
2005-06-13 15:01 ` Jeremy White
2005-06-13 15:11 ` Takashi Iwai
2005-06-14 3:22 ` Jeremy White
2005-06-14 8:30 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42AD7ADC.8090102@codeweavers.com \
--to=jwhite@codeweavers.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.