linux-kernel - Re: Closed source userspace graphics drivers with an open source kernel component

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]

Date:	Thu, 01 Jul 2010 17:18:46 -0700
From:	Saravana Kannan <skannan@...eaurora.org>
To:	Dave Airlie <airlied@...il.com>
CC:	Daniel Walker <dwalker@...eaurora.org>,
	LKML <linux-kernel@...r.kernel.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	linux-arm-msm@...r.kernel.org, jcrouse@...eaurora.org
Subject: Re: Closed source userspace graphics drivers with an open source
 	kernel component

Dave Airlie wrote:
> This is more about initial development stages. We maintain kernel
> API/ABI for all in-tree drivers, however before we put a driver into
> mainline, we usually need to redo the crazy interfaces that vendors
> have come up with. Like 32/64 alignment, passing userspace addresses
> into the kernel, passing phy addresses to userspace etc. If the
> userspace binary is closed that process becomes next to impossible.

My 2 cents:
I think we should leave the onus of fixing the userspace to work with 
the sane kernel API with the entity trying to get their drivers into the 
kernel. I think it's a better approach (as in, more likelihood of 
getting device support) than saying, we will only allow fully open 
sourced kernel drivers.

-Saravana
--
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/