[alsa-devel] CONFIG_SND_DEBUG (was: Re: [PATCH] ALSA: get rid of CONFIG_SND_VERBOSE_PRINTK)
tiwai at suse.de
Wed Jun 5 10:46:39 CEST 2013
At Wed, 05 Jun 2013 09:47:30 +0200,
David Henningsson wrote:
> On 06/05/2013 09:34 AM, Joe Perches wrote:
> > On Wed, 2013-06-05 at 09:22 +0200, Takashi Iwai wrote:
> >> At Wed, 05 Jun 2013 00:07:57 -0700, Joe Perches wrote:
> >>> On Wed, 2013-06-05 at 08:54 +0200, Takashi Iwai wrote:
> >>>> At Tue, 04 Jun 2013 23:52:01 -0700, Joe Perches wrote:
> >>>>> On Wed, 2013-06-05 at 08:32 +0200, Takashi Iwai wrote:
> >>>>>> Yes. These are snd_printd() just to be conditionally built in.
> >>>>>> But in most cases it's rather useful to print them (as most distros
> >>>>>> set CONFIG_SND_DEBUG=y).
> >>>>> Ubuntu doesn't, I believe Fedora doesn't.
> >>>> Then they should have done so :)
> >>> But they don't, so what distros do?
> >> RedHat (including Fedora) and SUSE do at least.
> > Mandriva does too. (still looking around for others)
> > We can ask Ubuntu to enable CONFIG_SND_DEBUG.
> > (cc'd Andy Whitcroft, Leann Ogasawara and David Henningsson)
> > Maybe there are others Canonical folk that
> > should be cc'd?
> Adding kernel team mailing list to CC.
> Andy/Leann - apparently CONFIG_SND_DEBUG is on by default from upstream,
> and we explicitly disable it. Is there any reason why we do that?
Inheriting from Debian?
Note that CONFIG_SND_DEBUG=n is correct if you are really sure that
the driver works fine on your device and you want to keep the kernel
as minimal as possible. For generic kernels, better to set this
option because it also enables more safety checks.
More information about the Alsa-devel