In article <Pine.LNX.4.21.0008290851330.26015-100000@phobos.fachschaften.tu-muenchen.de>,
Simon Richter <Simon.Richter@phobos.fs.tum.de> wrote:
>On Tue, 29 Aug 2000, Mike A. Harris wrote:
>
>> #include'ing header files is not necessarily ok. Some headers
>> include "inline functions" which is GPL code. Such inclusion in
>> a module makes that module have to comply with GPL.
>
>I think this needs to be resolved ASAP. I don't have kernel sources handy,
>so I cannot tell you whether the functions are actually worth being
>protected (inb/outb doesn't belong to this group really),
If it is in the header file I think it should be open for use.
Not allowing inline code to be used just adds another hoop to jump. Just
compile with that function explicitly defined. Define another version in
the kernel and use that in your module instead. Etc.
There was another thread a few days ago commenting that modern processors
may actually be a bit faster with less inlined code and unrolled loops. Which
may mean that a lot of what is now inlined may be better off compiled in.
--
__O
Fireplug - a Lineo company _-\<,_
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net> www.fireplug.net 604-461-7532
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:24 EST