linux-kernel - Multi-card DRI interface timeframe

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:	Sun, 7 Feb 2010 08:39:57 -0500
From:	Robert Bradbury <robert.bradbury@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Multi-card DRI interface timeframe

Have: Radeon R3450 & Intel i915. Want multiple X terminals and multiple screens.

Excerpted logs:
Xorg.2.log:(II) RADEONHD(0): [DRI] installation complete
Xorg.3.log:(EE) RADEONHD(0): [dri] DRIScreenInit failed.  Disabling DRI.

Xterms :0 and :1 are like :3.  I am under the impression that only one
VT (here :2) can get the DRI interface.  That terminals is fast, the
rest much less so. (Its also annoying that the DRI gets assigned to
the VT/X started but assume thats an Xorg scheduling issue).
I am under the impression that how many VTs/X Servers can use the DRI
is a kernel issue.

Q1: What is the kernel development time frame for allowing the active
VT to take control of the DRI interface?

Now, this machine has both the Intel i915 graphics interface and F3450
card with 2 video interfaces.  The X server (via Xorg.conf) has no
problem setting up both hardware controllers.  It is possible to do
dual screen (like xinerama but using a large virtual screen) across
both Radeon interfaces.  However one cannot do "dual screen" (or
tri-screen) across both hardware controllers.  (Of course in this
situation it seems that switching VTs would involve switching both
controllers so it would seem to me to involve kernel issues.)

Q2: What is the kernel development time frame for allowing mixing and
matching video controller hardware across multiple screens?

I realize that this is not the focus of the LKML per se but the KMS,
DRI, and controller drivers all *are* in the Kernel.  If other forums
would be better for these types of questions then please suggest them.

Thank you,
Robert Bradbury
--
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/