From: Tobin Davis <tdavis@dsl-only.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Planned changes
Date: Fri, 16 May 2008 09:35:59 -0700 [thread overview]
Message-ID: <1210955759.6610.866.camel@razman> (raw)
In-Reply-To: <s5hej82e2of.wl%tiwai@suse.de>
On the debug side, I think it would be nicer if we could just compile
with all debugging available, then specify a debug=<level> option on
module load or through /sys writes (echo 3
>/sys/module/snd_hda-intel/parameters/debug). This way, each module can
be debugged independently without a lot of debug messages from other
modules.
As to the Kconfig option, switching to that would then require
users/developers to edit a kernel config file. Being able to select
which module to compile is far easier for people that only care about
one or two specific cards.
Just my $.02(USD) worth.
Tobin
On Fri, 2008-05-16 at 16:36 +0200, Takashi Iwai wrote:
> Hi,
>
> there are some patches floating around on my experimental tree, which
> I'd like to merge to the ALSA upstream. At least, the following two
> are ready for merge:
>
> - Use menuconfig in ALSA kconfig
> - Convert CONFIG_SND_DEBUG_DETECT to CONFIG_SND_DEBUG_VERBOSE
>
> The first one is to change from menu to menuconfig in ALSA Kconfig
> files. There have been some patches by others, but they haven't been
> applied because of the problem with alsa-driver build. Now I hacked
> alsa-driver build again so that it works with menuconfig somehow.
>
> The drawback is that it changes the configure option. Instead of
> --with-cards and --with-card-options, now we have a single
> --with-kconfigs. I think, however, it's rather an improvement.
>
> The next one, renaming to CONFIG_SND_DEBUG_VERBOSE, is easy.
> The reason is that CONFIG_SND_DEBUG_DETECT and snd_printdd() are used
> almostly exclusively for verbose debug messages. This may reduce some
> misunderstanding about this option.
>
> The patches can be found on my experimental tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver-build-unstable.git
>
> If there is no objection, I'll apply the above two changes in the next
> week.
>
>
> thanks,
>
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Tobin Davis
"You've got to have a gimmick if your band sucks."
-- Gary Giddens
next prev parent reply other threads:[~2008-05-16 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 14:36 Planned changes Takashi Iwai
2008-05-16 16:35 ` Tobin Davis [this message]
2008-05-16 16:46 ` Takashi Iwai
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=1210955759.6610.866.camel@razman \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.