On Die, 2002-12-10 at 18:14, Steven Newbury wrote:
> I have got DRI running with Dual Screens with DRI working on display
> :0.0 and Indirect rendering on :0.1.
>
> If I attempt to enable DRI on the second screen if fails to open
> /dev/dri/card0 because it is busy. It is ready used for the fi
Ian Romanick wrote:
On Tue, Dec 10, 2002 at 05:14:37PM +, Steven Newbury wrote:
I have got DRI running with Dual Screens with DRI working on display
:0.0 and Indirect rendering on :0.1.
If I attempt to enable DRI on the second screen if fails to open
/dev/dri/card0 because it is busy. It
On Tue, Dec 10, 2002 at 05:14:37PM +, Steven Newbury wrote:
> I have got DRI running with Dual Screens with DRI working on display
> :0.0 and Indirect rendering on :0.1.
>
> If I attempt to enable DRI on the second screen if fails to open
> /dev/dri/card0 because it is busy. It is ready use
Tue, 10 Dec 2002 17:14:37 +, tu as dit :
> I have got DRI running with Dual Screens with DRI working on display
> :0.0 and Indirect rendering on :0.1.
> If I attempt to enable DRI on the second screen if fails to open
> /dev/dri/card0 because it is busy. It is ready used for the first
I have got DRI running with Dual Screens with DRI working on display
:0.0 and Indirect rendering on :0.1.
If I attempt to enable DRI on the second screen if fails to open
/dev/dri/card0 because it is busy. It is ready used for the first
screen. On failing to access the device DRI is then disa
