From: Christoph Hellwig <hch@caldera.de>
To: Martin Laberge <mlsoft@videotron.ca>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.0 - sndstat not present
Date: Mon, 8 Jan 2001 16:45:37 +0100 [thread overview]
Message-ID: <20010108164536.A4257@caldera.de> (raw)
In-Reply-To: <200101081518.QAA01381@ns.caldera.de> <3A59DD1F.E1CB0B0F@videotron.ca>
In-Reply-To: <3A59DD1F.E1CB0B0F@videotron.ca>; from mlsoft@videotron.ca on Mon, Jan 08, 2001 at 10:30:39AM -0500
On Mon, Jan 08, 2001 at 10:30:39AM -0500, Martin Laberge wrote:
> the reference to sndstat and /proc/sound was found in
>
> drivers/sound/soundcard.c
IIRC it is only in the changelogs - and I don't want to play Big Brother on
source files ...
> thanks for your lights on this topic...
>
> is there nothing i can use anymore to check existence of sound drivers
> in kernel...
Nothing sound specific, no.
>
> these informations were very valuables when i was configuring my cards
> for the first time... sometimes the driver loaded but do not appeared in
> sndstat
> then i was able to change my configuration according to what i see in
> sndstat...
The problem is that the PCI drivers don't support this feature anymore.
Not sure wether ALSA, which will bring a unified (in-kernel) sound-API
again has such a feature.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-08 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 14:23 2.4.0 - sndstat not present Martin Laberge
2001-01-08 15:18 ` Christoph Hellwig
2001-01-08 15:30 ` Martin Laberge
2001-01-08 15:45 ` Christoph Hellwig [this message]
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=20010108164536.A4257@caldera.de \
--to=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mlsoft@videotron.ca \
/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