All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa problems
Date: Tue, 28 Mar 2006 15:11:46 +0200	[thread overview]
Message-ID: <1143551506.13615.48.camel@localhost> (raw)
In-Reply-To: <s5hu09i7m3k.wl%tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 795 bytes --]

On Tue, 2006-03-28 at 15:08 +0200, Takashi Iwai wrote:

> > 1)
> > #include <sound/core.h>
> > doesn't compile because it requires sound/driver.h *before* it.
> 
> Yes.  And what's the point?

Well, that's pretty dumb. If it requires sound/driver.h it could just as
well include it itself.

> I don't understand what's the problem.  You can create an empty PCM
> via snd_pcm_new(), then add each stream, playback or capture, can be
> assigned appropriately via snd_pcm_new_stream() later on.

Right.
snd_pcm_new()
snd_device_register(card, pcm)
snd_pcm_new_stream(...)   <--- this stream never shows up as a chardev!!

> It can.  Call snd_device_free().

Hah ok. I didn't realize pcms were really just device thingies since
they have so many extra functions.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]

  reply	other threads:[~2006-03-28 13:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 12:10 alsa problems Johannes Berg
2006-03-28 13:08 ` Takashi Iwai
2006-03-28 13:11   ` Johannes Berg [this message]
2006-03-28 13:16     ` Takashi Iwai
2006-03-28 13:21       ` Johannes Berg
2006-03-28 13:36         ` Takashi Iwai
2006-03-28 13:44           ` Johannes Berg
2006-03-28 14:06             ` Takashi Iwai
2006-03-28 14:10               ` Johannes Berg
2006-03-28 14:21                 ` Takashi Iwai
2006-03-28 15:33                   ` Johannes Berg

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=1143551506.13615.48.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=alsa-devel@alsa-project.org \
    --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.