12-26-2019, 08:55 AM
(This post was last modified: 12-26-2019, 08:57 AM by ceratophyllum.)
Unfortunately, retroleap only works on certain Leappad2 models.
I bought one on eBay just to try out retroleap and it does not work. The problem is board revision 0x310 GPIOs are not the same as the other models. The retroleap patch to the kernel knows nothing about this board.
I hoped it might be the same as Valenica 0x205, 0x206, or 0x207, but it is not. 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.
#define LF2000_BOARD_VALENCIA 0x206
#define LF2000_BOARD_VALENCIA_EP 0x207
#define LF2000_BOARD_VALENCIA_FEP 0x208
I posted an issue to the retroleap github, but I think the project has died. 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:
gpio_map[DPAD_LEFT] = ????????????
gpio_map[DPAD_RIGHT] = ????????????
gpio_map[DPAD_DOWN] = ????????????
gpio_map [DPAD_UP]= ????????????
gpio_map [BUTTON_HOME]= ????????????
The values for the volume buttons must be right, since they are working:
gpio_map[BUTTON_VOLUMEDOWN] = LF2000_GPIO_PORT_A | 13;
gpio_map[BUTTON_VOLUMEUP] = LF2000_GPIO_PORT_A | 14;
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. Unfortunately, it looks like there are 128 possibile values:
cat /sys/devices/virtual/gpio/gpiochip2048/ngpio
128
Okay, maybe only 125 since the screen is using one:
spi_lcd_init: spi_channel: 1, gpio_port:2, gpio_pin:3, lcd: GiantPlus-1, type: 2
and the 2 buttons work. Still, too many to guess. (Recompiling takes a while on my system)
Maybe someone who knows about this hardware can help?
I bought one on eBay just to try out retroleap and it does not work. The problem is board revision 0x310 GPIOs are not the same as the other models. The retroleap patch to the kernel knows nothing about this board.
I hoped it might be the same as Valenica 0x205, 0x206, or 0x207, but it is not. 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.
#define LF2000_BOARD_VALENCIA 0x206
#define LF2000_BOARD_VALENCIA_EP 0x207
#define LF2000_BOARD_VALENCIA_FEP 0x208
I posted an issue to the retroleap github, but I think the project has died. 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:
gpio_map[DPAD_LEFT] = ????????????
gpio_map[DPAD_RIGHT] = ????????????
gpio_map[DPAD_DOWN] = ????????????
gpio_map [DPAD_UP]= ????????????
gpio_map [BUTTON_HOME]= ????????????
The values for the volume buttons must be right, since they are working:
gpio_map[BUTTON_VOLUMEDOWN] = LF2000_GPIO_PORT_A | 13;
gpio_map[BUTTON_VOLUMEUP] = LF2000_GPIO_PORT_A | 14;
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. Unfortunately, it looks like there are 128 possibile values:
cat /sys/devices/virtual/gpio/gpiochip2048/ngpio
128
Okay, maybe only 125 since the screen is using one:
spi_lcd_init: spi_channel: 1, gpio_port:2, gpio_pin:3, lcd: GiantPlus-1, type: 2
and the 2 buttons work. Still, too many to guess. (Recompiling takes a while on my system)
Maybe someone who knows about this hardware can help?