[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0705292212120.11140@yvahk01.tjqt.qr>
Date: Tue, 29 May 2007 22:18:05 +0200 (MEST)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Takashi Iwai <tiwai@...e.de>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Uwe Bugla <uwe.bugla@....de>, linux-kernel@...r.kernel.org,
Jaroslav Kysela <perex@...e.cz>,
Mauro Carvalho Chehab <mchehab@...radead.org>
Subject: Re: BUG in 2.6.22-rc2-mm1: Parts of Alsa sound architecture broken
On May 29 2007 18:41, Takashi Iwai wrote:
>
>Well, I find the change of CONFIG_SND to menuconfig is fine, too.
>But CONFIG_SND_PCI_DRIVERS and others don't make much sense to me.
>How is it useful at all?
Hah, I just tell you some of my own experience.
In summer 2003, I bought the last new machine, and it got these
shiny new ports they like to call USB. :)
I did not have much use for it, but I left it on - you never know
what standard next is the big win of the decade. And actually,
it did not took long (well, summer 2005) to get my first USB device.
Still, I am hell as sure I do not have USB-based sound devices
anytime soon, so it would be cool to deactivate the whole usbsound
menu at once. I think I said that in the patch description, did not I?
>Anyway, I'd like to confirm that this really works before merging to
>the ALSA tree. As Mauro suspected, kconfig seems not working as
>expected...
Unfortunately, there are sometimes non-visible options in menus (the
Networking>QoS menu for example) that, when converted to menuconfig-if-endif,
also get lost when the menuconfig object is deactivated. In case of QoS, this
can break compilation. For most subsystems however, it works alright because
the particular subsystem referencing CONFIG_INVISIBLE_THING is deactivated
anyway and does not get compiled.
Such strange menus (like QoS) have not been menuconfigized so far, it's just
too hard to keep the bits together. As far as other subsystems are concerned,
please give it some testing.
Jan
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists