- From: Bernd Porr <Bernd.Porr_at_cn.stir.ac.uk>
- Date: Tue, 24 Feb 2004 10:55:28 +0000
Frank, I think it's a good idea to compile within the 2.6 kernel. However, I would like to go one step further. Most of the postings in this mailing list are about problems compiling comedi. From my point of view it would be nice having comedi in a form that it can be basically _copied_ into the kernel (or externally compiled but virtually as part of the kernel). This gives everybody the opportunity to have a kernel with comedi or to compile comedi externally. I was quite amazed how litte has to be changed by my "patch-o-matic" for the 2.6.x kernel to integrate comedi into the kernel. Maybe we could extend the patch-o-matic so that we can generate a 2.4 kernel with comedi as part of it and a 2.6 kernel with comedi integrated. These scripts could then account for the differences between an "external" comedi and an "internal" comedi. When I did the debugging for 2.6.x I always modified the original comedi and then ran the patch-o-matic. Thus, the development can still be done in the "external" comedi but it would be also possible to have a comedi which compiles within the kernel. Finally I think many people would love a kernel which has comedi integrated. My poor cooleagues did the beta testing of my driver and nearly all of them generated missing symbols: They used the "external" comedi but their kernel config was out of sync with the actual kernel which was installed. /Bernd P.S.: Dave, thanks! Frank Mori Hess wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 23 February 2004 07:24 pm, David Schleef wrote: > >>Thanks mostly to Bernd Porr, this release has much improved >>Linux-2.6 support. Since increasing numbers of people are now >>using 2.6, it seems wise to get this out. >> > > > Do you have an opinion regarding moving the module compilation to kbuild? > That is, doing a make in the kernel directory with SUBDIRS overridden (and > CC modified to include our compat headers first). I've done it for the > linux-gpib kernel modules without problems. It would probably mean > abandoning 2.2 and earlier kernel support though. > > The current build system still has a couple issues I'm aware of. We don't > define KBUILD_BASENAME (not sure what problems it might cause, but > KBUILD_BASENAME is used in various asm kernel headers). Also, the > vermagic.o file isn't linked into comedi modules, which causes them to > taint the 2.6 kernel (I believe vermagic.o is supposed to prevent people > from compiling the kernel and the modules with different versions of gcc). > > - -- > Frank > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQFAOquY5vihyNWuA4URAuYeAJ9O+7H5vvDuIUljHUyhhvesXYz15gCgmC5j > jiNLufpTzGrZRvBKcx5XQyk= > =6MI+ > -----END PGP SIGNATURE----- > > _______________________________________________ > comedi mailing list > comedi_at_comedi.org > https://cvs.comedi.org/cgi-bin/mailman/listinfo/comedi
Received on 2004-02-24Z10:55:28