AFAIK the current interpretation suggests that you must keep it out of
the statically-linked kernel image. This would tend to imply using an
initrd image for critical modules which can't be GPL'd.
It has also been mentioned that you could shove all non-GPL'd binary
code into a special ELF section of the static kernel image, and
similarly satisfy the GPL 'separate work' clause.
Standard IANL / IANAL disclaimers apply.
( I Am Not Linus / I Am Not A Lawyer )
Jeff
-- Custom driver development | Never worry about theory as long Open source programming | as the machinery does what it's | supposed to do. -- R. A. Heinlein- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/