gc-linux-devel

[Gc-linux-devel] GCPad driver + mouse emulation.

[Free T. C. <Fre...@fr...>]

Hello everybody !

I'm currently trying to port the GCPad driver from GCLib to Linux/GC (I 
use an dummy GCPAD environment on my x86 box)...

I've got some questions :
	- In the GCLib, the driver reads gamepad status into the mapped memory, 
but is there an IRQ sent by the controller to know when its status 
changes ? I ask for this because the standard input layer into the Linux 
kernel is not really done to be used with devices that make an active 
wait loop for data (waste of CPU time) !

	- I didn't see informations about the Serial Interface. Have you got some 
(maybe it could help me to make a better GCPad driver) ?

Regards, Free The Cube.

PS : Last year, i also made an 'user-land' driver that converts joystick 
events into mouse events, so you can use a GCPad as a pointer/mouse. It 
works with XFree86 and GPM, but not with DirectFB (I could make a 
kernel-space version to work with). It can emulate PS/2 and IMPS/2 
protocols (and soon EXPS/2), and joystick keys can be assigned. 
http://freshmeat.net/projects/js2mouse/
We can imagine to use a virtual keyboard such like 
http://freshmeat.net/projects/xvkbd/ or xkbd (i don't know the URL).

PS2 : I don't if you are interested by a french translation of some docs 
: http://free.the.cube.free.fr

Re: [Gc-linux-devel] GCPad driver + mouse emulation.

[Richard E. <ric...@br...>]

Hello there!

> - I didn't see informations about the Serial Interface. Have you got some
> (maybe it could help me to make a better GCPad driver) ?

I'm not an expert on the subject, but as far as I know the only
documentation on the serial interface
is found in US patent 6,609,977. If you look at the patent you will find the
following line:

"Serial interface provides a serial interface to hand controllers or other
serial devices using automatic
controller polling and bulk data mode including a light gun interface."

If you need more info about the registers, then take a look at the patent.
The entire 0xcc006400 register
range is covered there. Take a close look on the SI Communication Control
Status Register (Offset + 0x34).
You will find all interrupt related stuff there. It is possible to get an
interrupt when a "pad-poll" has completed,
but you still need to start the transfer somewhere (Writing a '1' to the
Control Status Register bit 0.) Remember also
to set bit 27 of the register to enable the TC (Transfer Complete)
interrupt.

Good luck!


Richard Eng