From: Jamie Lokier <jamie@shareable.org>
To: linux-kernel@vger.kernel.org
Subject: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: Tue, 6 May 2003 17:42:52 +0100 [thread overview]
Message-ID: <20030506164252.GA5125@mail.jlokier.co.uk> (raw)
I was mulling over a commercial project proposal, and this question
came up:
What's the position of kernel developers towards using the GPL'd Linux
kernel modules - that is, device drivers, network stack, filesystems
etc. - with a binary-only, closed source kernel that is written
independently of Linux?
I realise that linking the modules directly with the binary kernel is
a big no no, but what if they are dynamically loaded?
There seems to be a broad agreement, and I realise it isn't unanimous,
that dynamically loading binary-only modules into the Linux kernel is
ok. Furthermore, there are some funny rules about which interfaces a
binary-only module may use and which it may not, before it's
considered a derivative work of the kernel.
So, as dynamic loading is ok between parts of Linux and binary-only
code, that seems to imply we could build a totally different kind of
binary-only kernel which was able to make use of all the Linux kernel
modules. We could even modularise parts of the kernel which aren't
modular now, so that we could take advantage of even more parts of Linux.
What do you think?
-- Jamie
next reply other threads:[~2003-05-06 16:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 16:42 Jamie Lokier [this message]
2003-05-06 17:35 ` Alan Cox
2003-05-06 18:54 ` Jamie Lokier
2003-05-06 19:28 ` Jean-Marc Lienher
2003-05-06 19:53 ` Alan Cox
2003-05-06 22:31 ` Jamie Lokier
2003-05-06 21:38 ` Alan Cox
2003-05-08 21:36 ` Pavel Machek
2003-05-06 19:17 ` Eric W. Biederman
2003-05-06 21:55 ` Jamie Lokier
2003-05-06 22:21 ` David Schwartz
2003-05-07 8:21 ` Eric W. Biederman
2003-05-07 14:25 ` Valdis.Kletnieks
2003-05-07 14:31 ` Jamie Lokier
2003-05-07 15:50 ` Eric W. Biederman
2003-05-06 20:43 ` Pavel Machek
2003-05-06 22:18 ` Jamie Lokier
2003-05-06 21:31 ` Alan Cox
2003-05-06 22:48 ` Jamie Lokier
2003-05-07 12:20 ` Alan Cox
2003-05-07 14:26 ` Jamie Lokier
2003-05-07 15:18 ` Pavel Machek
2003-05-08 11:11 ` Krzysztof Halasa
[not found] <20030506165014$3d57@gated-at.bofh.it>
[not found] ` <20030506193019$0d29@gated-at.bofh.it>
[not found] ` <20030506220018$5b96@gated-at.bofh.it>
2003-05-07 1:17 ` Tony 'Nicoya' Mantler
[not found] <BKEGKPICNAKILKJKMHCAAEBCCLAA.Riley@Williams.Name>
2003-05-07 16:57 ` Eric W. Biederman
2003-05-09 1:23 Jean Tourrilhes
2003-05-13 9:08 Dean McEwan
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=20030506164252.GA5125@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®