One of the causes of slow running of the wince system-check oeminterrupthandler for unexpected interruptions (by gooogleman)

Author: gooogleman 10:20:42

One of the causes for the slow running of the wince system-check oeminterrupthandler for unexpected interruptions

This method has been used for a long time, but has never been used to write a blog. Now someone asks me why his machine clock speed is normal, but the machine is slow, I told him to go to the oeminterrupthandle function to print the physical interrupt and check whether there was any unexpected interruption.

For example, in C:/wince500/platform/smdk2440a/src/common/intr

// Get pending interrupt (s)
IRQ = inreg32 (& g_pintrregs-> effecffset );

In this way, you can read the physical interrupt, print it out, and then you can know what the interrupt is. Hey, it's good. Very useful. It is the same in Microsoft's wince and mobile. I went to work and didn't have that much time to writeArticle.