The term "Resources" doesn't apply. It's
an old-style port that needs lots of time
to properly read. Stick an analog joystick
on it and you have to pump some volts through
it, let it settle a bit, measure it, and from
that determine the pot position. Lots and
lots of time (it has nothing to do with
"resources"). Since the time to read the
port is constant, the faster the CPU, the
more that's wasted. It's like putting on
the brakes 20x a second as you drag down
the strip. Compare with a device (a game
port could be considered a device) that
works with an interrupt, where the device
does all the work, and the CPU only stops
to read the answer (it doesn't have to calc
the answer). To put it in simple terms.
E- [Wed, 13 Dec 2006 21:15:21 -0800]:
>You got to be kidding.
>The gameport was around long before the Pentium when computers were still
>running under 12Mhz. I highly doubt the gameport is a resource hog.
>The big problem is that a "game port" has to
>be polled. This, as well as the process used
>to read the port, wastes lots of CPU time.
40th Floor - Software @ http://40th.com/
iPlay : the ultimate audio player for mobiles
parametric eq, xfeed, reverb; all on a mobile