Jim Davis

Afterthought- Refind might not have crashed, but simply timed-out, while I was pokin-n-hopin...

One last bit o good news to go to sleep on... the McAfee touch test tool also failed on the Toshiba. That is to say, it displayed properly, but did not respond to touch. This is in sharp contrast to the tool's performance on the Acer, where it was accurate and responsive. It did not crash, but also did not recognize any touch, and I had to three-finger-salute to boot. So, I surmise from this that the Toshiba, despite supporting touch in the (meager) firmware setup, and despite its publication of...

Okay, here's a quick report on a difference I found immediately: With the Acer, the Absolute Pointer appears in the device tree (devtree from the EFI shell) and in the list returned by devices. With the Toshiba, those entries are absent. The Toshiba publishes the proper guids, but those guids are lies! Here, by way of illustration, is my Notepad++ search result (through my text captures of EFI shell sessions on each tablet): Search "Pointer" (11 hits in 6 files) J:\PE\EFI\Notes\Acer\dmpstore.txt...

Oops... yeah, well, the Toshiba crashed, so you may want to hold off on that merge... I'll give some more time to this at a later date. But for now, here's an outline of the differences between my two 32-bit tablets. The crashing Toshiba Encore Mini has a screen size of 1024x600, and defaults to landscape mode (from the firmware Setup screen through Windows loading its sensor drivers). The successful Acer Iconia is 1280x800, defaults to portrait. Refind displays properly on both. I invoked the Toshiba...

I just did a quick smoke test of your build, and it worked for me. And, as a bonus, your EDK2 build consumes 38k less than my quick & dirty build from yesterday (GNU-EFI: I see that Rod says that the gnu-efi build is fatter, now I know what he means). I've been testing on an Acer Iconia Tab 8W (which is a Bay Trail chipset). I have another tablet with 32-bit firmware (a Toshiba Encore Mini, also Bay Trail), and I will test on it too, when I get the chance-- but I expect it will behave the same (we'll...

Just a quick follow-up... I built 0.11.2 myself, with one small change, and it works great. The resulting refind_ia32.efi has the touchscreen fully supported, and appears "working as designed", at least, thus far. Of course, my testing is preliminary, and the ramifications of the change are a huge unknown. All I've done is one boot-iteration, using the arrows to move through my choices, selecting the Info choice, backing out by touching the highlighted Return line, and then selecting one of my boot...

The 0.11.2 sources show that the pointer (touchscreen) support is IFDEFed out for 32-bits. This effectively eliminates pointer support for all our goofy 32-bit UEFIs (pronounced Goofie Ufie). This means if you downloaded the current SF binaries (as I did), the included refind_ia32.efi doesn't really have touchscreen support built into it. @CJ: Is this because there's an issue with the code performance/correctness under 32-bits? @The Mighty Quinn: The UEFI setup support for touchscreen is probably...