Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Günther Montag" <Safari.Doktor@addcom.de>
Cc: "alsa-devel@lists.sourceforge.net"
	<alsa-devel@lists.sourceforge.net>,
	hfterm-hackers@lists.sourceforge.net
Subject: Re: env LD_PRELOAD=/usr/lib/libaoss.so ....
Date: Thu, 16 Oct 2003 15:10:06 +0200	[thread overview]
Message-ID: <s5hu169gwgh.wl@alsa2.suse.de> (raw)
In-Reply-To: <200310161413.28379.Safari.Doktor@addcom.de>

At Thu, 16 Oct 2003 14:13:28 +0200,
G╴nther Montag wrote:
> 
> hello friends
> when I start my ham program with this preload
> it says
> ***
> hfkernel_user will be started by /usr/local/bin/hfkernel start
> hfkernel[235]: hfkernel 0.4.1 starting...
> ALSA lib pcm.c:1809:(snd_pcm_open_noupdate) Unknown PCM dsp0
> hfkernel[235]: error: open: No such file or directory
> ***
> although I called the soundcard right with /dev/dsp0,
> the device is there (cat file > /dev/dsp0 gives a sound),
> the same with /dev/adsp
> somewhere (where?) on the way it seems to eat the /dev!

when you use OSS-wrapper library, the access to /dev/dsp* or
/dev/adsp* will be coverted to the ALSA API.  that is, these files are
never accessed in practice.

the message above shows that you don't have the definition of dsp0 in
~/.asoundrc.  simply add

	pcm.dsp0 pcm.default

to ~/.asoundrc.

btw, it won't be a problem on cvs version, i fixed yesterday use the
default pcm as fallback.

> 
> Another question:
> I looked into the file alsa-lib-0.9.7/src/pcm/pcm.c, where this#
> function snd_pcm_open_noupdate is,
> thanjs Jaroslav for the very interesting documentation,
> You made my day,
> but if You have time tell me: it looks like html,
> how  can I read it as html?

you can generate the document via doxygen.
the already formatted html is found at
	http://www.alsa-project.org/alsa-doc/alsa-lib


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

  reply	other threads:[~2003-10-16 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16 12:13 env LD_PRELOAD=/usr/lib/libaoss.so Günther Montag
2003-10-16 13:10 ` Takashi Iwai [this message]
2003-10-16 15:56   ` Dr. med. Günther Montag
2003-10-16 16:51     ` Takashi Iwai
2003-10-21 11:56       ` [Hfterm-hackers] " Günther Montag

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=s5hu169gwgh.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=Safari.Doktor@addcom.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=hfterm-hackers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox