I've installed the binary prebuild from android 2.3.4-DevKit-2.1, on a beagleboard-xm Rev C. I've made no changes to the images as distributed by TI. I just burned them directly to my flash card.
Some things work, including basic Android on a DVI display, with mouse control.
But, I see no signs of life for the touch input. I tried the 'getevent' command, and the touchscreen event type was not reported, although 3 others were (Microsoft Microsoft Wheel Mouse Optical, gpio-keys, twl4030_pwrbutton).
So, touch input appears inoperable, and leads to few questions . . .
1) Regarding touch control support: I assumed touch control would be enabled (although uncalibrated), since this is a prebuilt binary for the beagleboard-xm, where the touch controller resides. On the other hand, I see no reference to touch in the user guide. So, do I need to enable/install the touch controller support on my own, and if so, what is the procedure for doing so in the prebuilt binary. I'm assuming the procedure outlined in the porting guide does not apply to prebuilt binaries, but maybe that's wrong.
2) Regarding touch control calibration: Once I get past insuring the touch controller is alive, what is the correct/best approach for calibrating touch input? There is a calibration discussion in the porting guide, but that defines the parameters in source code, which presumably requires a source build, or maybe just a runtime module installation. I've also seen references elsewhere to defining the touch calibration in xorg.conf. Which of these approaches (or others?) do I follow, keeping in mind I'm attempting to dodge a source build for now?
3) Regarding beagleboard-xm revisions: The developer guide states that beagleboard-xm revisions through Rev C are supported. So far I've seen no need to specify my revision anywhere, which suggests the differences don't matter to the software, or if they do, that they're handled automatically. Am I correct that I don't need to specify the XM revision anywhere?
Ron