gc-linux-devel

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

[Daniel T. <gc-...@re...>]

Hi Folks

First, a bit of news:

Linux boots successfully when loaded via the Max Drive Pro. Datel
finally got round to releasing their gizmo (I got mine about a week ago)
and almost the first time I tried it the kernel booted, found my NFS
server and made it to the Debian login prompt on my UK (PAL) 'Cube.

Second, a bit of a problem:

I have a (very cheap) keyboard adaptor I bought on Lik-sang at the same
time I bought my BBA. It is a two-in-one device that can either connect
a PS/2 keyboard or a Playstation controller. The kernel correctly
identified the peripherals in the boot messages (2 controllers, unused,
keyboard) but unfortunately the keyboard just didn't seem to work
(though caps lock and num lock lights do come on and off when I press
those buttons).

So a variety of crack-pot questions:

 - has anyone had their Lik-sang 2-in-1 adaptor work on gc-linux?
   (and in what socket)

 - has anyone had their keyboard work after booting via a Max drive?
   (a long shot given how rare those things are)

 - does anyone know of any bare machine .dol programs that use the
   keyboard so I might be able to prove the hardware does work?

 - could someone with a keyboard and SDLoad unplug their BBA and
   let me know if <Shift-PgUp> gets the kernel to scroll up from the
   'Looking for RPC ... messages'? (I want to debug the keyboard thing
   before laying a network cable down to the living room so I'd like to
   know how to tell when I've got it working!)

Unless someone has a better suggestion I guess I need to go and add lots
of printk's to the keyboard driver (and any lower-level drivers) to
figure out what might have gone wrong.

-- 
Daniel Thompson <gc-...@re...>

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

[Rob R. <ro...@re...>]

I know I got to that problem a while ago at the 21C3. My keyboard
adaptor (actually mist's) was not recognised. Mist told me it had worked
when the SI driver was still hardcoded to accept a keyboard at some
port, but it didn't work any more. I don't think I have time to check it
out this week. The fact that the num and caps lights work does not need
to mean anything, don't know if they are controlled by the kernel or the
hardware.

Rob

-----Oorspronkelijk bericht-----
Van: gc-...@li...
[mailto:gc-...@li...] Namens Daniel
Thompson
Verzonden: zondag 6 februari 2005 18:50
Aan: gc-...@li...
Onderwerp: [Gc-linux-devel] Successful boot via Max Drive Pro; keyboard
not working

Hi Folks

First, a bit of news:

Linux boots successfully when loaded via the Max Drive Pro. Datel
finally got round to releasing their gizmo (I got mine about a week ago)
and almost the first time I tried it the kernel booted, found my NFS
server and made it to the Debian login prompt on my UK (PAL) 'Cube.

Second, a bit of a problem:

I have a (very cheap) keyboard adaptor I bought on Lik-sang at the same
time I bought my BBA. It is a two-in-one device that can either connect
a PS/2 keyboard or a Playstation controller. The kernel correctly
identified the peripherals in the boot messages (2 controllers, unused,
keyboard) but unfortunately the keyboard just didn't seem to work
(though caps lock and num lock lights do come on and off when I press
those buttons).

So a variety of crack-pot questions:

 - has anyone had their Lik-sang 2-in-1 adaptor work on gc-linux?
   (and in what socket)

 - has anyone had their keyboard work after booting via a Max drive?
   (a long shot given how rare those things are)

 - does anyone know of any bare machine .dol programs that use the
   keyboard so I might be able to prove the hardware does work?

 - could someone with a keyboard and SDLoad unplug their BBA and
   let me know if <Shift-PgUp> gets the kernel to scroll up from the
   'Looking for RPC ... messages'? (I want to debug the keyboard thing
   before laying a network cable down to the living room so I'd like to
   know how to tell when I've got it working!)

Unless someone has a better suggestion I guess I need to go and add lots
of printk's to the keyboard driver (and any lower-level drivers) to
figure out what might have gone wrong.

-- 
Daniel Thompson <gc-...@re...>



-------------------------------------------------------
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

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

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

Hi,

First of all, I wrote the SI driver for gc-linux (altho most of the credit has to
go to groupaz since he wrote/hacked the detection code).

While writing this driver I only had access to a Datel adapter (+ keyboard) and
a few standard controllers; I was not able to test this.

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.

Numlock/capslock/scrolllock don't mean anything. They aren't handled by the
kernel like in a normal computer, but just light up when you press then. No
signal is received by the SI hardware in the cube, as far as I know.

If you have the time/resources to improve the driver, please do so!

Steven Looman

On Sun, Feb 06, 2005 at 09:03:08PM +0100, Rob Reilink wrote:
> I know I got to that problem a while ago at the 21C3. My keyboard
> adaptor (actually mist's) was not recognised. Mist told me it had worked
> when the SI driver was still hardcoded to accept a keyboard at some
> port, but it didn't work any more. I don't think I have time to check it
> out this week. The fact that the num and caps lights work does not need
> to mean anything, don't know if they are controlled by the kernel or the
> hardware.
> 
> Rob
> 
> -----Oorspronkelijk bericht-----
> Van: gc-...@li...
> [mailto:gc-...@li...] Namens Daniel
> Thompson
> Verzonden: zondag 6 februari 2005 18:50
> Aan: gc-...@li...
> Onderwerp: [Gc-linux-devel] Successful boot via Max Drive Pro; keyboard
> not working
> 
> Hi Folks
> 
> First, a bit of news:
> 
> Linux boots successfully when loaded via the Max Drive Pro. Datel
> finally got round to releasing their gizmo (I got mine about a week ago)
> and almost the first time I tried it the kernel booted, found my NFS
> server and made it to the Debian login prompt on my UK (PAL) 'Cube.
> 
> Second, a bit of a problem:
> 
> I have a (very cheap) keyboard adaptor I bought on Lik-sang at the same
> time I bought my BBA. It is a two-in-one device that can either connect
> a PS/2 keyboard or a Playstation controller. The kernel correctly
> identified the peripherals in the boot messages (2 controllers, unused,
> keyboard) but unfortunately the keyboard just didn't seem to work
> (though caps lock and num lock lights do come on and off when I press
> those buttons).
> 
> So a variety of crack-pot questions:
> 
>  - has anyone had their Lik-sang 2-in-1 adaptor work on gc-linux?
>    (and in what socket)
> 
>  - has anyone had their keyboard work after booting via a Max drive?
>    (a long shot given how rare those things are)
> 
>  - does anyone know of any bare machine .dol programs that use the
>    keyboard so I might be able to prove the hardware does work?
> 
>  - could someone with a keyboard and SDLoad unplug their BBA and
>    let me know if <Shift-PgUp> gets the kernel to scroll up from the
>    'Looking for RPC ... messages'? (I want to debug the keyboard thing
>    before laying a network cable down to the living room so I'd like to
>    know how to tell when I've got it working!)
> 
> Unless someone has a better suggestion I guess I need to go and add lots
> of printk's to the keyboard driver (and any lower-level drivers) to
> figure out what might have gone wrong.
> 
> -- 
> Daniel Thompson <gc-...@re...>
> 
> 
> 
> -------------------------------------------------------
> 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
> 
> 
> 
> -------------------------------------------------------
> 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
> 

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

[Daniel T. <gc-...@re...>]

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?

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
>