mfw/ti1_key.c: properly initialize notified_keys array The code in this ti1_key.c layer needs to call kpd_subscribe() and kpd_define_key_notification() functions in order to register with the KPD driver. The original code passed KPD_NB_PHYSICAL_KEYS in nb_notified_keys - this constant is defined to 24 in kpd_cfg.h on all platforms of interest to us - but it only filled the first 23 slots in the notified_keys array, resulting in stack garbage being passed to KPD API functions. The fix consists of initializing the last missed array slot to KPD_KEY_RECORD, the key ID for the right side button on the D-Sample handset. On our current hw targets this "Record" button exists as the EXTRA button on our Luna keypad board and as the camera button on the Pirelli DP-L10. There is no support whatsoever for this button in current BMI+MFW, we have no plans of doing anything with Pirelli's camera button even if we do get our UI fw running on that phone, and the Mother's dream of building our own FreeCalypso handset with the same button arrangement as D-Sample (including the right side button) is currently very nebulous - but let us nonetheless handle the full set of buttons on the KPD to MFW interface, and let upper layers weed out unsupported buttons.

/**
 * @file	xxx_state_i.h
 * 
 * Internal definitions for XXX state machine, 
 * i.e. the states and the functions corresponding to the states.
 *
 * The messages are declared in xxx_message.h, since they can 
 * be seen from outside.
 *
 * @author	Your name here (your_email_here)
 * @version 0.1
 */

/*
 * History:
 *
 *	Date       	Author					Modification
 *	-------------------------------------------------------------------
 *	//							Create.
 *
 * (C) Copyright 2001 by Texas Instruments Incorporated, All Rights Reserved
 */

#ifndef __XXX_STATE_I_H_
#define __XXX_STATE_I_H_


#include "rv/rv_general.h"


/**
 * XXX states.
 *
 * XXX instance is a state machine with several possible states.
 * Based on the current state, XXX handle different kind of messages/events.
 * States are listed in the order they should normally be sequenced.
 *
 * See the Readme file for a description of the state machine.
 */
typedef enum
{
	XXX_STATE_1,
	XXX_STATE_2
} T_XXX_INTERNAL_STATE;


/*
 * Optional but	recommanded, define a function for the processing
 * in each state, like:
 *   T_XXX_RETURN xxx_state_1					(T_RV_HDR * message_p);
 *   T_XXX_RETURN xxx_state_2					(T_RV_HDR * message_p);
 */

#endif /* __XXX_STATE_I_H_ */