Abstract: Program code loaded for execution by a computer can be dynamically instrumented to collect event data by inserting an instruction at a trace point within the program code as loaded in a memory space of a computer, where the trace point corresponds to the beginning of a predefined function of the program selected for event tracing. The instruction provides for the direction of the execution of said computer to a function proxy routine, which includes a call to an instance of the predefined function. Event data is collected in connection with the calling of the instance of the predefined function.

Abstract: A content and collaborative filtering system for recommending entertainment oriented content items, such as music and video, and other media content items to a user based on similarity in profile between the user and other users and between the content indexed in the user's profile and other content in the database. The system stores implicit and explicit ratings data for such content items provided by the users. Upon request of the user, the system accesses the user's profile and corresponding content interests database. The system uses the relationships between the content items to determine a subset of the content items to be referred to the user. The system also correlates a similarity between the user's ratings of the content items and other users' ratings. Based on the correlations, a subset of users is selected that is then used to provide recommendations to the user. The recommended items have a high probability of being subjectively appreciated by the user.

Abstract: A device driver architecture that couples an operating system to a computer interface of a controller device that includes a plurality of functional sub-elements. The device driver includes a plurality of operating system interface objects each presenting an operating system interface (OSI) to the operating system, a plurality of computer interface objects each providing for the generation of programming values to be applied to the computer interface to establish the operating mode of a respective predetermined sub-element of the controller device, and a device driver library of processing routines callable by each of the plurality of operating system interface objects to process data and generate calls to the plurality of computer interface objects in predetermined combinations. The device driver library enables the selection of an execution contexts within which to define the generation and application of the programming values to the computer interface.

Abstract: A device driver architecture that couples an operating system to a computer interface of a controller device that includes a plurality of functional sub-elements. The device driver includes a plurality of operating system interface objects each presenting an operating system interface (OSI) to the operating system, a plurality of computer interface objects each providing for the generation of programming values to be applied to the computer interface to establish the operating mode of a respective predetermined sub-element of the controller device, and a device driver library of processing routines callable by each of the plurality of operating system interface objects to process data and generate calls to the plurality of computer interface objects in predetermined combinations. The device driver library enables the selection of an execution contexts within which to define the generation and application of the programming values to the computer interface.

Abstract: A system is disclosed that includes a first processor, which in some embodiments includes a DSP, and a first memory pool and a second memory pool. The second memory pool is primarily associated with the DSP and stores code that is available for execution by the DSP. A plurality of code modules are stored in the first memory pool, which in some embodiments is associated with a second processor. The code modules are individually and dynamically swapped into the first memory pool, which in some embodiments is not large enough to simultaneously store all of the code modules. In some instances, the dynamic code module swapping is done at the direction of a second processor, which is aware of the state of the DSP execution. In other instances, the dynamic code module swapping is done at the direction of the DSP. In each instance, dynamic code swapping is performed in a manner that minimizes or eliminates any halts in DSP instruction execution.