Quote:
Originally Posted by tshering
Maybe this is related to the following:
The relevant part is |
OK, I copy/pasted that code into rcS (only on my PC; I haven't pushed that change to GitHub yet since I've been experimenting a bit and need to clean up my tree first) but unless I'm missing something else to do (which I could be), I still couldn't get the touch driver bundled in the Feb2019 vlasovsoft pbchess package to work with my GloHD (nor would any of the other drivers work with it either). I don't have access to any other devices to determine if things work properly with that set on other devices as well or if it's only my device that's weird.
The only other difference I can think of is that I do use the KSM Bouncer functionality since I like forcing people to enter a password on boot. It could be the newer touch driver isn't loaded by then, but things work properly with the older driver so I'm not sure that's it. Unless order matters in the rcS file; I just realized I put that section after the mouse driver part so putting it before that section could be one last thing I could try.
Anyway, other than that and/or bundling that older version of the driver (either replacing the one that exists in the Feb2019 pbchess package, or as a standalone adding a special case just for GloHD to load the older driver if the newer one still works with other Mark 6 and older devices), I'm out of ideas.
Other than figuring out the backwards compatible part with older firmwares (although if you're using a Mark 7 device, I wonder why anyone would want to use an older firmware version, especially if that device is a Forma or Libra since the newer firmwares fix major bugs and the older version of KSM09 works fine on older devices for both new and old firmwares so unfortunately that part is not really a high priority/on my personal motivated interest list to figure out), I think the only thing left to do is figure out how much of update002 is left that is still relevant to migrate over (which I think mostly has to do with usbnet if I'm reading things right) since a good chunk of it seems to have already made it over in later versions of KSM09. After that, it might be worthwhile to try creating a unified KSM09 2019-12 or 2020-01 update roll-up (maybe targeting 4.18/4.19 devices just to make support easier).