From: Greg KH <greg@kroah.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can't use SYSFS for "Proprietry" driver modules !!!.
Date: Sat, 26 Mar 2005 10:28:28 -0800 [thread overview]
Message-ID: <20050326182828.GA8540@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10503261710320.13484-100000@mtfhpc.demon.co.uk>
On Sat, Mar 26, 2005 at 05:52:20PM +0000, Mark Fortescue wrote:
>
> I am writing a "Proprietry" driver module for a "Proprietry" PCI card and
> I have found that I can't use SYSFS on Linux-2.6.10.
>
> Why ?.
What ever gave you the impression that it was legal to create a
"Proprietry" kernel driver for Linux in the first place. I seriously
encourage you to consult your company's legal department if you insist
on attempting to do this, as they will be contacted by others after your
driver is released.
> I am not modifing the Kernel/SYSFS code so I should be able, to use all
> the SYSFS/internal kernel function calls without hinderence.
I'm sorry, but as you have found out, that is not possible.
> I believe that this sort of idiocy is what helps Microsoft hold on to its
> manopoly and as shuch hinders hardware/software development in all areas
> and should be chanaged in a way that promotes diversified software
> development.
If your company does not agree with the current license of the Linux
kernel, which prevents you from creating "Proprietry" drivers, then do
not write or create such drivers in the first place. We (the kernel
community) are not forcing you to write a Linux driver.
However, if you do wish to create a Linux driver, you _must_ abide by
the legal requirements of the kernel, which I feel, along with every IP
lawyer I have ever consulted, that it is not allowed to create a non-GPL
compatible kernel module.
Good luck,
greg k-h
next prev parent reply other threads:[~2005-03-26 18:28 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 17:52 Can't use SYSFS for "Proprietry" driver modules !!! Mark Fortescue
2005-03-26 18:28 ` Greg KH [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-03-27 1:15 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
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
2005-03-27 5:20 Chuck Ebbert
2005-03-27 7:21 Manfred Spraul
2005-03-28 1:03 Albert Cahalan
2005-03-28 2:04 Aaron Gyes
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=20050326182828.GA8540@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
/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