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: <20080529113406.5d8f75c4@core>
Date:	Thu, 29 May 2008 11:34:06 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Alexander van Heukelum" <heukelum@...tmail.fm>
Cc:	"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 11:05:08 +0200
"Alexander van Heukelum" <heukelum@...tmail.fm> wrote:

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

I think gpu is better - we are seeing various GPU as CPU accelerator
toolkits appearing and assuming the AMD one ends up open source we will
end up with gpu/something that isn't video.

Remember GPU = Grahi^WGeneric Processing Unit ;)

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/