From: "Udo A. Steinberg" <reality@delusion.de>
To: rui.p.m.sousa@clix.pt
Cc: Gerd Knorr <kraxel@bytesex.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: BT878 audio dma
Date: Wed, 15 Aug 2001 14:09:16 +0200 [thread overview]
Message-ID: <3B7A666C.567260F3@delusion.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0108151358390.9296-100000@sophia-sousar2.nice.mindspeed.com>
rui.p.m.sousa@clix.pt wrote:
>
> On Wed, 15 Aug 2001, Udo A. Steinberg wrote:
>
> The bt878 must be grabing an audio device. If so, and when the bt878
> module is loaded first, thememu10k1 should be using /dev/dsp1 (and
> /dev/dsp2).
>
> When you compile the bt878 as a module and _loaded it after_ the
> emu10k1 module does it still work (proving my point above)?
Yes, then it still works. Is there an easy way to tell which driver
uses which dsp device?
Regards,
Udo.
next prev parent reply other threads:[~2001-08-15 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 11:41 BT878 audio dma Udo A. Steinberg
2001-08-15 12:02 ` rui.p.m.sousa
2001-08-15 12:09 ` Udo A. Steinberg [this message]
2001-08-15 12:02 ` Gerd Knorr
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=3B7A666C.567260F3@delusion.de \
--to=reality@delusion.de \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.p.m.sousa@clix.pt \
/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