From: Thomas Gleixner <tglx@linutronix.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Greg KH <gregkh@suse.de>, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Benedikt Spranger <b.spranger@linutronix.de>,
"Hans J. Koch" <hjk@linutronix.de>
Subject: Re: [GIT PATCH] UIO patches for 2.6.21
Date: Sat, 28 Apr 2007 22:02:05 +0200 [thread overview]
Message-ID: <1177790525.7646.275.camel@localhost.localdomain> (raw)
In-Reply-To: <4633A6D7.3030806@tmr.com>
On Sat, 2007-04-28 at 15:56 -0400, Bill Davidsen wrote:
> Greg KH wrote:
> > Here are the updated UIO (Userspace I/O driver framework) patches for
> > 2.6.21.
> >
> > They have been revamped from the last time you have seen them, and they
> > include a real driver, the Hilscher CIF DeviceNet and Profibus card
> > controller, which is being used in production systems with this driver
> > framework right now. The kernel driver they replaced was a total mess,
> > with over 60+ ioctls to try to control the different aspects of the
> > device. See the last patch in this series for more details on this
> > driver.
> >
> I have a political question, if I have a user space driver, is my kernel
> tainted or not? Does this open another multi-month flame war around GPL,
> BSD, NDA, source available but not GPL, and all the other things we
> talked to death about inserting non-GPL modules?
The kernel driver has to be GPL, the user space part can be as any user
space code closed source. Of course we recommend to make it open as
those user space drivers which we did so far are all licensed under
LPGL.
There is nothing to flame, the user space boundary is entirely clear.
tglx
next prev parent reply other threads:[~2007-04-28 20:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 22:49 [GIT PATCH] UIO patches for 2.6.21 Greg KH
2007-04-27 22:50 ` [PATCH 1/3] UIO: Add the User IO core code Greg Kroah-Hartman
2007-04-27 22:50 ` [PATCH 2/3] UIO: Documentation Greg Kroah-Hartman
2007-04-27 22:50 ` [PATCH 3/3] UIO: Hilscher CIF card driver Greg Kroah-Hartman
2007-04-29 19:44 ` [PATCH 3/3] UIO: Hilscher CIF card driver (with patch) Hans-Jürgen Koch
2007-05-01 23:42 ` [PATCH 2/3] UIO: Documentation Randy Dunlap
2007-05-02 8:41 ` Hans-Jürgen Koch
2007-05-02 20:52 ` Randy Dunlap
2007-05-02 22:00 ` Hans-Jürgen Koch
2007-05-02 23:37 ` Randy Dunlap
2007-05-03 5:37 ` Greg KH
2007-05-03 6:39 ` Hans-Jürgen Koch
2007-05-04 9:37 ` Hans-Jürgen Koch
2007-05-07 17:46 ` Randy Dunlap
2007-05-07 20:01 ` Hans-Jürgen Koch
2007-04-27 23:19 ` Flaws with "UIO: Add the User IO core code" Alan Cox
2007-04-28 11:39 ` Thomas Gleixner
2007-04-28 18:52 ` Flaws with "UIO: Add the User IO core code" (with patch) Hans-Jürgen Koch
2007-04-28 20:24 ` Alan Cox
2007-04-28 20:38 ` Thomas Gleixner
2007-04-28 21:03 ` Hans-Jürgen Koch
2007-04-28 21:08 ` Thomas Gleixner
2007-04-28 21:14 ` Flaws with "UIO: Add the User IO core code" Hans-Jürgen Koch
2007-04-29 22:18 ` Flaws with "UIO: Add the User IO core code" (with patch) Hans-Jürgen Koch
2007-04-27 23:04 ` [GIT PATCH] UIO patches for 2.6.21 Andrew Morton
2007-04-27 23:11 ` Greg KH
2007-04-28 11:38 ` Thomas Gleixner
2007-04-27 23:26 ` Alan Cox
2007-04-28 0:28 ` Hans-Jürgen Koch
2007-04-28 13:00 ` Matthieu CASTET
2007-04-28 13:49 ` Hans-Jürgen Koch
2007-04-28 19:56 ` Bill Davidsen
2007-04-28 20:02 ` Thomas Gleixner [this message]
2007-04-28 20:03 ` Hans-Jürgen Koch
2007-04-28 20:15 ` Alan Cox
2007-04-28 20:31 ` Thomas Gleixner
2007-04-29 1:23 ` Greg KH
2007-04-29 8:30 ` Thomas Gleixner
2007-04-29 12:09 ` Jan Engelhardt
2007-04-29 16:27 ` Alan Cox
2007-05-07 20:02 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2007-05-08 14:04 Greg KH
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=1177790525.7646.275.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=b.spranger@linutronix.de \
--cc=davidsen@tmr.com \
--cc=gregkh@suse.de \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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