With gpibintctrl, under linux Red Hat 8.0
I initialise ibdev with
enter board index: 0
enter primary address: 7
enter secondary address: 0
enter timeout: 0
enter 'EOI on last byte' flag: 0
enter end-of-string mode/byte: 0x0a
then I call ibwrt
ud0: ibwrt "VE?\r\n"
[0100] ( cmpl )
count: 5
and ibrd for 30 bytes
ud0: ibrd
enter byte count: 30
[2100] ( end cmpl )
count: 30
00 00 00 00 00 00 00 00 . . . . . . . .
00 00 00 00 00 00 00 00 . . . . . . . .
00 00 00 00 00 00 00 00 . . . . . . . .
00 00 00 00 00 00 . . . . . .
if I call ibrd for 16 and 14 bytes :
ud0: ibrd
enter byte count: 16
[0100] ( cmpl )
count: 16
45 53 50 33 30 30 20 56 E S P 3 0 0 V
65 72 73 69 6f 6e 20 33 e r s i o n 3
ud0: ibrd 14
[2100] ( end cmpl )
count: 14
2e 30 38 20 30 39 2f 30 . 0 8 0 9 / 0
39 2f 30 32 0d 0a 9 / 0 2 . .
I remember that in linux beta driver 0.8.5, which is not thread safe, the 30 bytes response was good : what is the difference between the two code parts which can
explain the difference between the 2 behaviour?