All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy White <jwhite@codeweavers.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: RFC:  Appropriate device detection for Wine  (more advice needed)
Date: Sun, 12 Jun 2005 21:43:11 -0500	[thread overview]
Message-ID: <42ACF2BF.5050603@codeweavers.com> (raw)
In-Reply-To: <42A5AE6A.2070204@codeweavers.com>

Okay,

So now I have a patch for Wine that very nicely
has Wine scanning for all cards and devices.  It
even probes for devices that behave badly
(e.g. my winmodem) and strips them out.

But I still have one device on my laptop;
card 0, device 4, that simply does not work
(see details below).

It seems to 'smell' right, but when data is
written to it, the buffer is never emptied.
Writing a sound file to it with aplay hangs
indefinitely; using pcm fills the sound buffer
and then blocks indefinitely.

So I'd like some advice:  Have I just been utterly
unrealistic in trying to scan for all PCM devices
on all cards?  Should I only report device 0 on each
card by default, and require the user to explicitly
request alternate devices?  Is there some way I can
detect that this device is psycho and automatically
strip it out?  What the heck is device 4 on my card?

Any/all advice appreciated.

Thanks,

Jeremy

p.s. Some details on sound card, let me know if more
is relevant:

releveant lspc -v snippet:


00000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
         Subsystem: Dell: Unknown device 011d
         Flags: bus master, medium devsel, latency 0, IRQ 7
         I/O ports at b800 [size=256]
         I/O ports at bc40 [size=64]
         Memory at f4fff800 (32-bit, non-prefetchable) [size=512]
         Memory at f4fff400 (32-bit, non-prefetchable) [size=256]
         Capabilities: [50] Power Management version 2


jertop:/proc/asound/card0/pcm4p# cat /proc/asound/card0/pcm4p/info
card: 0
device: 4
subdevice: 0
stream: PLAYBACK
id: Intel ICH - IEC958
name: Intel 82801DB-ICH4 - IEC958
subname: subdevice #0
class: 0
subclass: 0
subdevices_count: 1
subdevices_avail: 1



cat /proc/asound/devices
jertop:/# cat /proc/asound/devices
   0: [0- 0]: ctl
  20: [0- 4]: digital audio playback
  27: [0- 3]: digital audio capture
  26: [0- 2]: digital audio capture
  25: [0- 1]: digital audio capture
  16: [0- 0]: digital audio playback
  24: [0- 0]: digital audio capture
  33:       : timer
  32: [1- 0]: ctl
  48: [1- 0]: digital audio playback
  56: [1- 0]: digital audio capture


-------------------------------------------------------
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

  reply	other threads:[~2005-06-13  2:43 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         ` Jeremy White [this message]
2005-06-13  7:24           ` RFC: Appropriate device detection for Wine (more advice needed) Clemens Ladisch
2005-06-13 12:23             ` Jeremy White
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=42ACF2BF.5050603@codeweavers.com \
    --to=jwhite@codeweavers.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.