Dne 13.5.2017 v 08:40 Petr Cvek napsal(a):
> The second problem seems to be a same problem. When playing/encoding the data
> from the sensor (with or without previous fix) and calling (probably)
> anything on v4l2 the drivers stops in a same way. I discovered it by trying
> to use the
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Sun May 14 05:00:22 CEST 2017
media-tree git hash:3622d3e77ecef090b5111e3c5423313f11711dfa
media_build
Fix some unneeded exported symbols by marking them as static.
This was found with the 'sparse' tool.
Signed-off-by: Juan Antonio Pedreira Martos
---
.../media/atomisp/platform/intel-mid/atomisp_gmin_platform.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
With gcc-7.1.1 I was getting the following compile error:
error: ‘*’ in boolean context, suggest ‘&&’ instead
The problem is the definition of CEIL_DIV:
#define CEIL_DIV(a, b) ((b) ? ((a) + (b) - 1) / (b) : 0)
Which when called as: CEIL_DIV(x, y * z) triggers this error, note
we cannot
Hi!
> > > Nevertheless, V4L2_CID_FOCUS_ABSOLUTE
> > > is documented as follows (emphasis mine):
> > >
> > > This control sets the *focal point* of the camera to the specified
> > > position. The unit is undefined. Positive values set the focus
> > > closer to the camera, negative values
Dne 2.5.2017 v 16:57 Robert Jarzmik napsal(a):
> Petr Cvek writes:
>
>> Dne 1.5.2017 v 06:20 Petr Cvek napsal(a):
>>> This patchset is just a grouping of a few bugfixes I've found during
>>> the ov9640 sensor support re-adding.
>>
>> P.S. I've manually calculated every format