Re: Kbuild problem
From: Adrian Bunk
Date: Sun Feb 18 2007 - 05:40:48 EST
On Sun, Feb 18, 2007 at 12:22:10AM -0500, Kai Germaschewski wrote:
> On Sat, 17 Feb 2007, Tilman Schmidt wrote:
> > Alright, then so be it. But that raises another question:
> > asyncdata.o is only needed for M105 and M101, not for the base
> > driver. How do I express in Kbuild that asyncdata.o is to be added
> > to gigaset-y only if CONFIG_GIGASET_M105 and CONFIG_GIGASET_M101
> > are not both 'n'?
> The way this is typically done is via Kconfig. Add a config option
> ASYNCDATA (actually something more descriptive/specific would be better),
> add a "select ASYNCDATA" to the config options for m101 and m105, and then
> you can use CONFIG_ASYNCDATA to decide whether to add asyncdata.o in the
One disadvantage of this approach is that in a kernel with
CONFIG_GIGASET_BASE=y, you can't later compile and load the usb_gigaset
or ser_gigaset modules without rebooting since they require a change to
the kernel image.
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/