dri2: SProcDRI2Connect - send the response.
The swapped implementation of DRI2Connect is always responding with empty device and driver values. However the response was only prepared and never sent (also had undefined .type member), causing e.g. glxinfo get stuck waiting for response when started remotely from machine with different endianity. Signed-off-by: Michal Srb <msrb@suse.com> Reviewed-by: Jeremy Huddleston <jeremyhu@apple.com> Tested-by: Michel Dänzer <michel@daenzer.net> Signed-off-by: Keith Packard <keithp@keithp.com>
This commit is contained in:
parent
457fc77691
commit
9bc53d8cb0
|
@ -589,12 +589,15 @@ SProcDRI2Connect(ClientPtr client)
|
|||
if (sizeof(*stuff) / 4 != client->req_len)
|
||||
return BadLength;
|
||||
|
||||
rep.type = X_Reply;
|
||||
rep.sequenceNumber = client->sequence;
|
||||
swaps(&rep.sequenceNumber);
|
||||
rep.length = 0;
|
||||
rep.driverNameLength = 0;
|
||||
rep.deviceNameLength = 0;
|
||||
|
||||
WriteToClient(client, sizeof(xDRI2ConnectReply), &rep);
|
||||
|
||||
return Success;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue