linux-kernel - Re: in-kernel DRM tree move around....

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: <1212051908.8215.1255644495@webmail.messagingengine.com>
Date:	Thu, 29 May 2008 11:05:08 +0200
From:	"Alexander van Heukelum" <heukelum@...tmail.fm>
To:	"Dave Airlie" <airlied@...il.com>,
	"kernel list" <linux-kernel@...r.kernel.org>,
	"dri-devel" <dri-devel@...ts.sourceforge.net>
Subject: Re: in-kernel DRM tree move around....

On Thu, 29 May 2008 10:46:22 +1000, "Dave Airlie" <airlied@...il.com>
said:
> Hi,
> 
> So I've been growing more annoyed with the current layout of the drm
> tree in the kernel,
> 
> a) it lives under char.
> b) everything in one directory.
> c) header files in one directory.
> d) no header files exposed to userspace.
> 
> http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=7df9a948d0f849466e3de259cccb49bc54cbad68
> 
> is a proposal to create drivers/gpu/drm, (I may move AGP in there as
> well later). It also creates per-driver subdirs.

Looks like a lot more suitable place! I just wonder if drivers/video/drm
would be even more logical?

Greetings,
    Alexander

> This to me solves the a-d problems.
> 
> There is also an out-of-tree kernel drm which I'll probably give some
> more thought later.
> 
> Dave.
-- 
  Alexander van Heukelum
  heukelum@...tmail.fm

-- 
http://www.fastmail.fm - Does exactly what it says on the tin

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