linux-kernel - Re: [PATCH 2/3] UIO: Documentation

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: <20070809071932.GA22318@suse.de>
Date:	Thu, 9 Aug 2007 00:19:32 -0700
From:	Greg KH <gregkh@...e.de>
To:	Jesper Juhl <jesper.juhl@...il.com>
Cc:	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>,
	linux-kernel@...r.kernel.org, "Hans J. Koch" <hjk@...utronix.de>
Subject: Re: [PATCH 2/3] UIO: Documentation

On Thu, Aug 09, 2007 at 01:03:39AM +0200, Jesper Juhl wrote:
> >
> I think the only way to avoid it is to not provide something like UIO.

Problem is, things like UIO provide a real solution for a wide range of
different types of devices.  Like the one provided in the kernel right
now, and a bunch of others that I am currently discussing with different
manufacturers (think high-speed DSPs that just want to give userspace
direct access to the card and have the kernel get the hell out of the
way so data can be read and processed as fast as possible.)

And also realize that some types of systems have been doing this very
same kind of kernel/userspace interface for many years, namely X :)

As for the legalities of using closed source userspace code with the UIO
interface, consult a lawyer if you have questions, and be sure to bring
up Alan's comments about derivative works :)

thanks,

greg k-h
-
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/