I am trying to understand the end objective of
the JTAG work discussed in one of the threads last week (sorry, I'm behind on my mails!).
There was one response that said: "The hope is that it would help debug
usb/bt device issues on kw."; but beyond this I could not make out the use
case for thi
> /n/sources/contrib/cinap_lenrek/draw.c
Works great -- thanks.
That code path is for the proc that called rfork(). The
new child proc returns through forkchild().
Hi,
I am trying to understand the implementation of sysrfork() in
/sys/src/9/port/sysproc.c:90.
When the new process is created p->nerrlab is set to zero,
however when sysrfork() returns,as the new process, poperror() is
called will clean up the error stack after the matching waserror()
before th
this is how /sys/src/cmd/vnc/draw.c was changed to not "mouse turd" on
vesa. have put the changed file in contrib at:
/n/sources/contrib/cinap_lenrek/draw.c
didnt made a patch because its just a work arround, not a real fix.
cpu% diff -c /n/dump/2009/0923/sys/src/cmd/vnc/draw.c draw.c
/n/dump/20
"mouse turds" happend in equis when using vesa too. it happens when
you loadimage() directly on the screen with the mouse over it. it
seems the software cursor isnt hidden and restored on loadimage
correctly. as a work arround, one can loadimage() in a temporary
offscreen image and then use draw
