void CFeatMgrBCEnhancedPlugin::GenericTimerFiredL(
	    MFeatureInfoPluginCallback& aService,
	    FeatureInfoCommand::TFeatureInfoCmd aCommandId,
	    TUint8 aTransId,
	    TInt aRetVal )
	{
    INFO_LOG2( "FeatMgr Corrupt Plugin: GenericTimerFiredL (0x%x, 0x%x)", 
                         aCommandId, aTransId );
    TInt err( KErrNone );
    
    switch ( aCommandId )
    {
    case FeatureInfoCommand::ELoadEnhancedFeatureInfoCmdId:
        {
        // Return some features and KErrNone.
        FeatureInfoCommand::TEnhancedFeatureInfo featureList;
        RFeatureArray features; 
        CleanupClosePushL( features );
        TBitFlags32 flags( 0 );
        flags.Set( EFeatureSupported );
        flags.Set( EFeatureModifiable );
        
        // Adding feature B
        const TInt KBDefaultData( 0x000000bb );
        TFeatureEntry b_entry( TUid::Uid(KFeatureBUid.iUid), flags, KBDefaultData );
        features.AppendL( b_entry );
        
        // Adding feature C
        const TInt KCDefaultData( 0x000000cc );
        TFeatureEntry c_entry( TUid::Uid(KFeatureCUid.iUid), flags, KCDefaultData );
        features.AppendL( c_entry );	

        featureList.iErrorCode = KErrNone;
        featureList.iList = features;
            
        FeatureInfoCommand::TEnhancedFeatureInfoRespPckg resPackage(featureList);
        TRAP(err, aService.ProcessResponseL(aCommandId, aTransId, resPackage));    
        
        CleanupStack::PopAndDestroy( &features );
        break;            
        }
    
    default :
        break;
    }
  
    // TEST CASES END
 
    if ( err != KErrNone )
        {
        ERROR_LOG1( "FeatMgr Plugin: Error in ProcessResponseL: %d", err );
        }
    CFeatMgrBasePlugin::GenericTimerFiredL(aService,aCommandId,aTransId,aRetVal);
    
	}
Exemplo n.º 2
0
/* With ARM and GHS toolsets, the entry point is main() - this will
   allow the linker to generate wrapper code to setup stacks, allocate
   heap area, and initialize and copy code and data segments. For GNU
   toolsets, the entry point is through __start() in the crt0_gnu.asm
   file, and that startup code will setup stacks and data */
int main(void)
{
    return c_entry();
}
Exemplo n.º 3
0
/* With ARM and GHS toolsets, the entry point is main() - this will
   allow the linker to generate wrapper code to setup stacks, allocate
   heap area, and initialize and copy code and data segments. For GNU
   toolsets, the entry point is through __start() in the crt0_gnu.asm
   file, and that startup code will setup stacks and data */
int main(void)
{
    c_entry();
    return 0;
}
Exemplo n.º 4
0
int main()
{
	return c_entry();
}