From: Fred Gleason <fredg@wava.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Re: How to support multiple open in low-level driver
Date: Mon, 6 Jan 2003 09:09:04 -0500 [thread overview]
Message-ID: <200301060909.04979.fredg@wava.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301051600200.500-100000@pnote.perex-int.cz>
On Sunday 05 January 2003 10:05, Jaroslav Kysela wrote:
> Well, you're talking about PCM devices (subdevices are one level after
> devices):
>
> cards -> pcm devices -> pcm subdevices
What are the differences between a "device" and a "subdevice" in general? Is
this indicative of some underlying hardware architecture, or is it a purely
logical/virtual artifact?
Cheers!
|-------------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Salem Radio Labs |
| Voice: 1-(540)-341-2880 | 87 Lee Highway, Suite 11 |
| FAX: 1-(540)-341-7176 | Warrenton, VA 20188 |
|-------------------------------------------------------------------------|
| The real problem with hunting elephants is carrying the decoys. |
| -- Anonymous |
|-------------------------------------------------------------------------|
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-01-06 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 22:37 How to support multiple open in low-level driver Anders Torger
2003-01-05 14:34 ` Jaroslav Kysela
2003-01-05 14:48 ` Anders Torger
2003-01-05 15:05 ` Jaroslav Kysela
2003-01-06 14:09 ` Fred Gleason [this message]
2003-01-06 14:26 ` Jaroslav Kysela
2003-01-06 15:52 ` Patrick Shirkey
2003-01-06 16:25 ` Paul Davis
2003-01-06 17:30 ` Jaroslav Kysela
2003-01-06 13:57 ` Justin Cormack
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=200301060909.04979.fredg@wava.com \
--to=fredg@wava.com \
--cc=alsa-devel@alsa-project.org \
/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.