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 o
Thanks. I noticed that audio HAL is in audioflinger. I am assuming that this
also can run on top of ALSA and hence can be considered hardware
independent. Is that how it is decided whether something goes under hardware
or not ..
Also, how does one hook up the 2D and 3D hardware acceleration. I saw
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 d
That's correct - anything in frameworks projects should be considered
hardware independent.
Unfortunately, SurfaceFlinger is one of the areas that isn't as
hardware-independent as we would like it to be. Expect to see
improvements in this area in the future. I'm not the graphics expert,
but hopef
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 u
