Am 17.02.2007 11:52 schrieb Adrian Bunk: > On Sat, Feb 17, 2007 at 01:04:33AM +0100, Tilman Schmidt wrote: >> [...] I'd prefer a >> Makefile which builds modular usb_gigaset.ko and/or ser_gigaset.ko >> like the present one (including asyncdata.o), but when linking >> usb-gigaset.o and ser-gigaset.o into the kernel includes asyncdata.o >> only once. Trouble is, I don't know how to express that in Kbuild. >> >> Any ideas? > > CONFIG_GIGASET_M105=y, CONFIG_GIGASET_M101=m and similar problems might > make this quite tricky.
I am no judge of that. All I know about the possibilities of Kbuild is what the files in Documentation/kbuild tell me. From browsing through other kernel Makefiles it would appear that there are more possibilities though, such as if/then/else constructs. > Shared functionality simply doesn't belong into any of the affected > modules, but to a different place where all users can access it. 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'? Thanks, Tilman -- Tilman Schmidt E-Mail: [EMAIL PROTECTED] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
signature.asc
Description: OpenPGP digital signature
