The camera service ended up there because of a dependency on SurfaceFlinger. However, the camera service is not supposed to be hardware dependent.
The generic camera implementation creates fake YUV preview frames and passes back a canned JPEG for the image capture. You'll need to implement your own version of CameraHardwareInterface to bring up your camera hardware. On Dec 2, 10:59 am, MohanParthasarathy <[EMAIL PROTECTED]> wrote: > Hi, > > Under hardware/libhardware, i can see that most of the user space HAL > drivers are maintained. Why is that Camera is in a different place > frameworks/base/camera ? > > Also, can someone tell me whether the drivers provided under > libhardware and ril can work without any changes if i have the right > drivers in the kernel ? > > thanks > -mohan --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
