From: Karel Kulhavy <clock@twibright.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ALSA make menuconfig Help description missing
Date: Tue, 17 May 2005 16:59:31 +0200 [thread overview]
Message-ID: <20050517145931.GA11564@kestrel> (raw)
In-Reply-To: <s5hfywmotdd.wl@alsa2.suse.de>
On Tue, May 17, 2005 at 03:49:02PM +0200, Takashi Iwai wrote:
> At Tue, 17 May 2005 14:35:49 +0200,
> Karel Kulhavy wrote:
> >
> > Hello
> >
> > v2.6.11 make menuconfig -> Device Drivers -> Sound -> Advanced Linux
> > Sound Architecture and
> >
> > v2.6.11 make menuconfig -> Device Drivers -> Sound -> Advanced Linux
> > Sound Architecture -> Advanced Linux Sound Architecture
> >
> > are missing their help descriptions:
> >
> > "There is no help available for this kernel option."
> >
> > Therefore the user is unable to determine how to use this subsystem
> > at all.
>
> Something like below fixes the problem?
Yes, tried, fixes ;-)
However I suggest that a pointer to user documentation for ALSA be added
to the Help.
For example I have a problem when I run XMMS, Skype says something like
"can't open /dev/dsp" and don't know where to start. The only thing I
know is that 1) I have ALSA turned on and 2) I want to know how to make
it accept more data streams from the programs and mix them together.
CL<
>
>
> Takashi
>
>
> --- linux/sound/Kconfig 22 Mar 2005 10:44:59 -0000 1.9
> +++ linux/sound/Kconfig 17 May 2005 13:47:08 -0000
> @@ -42,6 +42,8 @@
> config SND
> tristate "Advanced Linux Sound Architecture"
> depends on SOUND
> + help
> + Say 'Y' or 'M' to enable ALSA (Advanced Linux Sound Architecture)
>
> source "sound/core/Kconfig"
>
next prev parent reply other threads:[~2005-05-17 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 12:35 Karel Kulhavy
2005-05-17 13:49 ` Takashi Iwai
2005-05-17 14:16 ` Alexey Dobriyan
2005-05-17 14:32 ` Takashi Iwai
2005-05-17 14:59 ` Karel Kulhavy [this message]
2005-05-17 19:30 ` Lee Revell
2005-05-17 20:35 ` Valdis.Kletnieks
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=20050517145931.GA11564@kestrel \
--to=clock@twibright.com \
--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
all inboxes | Powered by JetHome®