CameraUvc Class Reference
Inheritance diagram for CameraUvc:
Collaboration diagram for CameraUvc:

List of all members.

Public Member Functions

 CameraUvc (ConfigFile *cf, int section)
int MainSetup ()
 Sets up the resources needed by the driver thread.
void MainQuit ()
 Cleanup method for driver thread (called when main exits)
int ProcessMessage (QueuePointer &resp_queue, player_msghdr *hdr, void *data)
 Message handler.

Private Member Functions

virtual void Main ()
 Main method for driver thread.

Private Attributes

player_camera_data_t data

Member Function Documentation

void CameraUvc::Main ( ) [private, virtual]

Main method for driver thread.

drivers have their own thread of execution, created using StartThread(); this is the entry point for the driver thread, and must be overloaded by all threaded drivers.

Implements ThreadedDriver.

References player_camera_data::bpp, player_camera_data::compression, Driver::device_addr, player_camera_data::fdiv, player_camera_data::format, player_camera_data::height, player_camera_data::image, player_camera_data::image_count, PLAYER_CAMERA_COMPRESS_JPEG, PLAYER_CAMERA_DATA_STATE, PLAYER_CAMERA_FORMAT_RGB888, PLAYER_MSGTYPE_DATA, Driver::ProcessMessages(), Driver::Publish(), and player_camera_data::width.

Here is the call graph for this function:

void CameraUvc::MainQuit ( void  ) [virtual]

Cleanup method for driver thread (called when main exits)

Overload this method and to do additional cleanup when the driver thread exits.

Reimplemented from ThreadedDriver.

int CameraUvc::ProcessMessage ( QueuePointer resp_queue,
player_msghdr hdr,
void *  data 
) [virtual]

Message handler.

This function is called once for each message in the incoming queue. Reimplement it to provide message handling. Return 0 if you handled the message and -1 otherwise

resp_queueThe queue to which any response should go.
hdrThe message header
dataThe message body

Reimplemented from Driver.

The documentation for this class was generated from the following files: