Leappad 2 games used Patch#
Leappad 2 games used free#

The results are prettier than just cat, but still noting happens except with KEY_U and KEY_D (vol+, vol-): Monitoring (as done above) /dev/input/event0 shows nothing at all when I press any key other than volume up (22) and volume down (23).ĮDIT: The 'diagnostic program' is probably evtest? Looks fine: u, d and the direction keys are all there. listed in input.h in the kernel source code.Īfter you press each button on the Leappad, a little jibberish will appear on the screen. These numbers represent the keys up, down, left, right, etc. >cat /sys/devices/platform/gpio-keys/keys (Basically, just mkdir developer in /flags.)Īnyway, when you boot the stock kernel, there is this in the sys filesystem: You don't have to solder anything to a cartridge you can get telnet access to your stock leappad by following the simple steps here: What 'diagnostic program?' I'm pretty sure the problem is at a lower level: the kernel needs to know the board revision so it knows where the GPIOs map to and 0x310 is not on the list.īelow is optional reading if you want more detail on why I think the problem is at a lower level than just reassigning keys.Ĭuriously, OpenLFConnect still works on the latest Manjaro Linux and can be used to enable developer mode (having first restored the leappad back to stock). With the original firmware, pressing any of these buttons causes junk to appear on the screen. I think this means they're not mapped to the right GPIOs. If you cat /dev/input/event0 and press Home and D-pad buttons, nothing happens at all. The D-pad and Home do not generate any keyboard events. Last time I heard from him, he suggested trying out the scancodes in Linux with some kind of a diagnostic program.

Leappad 2 games used free#

(12-27-2019, 04:01 AM)Jabberwock Wrote: Unfortunately, the creator of retroleap has not been active for a long time, as I understand, his free time is rather limited. Maybe someone who knows about this hardware can help?

Spi_lcd_init: spi_channel: 1, gpio_port:2, gpio_pin:3, lcd: GiantPlus-1, type: 2Īnd the 2 buttons work. Okay, maybe only 125 since the screen is using one: Unfortunately, it looks like there are 128 possibile values:Ĭat /sys/devices/virtual/gpio/gpiochip2048/ngpio I tried a few guesses based on the current values (see lines 23167 - 23324 of leapstergs_2.6.37.patch), but no new buttons were enabled. The values for the volume buttons must be right, since they are working: That's kind of sad, because all that is needed to get the d-pad working is to correctly define these variables in the patch: I posted an issue to the retroleap github, but I think the project has died. However, it is close: if you change one of these lines below to end in 0x310 in leapstergs_2.6.37.patch and recompile the kernel, the screen works properly and the volume (A,B) buttons work but the d-pad buttons and home are still dead. I hoped it might be the same as Valenica 0x205, 0x206, or 0x207, but it is not.

Leappad 2 games used Patch#

The retroleap patch to the kernel knows nothing about this board. The problem is board revision 0x310 GPIOs are not the same as the other models. I bought one on eBay just to try out retroleap and it does not work. Unfortunately, retroleap only works on certain Leappad2 models.