linux-kernel - Re: [RFC] GPU device layer patchset (00/07)

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: <Pine.LNX.4.64.0607221753390.5320@skynet.skynet.ie>
Date:	Sat, 22 Jul 2006 18:00:39 +0100 (IST)
From:	Dave Airlie <airlied@...ux.ie>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] GPU device layer patchset (00/07)

>
> Where can I find more info on why this might be nice?
> Or simply more info on what this actually does for me?

It does nothing for you yet, it is just step one for getting the DRM and 
framebuffer drivers to co-exist in the driver model world, with the next 
step being allowing a channel of communication between the two layers with 
a view that later I can ask the DRM to disable fbdev or pass info to it..

Why do we not want fbdev and DRM in one driver? as it would break way too 
many existing systems..

It also allows DRM to get called at suspend/resume time.

Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG

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