Re: Need Help On Touchscreen dos driver
Posted: Sat Nov 19, 2016 6:57 am
Okay, so thanks to Bret's information and the Linux driver source code, I figured out how to send a control packet to the touch screen. The values in the 8 bytes of that control/setup packet were copied from the Linux driver source code. Once the int14h returns I retrieve a valid transaction handle and closure ID.
Now that I know how to "talk" to it, I need to know how to "listen". I know for sure that the device is supposed to send me back something after this initialization packet is sent (the docs say so). I'll try and figure out how to read what it sends me myself. If you see this message before I post back, don't hesitate to hint me in the right direction.
BTW. I changed my callback prototype to "void far USBCallback (void)", but now even though it doesn't crash any longer when I pull the USB cord out (that's a progress), it doesn't display what it's supposed to do. My one-line callback function currently just raises a global flag, that the program's main loop should catch so as to print something on the screen saying that the callback has been called. Yet nothing happens. An idea why ?
Now that I know how to "talk" to it, I need to know how to "listen". I know for sure that the device is supposed to send me back something after this initialization packet is sent (the docs say so). I'll try and figure out how to read what it sends me myself. If you see this message before I post back, don't hesitate to hint me in the right direction.
BTW. I changed my callback prototype to "void far USBCallback (void)", but now even though it doesn't crash any longer when I pull the USB cord out (that's a progress), it doesn't display what it's supposed to do. My one-line callback function currently just raises a global flag, that the program's main loop should catch so as to print something on the screen saying that the callback has been called. Yet nothing happens. An idea why ?