linux-kernel - Re: DRM drivers with closed source user-space: WAS [Patch 0/3] Resubmit VIA Chrome9 DRM via

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:	Mon, 20 Jul 2009 16:16:20 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Thomas Hellström <thomas@...pmail.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	DRI <dri-devel@...ts.sourceforge.net>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: DRM drivers with closed source user-space: WAS  [Patch 0/3]
 Resubmit VIA Chrome9 DRM via_chrome9 for upstream

> If the common agreement of the linux community is to *NOT* allow these 
> drivers in, so be it, then be honest and go ahead and tell the driver 
> writers. Don't make them respin their development trying to fix minor 
> flaws when their driver won't get in anyway!

The existing policy based on what has been rejected is:

- If you have something which only works with some non-free tightly
  integrated software then we don't accept it

	Examples - GMX500, Intel wireless regulatory daemon.

So until there is an open source user and test case for the kernel code
it has no place in the kernel (and indeed if the two are closely
interconnected and dependent then there are good 'talk to your lawyer'
reasons as well)

Once there is a useful combination of kernel/user space free software for
the card then it makes sense to look at a merge. Until then you don't
even know what the final interface will look like and what is actually
needed kernel side.

The VIA stuff might be a useful basis for that work but that is a when/if
anyone ever writes drivers for it.

My guess is that if someone cares enough about the hardware they need to
get EXA working along with 2D render, then submit the bits the need to do
hardware rendering. After that tackle what is needed for 3D - as is
happening with the Nvidia drivers and then submit a DRM module for their
work.

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