Hi,
The linux-ppc kernel has an option (CONFIG_MAC_ADBKEYCODES) to use the old
ADB-style keycodes. I imagine setting this option to no uses the conversion
you're talking about. For the record, the scancodes I see (from showkey -s)
are as follows:
KeyPad Equals : 0x5c 0xdc
Left Arrow
Hello,
I'm attacking the bottle necks in my app and I've just noticed
that XvShmPutImage is one of my bottlenecks. It takes 4 msecs to draw 1
512 x 256 sized frame.
I suspect that I am doing something wrong, but I cant find what. Maybe
it is how I initialise the shared memory.
I've
woops, i forgot to attach the code. here it is attached.
To re-capitulate: XvShmPutImage seems to be slow, can anyone see why
that might be so, am I initiating Xv and its buffers correctly?
(p4 2ghz, 512 MB ram, 32Mb nvideo gforce go, calling XvShmPutImage on a
512x256 YUV422 image takes
On Sun, 8 Jun 2003, etienne deleflie wrote:
Hello,
I'm attacking the bottle necks in my app and I've just noticed
that XvShmPutImage is one of my bottlenecks. It takes 4 msecs to draw 1
512 x 256 sized frame.
What do you get for:
x11perf -repeat 1 -shmput500
If run in
Mark Vojkovich wrote:
On Sun, 8 Jun 2003, etienne deleflie wrote:
Hello,
I'm attacking the bottle necks in my app and I've just noticed
that XvShmPutImage is one of my bottlenecks. It takes 4 msecs to draw 1
512 x 256 sized frame.
What do you get for:
x11perf -repeat 1
