linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [Alsa-devel] [2.6.0-test9 ALSA] ALSA-OSS-emulation unable to register
Date: Mon, 3 Nov 2003 21:06:06 +0100	[thread overview]
Message-ID: <200311032106.28125.mbuesch@freenet.de> (raw)
In-Reply-To: <s5hu15ltgb5.wl@alsa2.suse.de>

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

On Monday 03 November 2003 20:14, you wrote:
> > CONFIG_SOUND_BT878=y
>
>   ^^^^^^^^^^^^^^^^^^^^
> this conflicts with ALSA.  try to pass the index parameter via boot
> option of snd-ens1371.

Thanks for your suggestion, but it doesn't work.
Still displays
ALSA sound/core/oss/pcm_oss.c:2353: unable to register OSS PCM device 0:0
Is there some other way to make bttv-audio and
ALSA-ens1371 working both? Would be cool if I
could use both at the same time. :)

> it's already fixed on the ALSA cvs version.

ok.

> ciao,
>
> --
> Takashi Iwai <tiwai@suse.de>		ALSA Developer - www.alsa-project.org

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/prVDoxoigfggmSgRAm/zAJ9nwkcRvzM2/w2EgYpbSZL0sZxoegCfYDBu
Oq5ZWs+LPXRF0iw3MfyKySI=
=Fg8x
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-11-03 20:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-02 14:01 [2.6.0-test9 ALSA] ALSA-OSS-emulation unable to register Michael Buesch
2003-11-03 19:14 ` [Alsa-devel] " Takashi Iwai
2003-11-03 20:06   ` Michael Buesch [this message]
2003-11-04 15:01     ` Takashi Iwai
2003-11-04 15:30       ` Michael Buesch
2003-11-04 15:36         ` Takashi Iwai
2003-11-04 20:35           ` Michael Buesch
2003-11-05 10:50             ` Takashi Iwai
2003-11-05 12:32               ` Michael Buesch

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=200311032106.28125.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).