lkml.org 
[lkml]   [2005]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: Please open sysfs symbols to proprietary modules
    From
    Date
    On Iau, 2005-02-03 at 04:54, Zan Lynx wrote:
    > So, what's the magic amount of redirection and abstraction that cleanses
    > the GPLness, hmm? Who gets to wave the magic wand to say what
    > interfaces are GPL-to-non-GPL and which aren't?

    The "derivative work" distinction in law, which can be quite complex
    because it involves issues like intent. Other than the intentional clear
    statement that the syscall interface is considered a barrier by the
    authors there is no other statement.

    The GPL grants of patents are having a similar effect too, you'll need a
    patent license from IBM to write RCU using code for example unless its
    free software.

    You also appear to misunderstand dual licensing. If you have a GPL/BSD
    dual licensed module then when its using GPL'd code it ends up a
    combined GPL work you can't add binary blocks too (except as per being
    "not a derivative work")

    Alan

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:10    [W:2.339 / U:0.060 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site