Remove some debug output that was accidentally left in a preceding commit
Use usleep instead of usdelay as CONFIG_BOARD_LOOPSPERMSEC might not be calibrated correctly and CC3000 is fine with longer wait.

Signed-off-by: Jussi Kivilinna <jussi.kivilinna@haltian.com>
This commit is a set of patches 02/11 through 03/11 correcting issues with the CC3000 networking (01/11 was committed separated).  Among these 10 patches:

03/11: CC3000 driver was getting stuck at recv() when remote host closed connection and application tried to read data from remotely shutdown socket. This patch adds proper handling for remotely closed socket event.

07/11: Socket state initialization was done in 'register', while it should be initialized in 'open' and deinitialized in 'close'. Old way caused problems when device is closed, power-cycled and then reopened as old socket state was left enabled.

08/11: Select thread was getting stuck after 'close, power-cycle, reopen', since selectsem was not properly setup and cleaned up.

09/11 'maxFD' was not properly reset in select worker and not checked for before calling cc3000_select().

10/11: After wlan_stop()/cc3000_close(), irqsem was left with count '-1'. Therefore on next wlan_start()/cc3000_open(), initial value for irqsem was wrong. Additional repeated wlan_start()/wlan_stop() decreased irqsem value further. Obviously this causes driver not to function correctly and freeze.

Patch moves initialization and destruction of waitsem, irqsem and readysem to cc3000_open/cc3000_close.

All are: Signed-off-by: Jussi Kivilinna <jussi.kivilinna@haltian.com>
Update ChangeLog
cctype: Undefined macros defined ctype.h so that builtin C++ implementations will be used
Update ChangeLog
Cosmetic change to comment
Fix missing quote in Kconfig
Refresh configuration
Fix typo
STM3240G-EVAL:  Rename files for compatibility with current naming conventions
STM3210E-EVAL:  Rename files for compatibility with current standards
Refresh configuration
Fix one warning.  There are a couple of others that look like real problems
STM3210E-EVAL:  Don't treat joystick as buttons if the DJOYSTICK driver is enabled
STM3210E-EVAL:  Add a DJoystick driver
Update ChangeLog
apps/examples/djoystick:  Add a test of the discreate joystick driver
DJoystick:  Add a new ioctl to get the support joystick discrete signals
STM3210E-EVAL:  Add missing initialization for the joystick driver