> But... how does situation change when Evil Linker does #include > <pop3/gpl_header_file_with_some_inline_functions.h> from his > binary-only part?
Right, but *why* is he doing that? The answer: It is the most practical way to write his driver. > I believe situation in this case changes a lot... And that's what > embedded people are doing; I do not think they are creating their own > headers or their own inline functions where headers contain them. They don't have to. You *cannot* use copyright to make ideas harder to express. That's what patents are for. All the people who make this linking argument seem to be completely missing the entire *point* of copyright. A copyright protects the *one* way you chose to express a particular idea. It cannot protect function. It cannot make other ideas harder to express. This is not some loophole or something. This is the most fundamental thing about copyrights that there is. This is the reason they're so easy to get. This is the reason they last so long. They *cannot* impede interoperation. They cannot make other ideas harder to express. They can't even make the very same idea you expressed harder to express. Copyrights are not patents. It is clear, at least in the United States, that something like "a kernel driver to make <some particular version of Linux> work with <some particular piece of hardware>" is an idea. You cannot own all the most practical ways to express that idea. When practical engineering concerns make one way (or one group of ways) the most reasonable, you simply *cannot* own them all with copyright. DS - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
