> Can you (someone?) clarify which wheels do not have a command to switch > into 'native mode' (which causes a USB ID change) and do these wheels use > a unified brake/acc.? > Do any wheels have a 'native mode' which stay with the generic USB ID? To my knowledge all wheels except original Driving Force and Formula Force have the fallback and native mode. Every Logitech wheel in fallback mode reports PID 0x294 which is the PID of the original Driving Force wheel. If DFP/G25/G27/DFGT receives specific command, it simulates reconnect and reports its "real" PID upon reconnection. > Wouldn't the device descriptor only be re-written for the new USB ID's in > 'native' mode. DF/DFP/FEX hides the separate throttle and brake axes in the original descriptor so we definitely need to replace it. G25/27 don't need such a hack, I don't know how about DFGT or Momo, I'll try to find that out. IMHO we need to replace the descriptor only if the wheel has PID 0x294 and is either DF or FEX. DFP has PID 0x298 and needs a fixed descriptor too. > If we force the 'native command' to be issued then we might affect/prevent > any 'old game' play. Problem is that not all wheels actually have the native mode as I mentioned above, but all support separate pedal axes. Unless we somehow read the anonymous fields reported by the original descriptor, I guess we'll have to decide whether to have separate or combined pedal axes. Another (rather hackish) way around this would be a "combined" value in /sys interface. When set to 1, we'd trigger reconnection (can we do that?) and not replace the descriptor (or replace it in case of G25/27). I've given some thought bypassing the ff-memless driver and I don't think it's necessary. We can patch ff-memless and add support for the missing effects. I guess that passing the device-specific commands like effect reset, G27 leds and range setting could be done via /sys interface too. However that's just a thought... Michal -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
