From: Steven Rostedt <rostedt@goodmis.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: floam@sh.nu, LKML <linux-kernel@vger.kernel.org>,
arjan@infradead.org, Paul Jackson <pj@engr.sgi.com>,
gilbertd@treblig.org, vonbrand@inf.utfsm.cl, bunk@stusta.de
Subject: Re: Can't use SYSFS for "Proprietry" driver modules !!!.
Date: Mon, 28 Mar 2005 20:27:21 -0500 [thread overview]
Message-ID: <1112059642.3691.15.camel@localhost.localdomain> (raw)
In-Reply-To: <c4ce304162b3d2a3ad78dc9e0bc455f5@mac.com>
On Mon, 2005-03-28 at 19:56 -0500, Kyle Moffett wrote:
> On Mar 28, 2005, at 19:21, Steven Rostedt wrote:
> > So you are saying that a stand alone section of code, that needs
> > wrappers to work with Linux is a derived work of Linux? If there's
> > some functionality, that you make, and it just happens to need
> > some kind of operating system to work. Does that make it a derived
> > work of any operating system?
>
> It depends on how special and different the wrappers for Linux are
> from the wrappers for other operating systems. Like, for example,
> the sysfs stuff is so radically different from the APIs that other
> operating systems provide that anything using it is most likely
> copied from other in-kernel sysfs code, and is therefore derived
> from the Linux kernel.
>
If your stand alone code has it's own API and your GPL wrapper handles
the sysfs interface, then this might get around it.
> > OK, I took your advise and found this from googling:
> >
> > http://www.pbwt.com/Attorney/files/ravicher_1.pdf
>
> Mmm, good reference, thanks!
>
You're welcome!
> > Unless you misunderstood me, and thought that I was talking
> > about taking some part of Linux and making it work under another
> > OS, I still stand by my statement.
>
> I think it really depends on the APIs implemented. Anything based
> on the sysfs code, even if only using the APIs, will probably be
> found to be a derivative work (NOTE: IANAL) because the sysfs API
> is so very different from everything else. Other interfaces like
> PCI management, memory management, etc, may not be so protectable,
> because they are standard across many systems. If Linux got a
> new and unique memory hotplug API, however, that might be a very
> different story. Similar things could be said about integration
> between drivers and the new Unified Driver Model, which appears to
> be quite original.
>
Yes, but as the article states, ideas are not protected under copyright
law. So an unique idea to handle hotplug then it may still not be
covered. This is all very ambiguous, and is too confusing. I'll leave
it up to the lawers!
-- Steve
next prev parent reply other threads:[~2005-03-29 1:28 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 1:15 Can't use SYSFS for "Proprietry" driver modules !!! Aaron Gyes
2005-03-27 1:29 ` Lee Revell
2005-03-27 2:55 ` Kyle Moffett
2005-03-27 8:57 ` Jan Engelhardt
2005-03-27 17:09 ` Willy Tarreau
[not found] ` <1111913399.6297.28.camel@laptopd505.fenrus.org>
2005-03-27 17:40 ` Kyle Moffett
2005-03-27 17:52 ` Dave Airlie
2005-03-27 17:58 ` Kyle Moffett
2005-03-27 18:04 ` Dr. David Alan Gilbert
2005-03-27 18:35 ` Adrian Bunk
2005-03-27 18:46 ` Jan Engelhardt
2005-03-27 19:16 ` Aaron Gyes
2005-03-27 19:30 ` Kyle Moffett
2005-03-28 1:54 ` Horst von Brand
2005-03-28 9:27 ` Jan Engelhardt
2005-03-28 12:04 ` Steven Rostedt
2005-03-28 13:12 ` linux-os
2005-03-28 13:46 ` Steven Rostedt
2005-03-28 14:50 ` Jan Engelhardt
[not found] ` <1112016850.6003.13.camel@laptopd505.fenrus.org>
2005-03-28 13:57 ` Steven Rostedt
2005-03-28 23:43 ` Paul Jackson
2005-03-29 0:21 ` Steven Rostedt
2005-03-29 0:56 ` Kyle Moffett
2005-03-29 1:27 ` Steven Rostedt [this message]
2005-03-29 12:15 ` linux-os
2005-03-29 12:29 ` Sean
2005-03-30 19:47 ` Rik van Riel
2005-03-30 19:57 ` linux-os
2005-03-31 11:35 ` Sean
2005-03-31 12:34 ` linux-os
2005-03-31 14:20 ` Sean
2005-03-31 22:55 ` Kyle Moffett
2005-03-30 23:30 ` John Pearson
2005-04-03 14:07 ` Clemens Schwaighofer
2005-03-29 16:31 ` Horst von Brand
2005-03-30 14:38 ` Olivier Galibert
2005-03-30 19:49 ` Rik van Riel
2005-03-29 1:22 ` Paul Jackson
2005-03-29 1:31 ` Steven Rostedt
2005-03-28 20:47 ` Horst von Brand
2005-03-27 19:37 ` Adrian Bunk
2005-03-27 21:22 ` Diego Calleja
2005-03-27 23:09 ` Greg KH
2005-03-28 13:14 ` Geert Uytterhoeven
2005-03-27 18:12 ` Greg KH
2005-03-29 1:04 ` Aaron Gyes
2005-03-29 3:33 ` Greg KH
2005-03-29 4:03 ` Zan Lynx
2005-03-29 4:44 ` Greg KH
2005-04-03 23:41 ` Mark Lord
2005-04-04 4:01 ` Paul Jackson
2005-04-04 7:15 ` Christoph Hellwig
2005-03-29 4:28 ` Aaron Gyes
2005-03-29 4:45 ` Greg KH
2005-03-29 5:01 ` Aaron Gyes
2005-03-29 5:05 ` Greg KH
2005-03-29 5:29 ` Aaron Gyes
2005-03-29 5:37 ` Brian Gerst
-- strict thread matches above, loose matches on Subject: below --
2005-03-28 2:04 Aaron Gyes
2005-03-28 1:03 Albert Cahalan
2005-03-27 7:21 Manfred Spraul
2005-03-27 5:20 Chuck Ebbert
2005-03-26 17:52 Mark Fortescue
2005-03-26 18:28 ` Greg KH
2005-03-26 20:34 ` Lee Revell
2005-03-26 20:46 ` Jan Engelhardt
2005-03-27 0:48 ` Greg KH
[not found] ` <1111885480.1312.9.camel@mindpipe>
2005-03-27 3:20 ` Greg KH
2005-03-27 3:30 ` Lee Revell
2005-03-27 18:10 ` Greg KH
2005-03-27 18:37 ` Steven Rostedt
2005-03-27 22:01 ` Adrian Bunk
2005-03-27 23:54 ` Steven Rostedt
2005-03-28 1:39 ` Adrian Bunk
2005-03-28 1:50 ` Steven Rostedt
2005-03-28 9:31 ` Jan Engelhardt
2005-03-28 14:45 ` Adrian Bunk
2005-03-27 22:41 ` Dave Airlie
2005-03-28 0:53 ` Chris Wedgwood
2005-03-27 15:04 ` Alan Cox
2005-03-28 3:56 ` Clemens Schwaighofer
2005-03-29 2:37 ` Coywolf Qi Hunt
2005-03-29 5:58 ` Jim Crilly
2005-03-28 16:52 ` Mark Fortescue
2005-03-28 18:38 ` Rik van Riel
2005-03-29 3:36 ` Greg KH
2005-03-29 6:17 ` Kevin Puetz
2005-03-27 12:42 ` Sean
2005-03-27 13:53 ` Wichert Akkerman
2005-03-27 15:06 ` Alan Cox
2005-03-28 13:12 ` Geert Uytterhoeven
2005-03-29 3:41 ` Lee Revell
2005-03-29 1:53 ` David Schwartz
2005-03-29 2:06 ` Kyle Moffett
2005-03-29 19:00 ` David Schwartz
2005-03-30 14:15 ` Olivier Galibert
2005-04-02 2:11 ` David Schwartz
2005-03-27 20:50 ` James Courtier-Dutton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1112059642.3691.15.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=floam@sh.nu \
--cc=gilbertd@treblig.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=pj@engr.sgi.com \
--cc=vonbrand@inf.utfsm.cl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox