Qtopia is hard to comprehend!

In order to make qtopia support touch level, these two naively exhausted their efforts and thoughts. I have been working for about 20 hours and still have no results. I am depressed, depressed, and extremely depressed! I have read some documents and the process is difficult. I will make a simple summary below:

In Linux, there are two types of touch flat drivers: one is to be located by the application; the other is to write the positioning information to the driver (which seems like this, not quite understandable ). For mizi 2410, the driver is the first type. So how can we make qtopia support touch screen when porting QT/E and qtopia? In my understanding, there are two methods.

First, modify the src/kernel/qwsxx_mouse.cpp file in QT/e ), the specific method is to first add # define customtouch to the file (this file has been annotated above, and you can just comment out), and then modify the program source code, the specific modification method can be found in the article pointer handling in qopia 2.1.1. At the same time, when configuring qtopia, it is best to add # define qws_need_calibration to the specific configuration file of the device. When qtopia is started, it will check whether there is a pointcal file in/etc. If not, the user correction process is generated first, and the correction information is stored in the/etc/pointcal file. Correction is no longer required when the file is started later. If the # define qws_need_calibration configuration is not added, you must correct the qtopia before starting the qtopia (the same algorithm as QT/e must be used) to enable the qtopia ), and generate the/etc/pointcal file. Otherwise, qtopia reports that the file cannot be opened during startup, and thus cannot touch the file.

The second method uses tslib instead of modifying QT/e. Add-tslib When configuring QT/e, and add # define qws_need_calibration When configuring qtopia (if not, you must correct the qtopia before starting the/etc/pointcal file ), in this way, when qtopia is started for the first time, it will call the correction function in QT/E for correction. The QT/e correction function uses the unified interface provided by tslib. So what is the order of compiling files? Because the structure of the touch plane driver is different, tslib encapsulates different touch plane drivers. When using tslib, you only need to write a small plugin according to the plugin example in tslib for your touch plane driver, then compile tslib, and then compile QT/e with the tslib library you compiled, and then compile qtopia.

According to the second method I have summarized, I have done everything well. As a result, due to the NFS of the Board and its poor performance, the connection is always interrupted during qpe execution and it has never been able to run normally. No way, I had to split the flash into 25 MB to form a jffs2 file system. I planned to copy the qtopia file to the Flash file. As a result, there was no jflash tool. I still had to use NFS to copy the file, my God! NFS is still not OK during copy! If you don't want to copy the file to flash, you can try again.

In a rush, I wrote these things in a mess. There may be many incorrect symbols. Let's do this first. Wait until the problem is solved and write a detailed process! God, help me! The problem is about to be solved!