git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1819 bbd45198-f89e-11dd-88c7-29a3b14d5316

1. Move file, "start_gcc.S", from "libcpu/arm/cortex-m3/" to "bsp/efm32/" 
2. Upgrade EFM32 driver libraries (CMSIS and efm32lib) to version 2.2.2 
3. Upgrade EFM32 G2xx development kit drivers (EFM32_Gxxx_DK) to version 1.7.2 (from version 1.6.0) 
4. Modify the files ("drv_usart.c" and "drv_iic.c") according to the driver libraries upgrading 

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1818 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1817 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1816 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1815 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1814 bbd45198-f89e-11dd-88c7-29a3b14d5316

There is notebook demo but somehow the workbench didn't show it...

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1813 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1812 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1811 bbd45198-f89e-11dd-88c7-29a3b14d5316

Suppress the warning "Lines ending with an invalid line end have been detected in file ...\rtgui_object.h" by convert the whole file to unix eol.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1810 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1809 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1808 bbd45198-f89e-11dd-88c7-29a3b14d5316

The old code won't detach ack_mb if error occurs. Fix it.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1807 bbd45198-f89e-11dd-88c7-29a3b14d5316

Use rtgui_*_t instead of struct rtgui_*

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1806 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1805 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1804 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1803 bbd45198-f89e-11dd-88c7-29a3b14d5316

overlapFunc will return RTGUI_REGION_STATUS_FAILURE in some
circumstance(OOM etc), check it and return error if any thing goes
wrong. It prevents garbage values crashing the system.

Please ignore the eol diff noise.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1802 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1798 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1797 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1796 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1795 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1794 bbd45198-f89e-11dd-88c7-29a3b14d5316

That commit broke bsp/stm3210x. The cause is that we calls rtgui_system_init in rtgui_startup. But the calibration starts before rtgui_startup and rtgui_system_init. This lead to crash.

One way to deal with it is move rtgui_system_init out of rtgui_startup and call it manually. But it will affect other bsps. So just revert the "bad" commit.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1793 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1792 bbd45198-f89e-11dd-88c7-29a3b14d5316

If we do not calibrate the touch screen, GUI is unusable. This patch use a semaphore to block GUI thread until calibration finish.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1791 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1790 bbd45198-f89e-11dd-88c7-29a3b14d5316

Check whether finger is still on the screen. If not, we couldn't determine where the user has touched. It's better to return early rather than give garbage values.

A more sensitive solution might be caculate the position once the interrupt occured. But it's not anti-shake friendly.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1789 bbd45198-f89e-11dd-88c7-29a3b14d5316

Rename flag to touched_down.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1788 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1787 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1786 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1785 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1784 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1783 bbd45198-f89e-11dd-88c7-29a3b14d5316

The old code only checks touch->max_x > touch->min_x but not touch->max_x == touch->min_x. Thus may lead to divided by zero error.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1782 bbd45198-f89e-11dd-88c7-29a3b14d5316

The old code forgot to drop the MSB in the very first byte retrieved from ads7843 after a control byte. This will lead to data corruption especially in 16-Clocks per conversion mode.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1781 bbd45198-f89e-11dd-88c7-29a3b14d5316

use RT_USING_FINSH micro to decide whether to compile FINSH functions or not.

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1780 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1779 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1778 bbd45198-f89e-11dd-88c7-29a3b14d5316

git-svn-id: https://rt-thread.googlecode.com/svn/trunk@1777 bbd45198-f89e-11dd-88c7-29a3b14d5316