linux-kernel - Re: [RFC] Simple userspace interface for PCI drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1157056749.4386.137.camel@mindpipe>
Date:	Thu, 31 Aug 2006 16:39:08 -0400
From:	Lee Revell <rlrevell@...-job.com>
To:	Xavier Bestel <xavier.bestel@...e.fr>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC] Simple userspace interface for PCI drivers

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.

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/