Re: [Gc-linux-devel] Successful boot via Max Drive Pro; keyboard not working

[Steven L. <st...@kr...>]

The detection code "says" what kind of controller is on what port. When you
"hardcode" it, if will always say there is a keyboard at port 4, no matter
what.

The code reading the controllers status (buttons, sticks, ...) looks at the
variables set by the detection code. When the detection code said there is
a keyboard at port 4 (which was hardcoded), it reads the port as a keyboard.

So, you're basically right, the keyboard driver doesnt work properly.

However, either way, your keyboard converter doesn't work like the Datel
keyboard converter, or the detection code is incomplete, leaving the keyboard in
an "unfinished" state, rendering it useless.

Steven Looman


On Sun, Feb 06, 2005 at 11:13:18PM +0000, Daniel Thompson wrote:
> On Sun, 2005-02-06 at 23:11 +0100, Steven Looman wrote:
> > The detection code is, for the keyboard, far from perfect. I was not able to
> > finalize/improve the detection code since I had no sources (documents, ...) to
> > look at. Isobel put an option into the kernel to "hardcode" the keyboard at a port.
> 
> Does the fact that the kernel announced it had a keyboard in port 4
> (which is where it was) show the detection code worked but the keyboard
> driver didn't or is it likely to be more complex than that?
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Gc-linux-devel mailing list
> Gc-...@li...
> https://lists.sourceforge.net/lists/listinfo/gc-linux-devel
>