All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Sound userspace drivers (fishing for insight)
Date: Wed, 08 Mar 2006 13:56:06 -0500	[thread overview]
Message-ID: <440F28C6.6050508@comcast.net> (raw)
In-Reply-To: <s5h8xrkepxy.wl%tiwai@suse.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Takashi Iwai wrote:
> At Wed, 08 Mar 2006 11:17:26 -0500,
> John Richard Moser wrote:
>>>> into the kernel; with alsa it's written to a /proc interface, which
>>> Using /proc? Where? I've not noticed it :-)
>> I thought that was what /proc/asound/card0/ was for?  :)
> 
> /proc is not referred from alsa-lib, i.e. programs don't access them.
> It's just for users who want to read some information.
> 

This makes me wonder then how stuff is set up.  There's no device, is
there a sound card syscall now?

> 
> Takashi
> 

- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

    Creative brains are a valuable, limited resource. They shouldn't be
    wasted on re-inventing the wheel when there are so many fascinating
    new problems waiting out there.
                                                 -- Eric Steven Raymond

    We will enslave their women, eat their children and rape their
    cattle!
                                     -- Evil alien overlord from Blasto
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBRA8oxQs1xW0HCTEFAQKGuA//RX/shtqKKPYQwSdP8O+Ai5C7VnQV+GiN
I/+OalJIjfK/zUiJP6CIsFcNxTFTPiUJOwF/MKguiwWHsMwr/CWu/MVqAQEDC/yP
UO1hSLcGKTp8xHh5jSIyotjisXaGx8rSq0Ye8ZDGPgDlVXb27USkmqWwySBCO+OJ
pFtzGy9GxuJ+1OWoiXd0ytTSVm6WPEX/zFNsQmY4AnFid5aTrlxjDjQpx2cxt4iq
j1nc+kkt450m4y233Cuncb7UXI/WzVhUX89dJf4RkjMKs5QDBvtQhzTB4K3PPByg
l13xQq8si/knA8jcYcEbtHrzh+bTlvSwa8hJfONG3tbShHedJNQA+kLm6zpwm/kw
hGkW0/IYU/Kpxh6Hg8yqb67ibbLFKjNc0njwRTZ5CLkE4pUwT/NASY4j5IcXYMrp
bOla+ASuy/g0dYngmh0wK4tqJJSfl+SdZt+AkeVm6x5XtYv2k2uEhfQsDWpqhp0z
TXiauuLhdJZ3mle21ZcY634Ws9C2vLmH6/TBQAgb0azryo9W4FQvEfPszbPyln04
irNC/VkKQ9vDr3spjXlqW9hCCD176+uOoHsI79WnUiz1EUdQ02kZ4mLm/i4JuXS8
Y8rezaHx7iypylVlI7c5CaDuEnrsBfvX7i/FqUa3/E0yH0v2wU0EcmC2K1OF1d7M
q0jA3aTHj+o=
=wEi9
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-03-08 18:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08  4:02 Sound userspace drivers (fishing for insight) John Richard Moser
2006-03-08  8:44 ` Jaroslav Kysela
2006-03-08 16:17   ` John Richard Moser
2006-03-08 18:44     ` Takashi Iwai
2006-03-08 18:56       ` John Richard Moser [this message]
2006-03-08 19:08         ` Takashi Iwai
2006-03-08 20:10           ` John Richard Moser

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=440F28C6.6050508@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=tiwai@suse.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.