linux-kernel - [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>] [day] [month] [year] [list]

Date:	Sat, 22 Jul 2006 15:40:57 -0400
From:	Louis E Garcia II <louisg00@...lsouth.net>
To:	linux-kernel@...r.kernel.org, airlied@...il.com
Subject: [RFC] GPU device layer patchset (00/07)

I believe their is some confusion over the use of graphics and video. It
might seem logical to use video for video cards but we also have another
use of video for video capture. The source tree has the drm
under /drivers/video but /sys has class/graphics for fb and
class/drm. /dev has /drm /fb.

Is is possible to clean some of this up? Since you are starting on a
rework can you put the gpu device layer source under /drivers/graphics
and maybe move the drm to /drivers/graphics/drm? Frame buffer could
possibly be moved under graphics too. 

The gpu layer can register /sys/class/graphics and udev can still
create /dev/dri/cardX and /dev/fbX. We can create a new dev node
maybe /dev/graphics/cardX or /dev/graphics/{drmX,fbX} for transition.

I really don't want to get in the middle of this as I am not that
technical but I wanted to share my thoughts.

-Louis

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