From: Greg KH <greg@kroah.com>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Lee Revell <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] Simple userspace interface for PCI drivers
Date: Thu, 31 Aug 2006 14:40:56 -0700 [thread overview]
Message-ID: <20060831214056.GB11939@kroah.com> (raw)
In-Reply-To: <1157057934.24286.3.camel@bip.parateam.prv>
On Thu, Aug 31, 2006 at 10:58:54PM +0200, Xavier Bestel wrote:
> Le jeudi 31 ao?t 2006 ? 16:39 -0400, Lee Revell a ?crit :
> > On Thu, 2006-08-31 at 10:30 +0200, Xavier Bestel wrote:
> > > Hi Greg,
> > >
> > > On Wed, 2006-08-30 at 08:23, Greg KH wrote:
> > > [...]
> > > > Thomas and I lamented that we were getting tired of seeing stuff like
> > > > this, and it was about time that we added the proper code to the kernel
> > > > to provide everything that would be needed in order to write PCI drivers
> > > > in userspace in a sane manner. Really all that is needed is a way to
> > > > handle the interrupt, everything else can already be done in userspace
> > > > (look at X for an example of this...)
> > > [...]
> > > > So, here's the code.
> > >
> > > I know I look like I'm trolling here, but as this is the perfect
> > > stable-binary-driver-ABI some people have been looking for, it would be
> > > wise to make it taint the kernel with its own flag.
> >
> > Why? There's no technical or legal requirement for userspace drivers to
> > be GPLed.
>
> Precisely. How do you know the bugreport you received isn't caused by
> some weird binary userspace driver hosing the PCI bus ?
You don't know that today. Nothing new here. So no, adding a taint
flag would achieve nothing. Unless you want to do that today for all
the ways a userspace program can directly access a PCI device today?
greg k-h
next prev parent reply other threads:[~2006-08-31 21:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 6:23 Greg KH
2006-08-30 10:09 ` Thomas Gleixner
2006-08-30 14:34 ` Matt Porter
2006-08-30 16:25 ` Thomas Gleixner
2006-08-30 17:55 ` Greg KH
2006-08-30 20:32 ` Foli Ayivoh
2006-08-30 21:01 ` Matthias Schniedermeyer
2006-08-30 21:25 ` linux-os (Dick Johnson)
2006-08-30 22:08 ` Greg KH
2006-09-01 1:36 ` Brice Goglin
2006-09-01 3:22 ` Greg KH
2006-09-01 3:37 ` Brice Goglin
2006-09-01 4:27 ` Greg KH
2006-08-31 13:49 ` Andi Kleen
2006-09-01 18:16 ` Greg KH
2006-08-30 17:07 ` Manu Abraham
2006-08-30 17:52 ` Greg KH
2006-08-30 22:50 ` Manu Abraham
2006-08-31 0:17 ` Greg KH
2006-08-31 13:24 ` Manu Abraham
2006-08-31 22:42 ` Greg KH
2006-08-31 7:40 ` Andrew Morton
2006-08-31 8:05 ` Thomas Gleixner
2006-08-31 8:30 ` Xavier Bestel
2006-08-31 20:39 ` Lee Revell
2006-08-31 20:53 ` Chris Friesen
2006-08-31 21:39 ` Greg KH
2006-08-31 20:58 ` Xavier Bestel
2006-08-31 21:12 ` Lee Revell
2006-08-31 21:18 ` Xavier Bestel
2006-08-31 21:33 ` Manu Abraham
2006-08-31 21:40 ` Greg KH [this message]
2006-09-01 21:17 ` Pavel Machek
2006-09-03 8:34 ` Thomas Gleixner
2006-09-12 19:47 ` Sam Ravnborg
2006-09-14 5:57 ` 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=20060831214056.GB11939@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=tglx@linutronix.de \
--cc=xavier.bestel@free.fr \
/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
Powered by JetHome