nanogui: nano-X driver stability discussion
Subject:
RE: nano-X driver stability discussion
From:
Alex Holden ####@####.####
Date:
20 May 1999 19:46:29 -0000
Message-Id: <Pine.LNX.4.04.9905202030410.382-100000@hyperspace>
On Thu, 20 May 1999, Greg Haerr wrote:
> Well I'm glad you figured it out, I couldn't. But the problem that
> I saw wasn't a hang bug a crash. The client hangs on reads so it should
> never get garbage back, though, right?
Hmm, I saw a hang, for the reason I described. It doesn't matter now as
it's getting thrown out anyway.
> Also, another thing I started to change in the client/server code,
> but now you should know... In the first version, the GrSendBlock took
> an int, rather than a long for the size parm. In ELKS and other 16-bit systems,
> this would fail if say ReadArea were called with more than 256x256 pixels (64k).
> Also, write() typically works only with < 64k data, so the internal write
> loop also needs recoding...
Do you mean that since write takes an int as the length argument, it can't
write more than 64K at a time on 16 machines?
--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------
