No - nothing specific to an implementation should go in the frameworks projects. As an example, the ALSA implementation of AudioHardwareInterface is in a separate repo.
On Dec 2, 5:30 pm, jyukon <[EMAIL PROTECTED]> wrote: > Hi, > > I've already implement a CameraHardwareInterface for UVC camera using > V4L2 I/F. Is frameworks/base/camera/libcameraservice the right place > for putting them when I upload them? > > -Jyunji > > On 12月3日, 午前9:29, Dave Sparks <[EMAIL PROTECTED]> wrote: > > > 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 -~----------~----~----~----~------~----~------~--~---
