Hi Nikolaus,
On Wed, Jul 05, 2017 at 04:02:04PM +0200, H. Nikolaus Schaller wrote:
> Hi Sakari,
>
> > Am 03.07.2017 um 14:23 schrieb H. Nikolaus Schaller :
> >
> > Hi Hugues,
> >
> >> Am 03.07.2017 um 14:03 schrieb Hugues FRUCHET :
> >>
> >> Hi
Hi Nikolaus,
On Wed, Jul 05, 2017 at 04:02:04PM +0200, H. Nikolaus Schaller wrote:
> Hi Sakari,
>
> > Am 03.07.2017 um 14:23 schrieb H. Nikolaus Schaller :
> >
> > Hi Hugues,
> >
> >> Am 03.07.2017 um 14:03 schrieb Hugues FRUCHET :
> >>
> >> Hi Nikolaus,
> >>
> >> nothing really strange in
Hi Sakari,
> Am 03.07.2017 um 14:23 schrieb H. Nikolaus Schaller :
>
> Hi Hugues,
>
>> Am 03.07.2017 um 14:03 schrieb Hugues FRUCHET :
>>
>> Hi Nikolaus,
>>
>> nothing really strange in trace, I wanted to check the latest S_FMT and
>> it is well
Hi Sakari,
> Am 03.07.2017 um 14:23 schrieb H. Nikolaus Schaller :
>
> Hi Hugues,
>
>> Am 03.07.2017 um 14:03 schrieb Hugues FRUCHET :
>>
>> Hi Nikolaus,
>>
>> nothing really strange in trace, I wanted to check the latest S_FMT and
>> it is well 1280x1024 YUV:
[ 425.579498] video2:
Hi Hugues,
> Am 03.07.2017 um 14:03 schrieb Hugues FRUCHET :
>
> Hi Nikolaus,
>
> nothing really strange in trace, I wanted to check the latest S_FMT and
> it is well 1280x1024 YUV:
>>> [ 425.579498] video2: VIDIOC_S_FMT: type=vid-cap, width=1280,
> height=1024,
Hi Hugues,
> Am 03.07.2017 um 14:03 schrieb Hugues FRUCHET :
>
> Hi Nikolaus,
>
> nothing really strange in trace, I wanted to check the latest S_FMT and
> it is well 1280x1024 YUV:
>>> [ 425.579498] video2: VIDIOC_S_FMT: type=vid-cap, width=1280,
> height=1024, pixelformat=UYVY, field=none,
Hi Nikolaus,
nothing really strange in trace, I wanted to check the latest S_FMT and
it is well 1280x1024 YUV:
>> [ 425.579498] video2: VIDIOC_S_FMT: type=vid-cap, width=1280,
height=1024, pixelformat=UYVY, field=none, bytesperline=2560,
sizeimage=2621440, colorspace=0, flags=0x0,
Hi Nikolaus,
nothing really strange in trace, I wanted to check the latest S_FMT and
it is well 1280x1024 YUV:
>> [ 425.579498] video2: VIDIOC_S_FMT: type=vid-cap, width=1280,
height=1024, pixelformat=UYVY, field=none, bytesperline=2560,
sizeimage=2621440, colorspace=0, flags=0x0,
Hi Hugues,
> Am 03.07.2017 um 10:16 schrieb Hugues FRUCHET :
>
> Hi Nikolaus,
> Could you enable V4L2 UAPI traces ? Something like:
> echo 0xFF > /sys/devices/platform/soc/. name>/video4linux/video2/dev_debug
>
> you will see then in kernel dmesg the V4L2 calls and their
Hi Hugues,
> Am 03.07.2017 um 10:16 schrieb Hugues FRUCHET :
>
> Hi Nikolaus,
> Could you enable V4L2 UAPI traces ? Something like:
> echo 0xFF > /sys/devices/platform/soc/. name>/video4linux/video2/dev_debug
>
> you will see then in kernel dmesg the V4L2 calls and their
> parameters/return
Hi Nikolaus,
Could you enable V4L2 UAPI traces ? Something like:
echo 0xFF > /sys/devices/platform/soc/./video4linux/video2/dev_debug
you will see then in kernel dmesg the V4L2 calls and their
parameters/return values.
BR,
Hugues.
On 07/01/2017 11:00 PM, H. Nikolaus Schaller wrote:
> Hi,
>
>
Hi Nikolaus,
Could you enable V4L2 UAPI traces ? Something like:
echo 0xFF > /sys/devices/platform/soc/./video4linux/video2/dev_debug
you will see then in kernel dmesg the V4L2 calls and their
parameters/return values.
BR,
Hugues.
On 07/01/2017 11:00 PM, H. Nikolaus Schaller wrote:
> Hi,
>
>
Hi,
Firstly, it turned out that we also must have V4L2_CID_PIXEL_RATE for omap3isp
compatibility
(see
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?=0bc77f3f06fcf2ca7b7fad782d70926cd4d235f1
).
And secondly, I have tried to add some SXGA config and it looks good by
Hi,
Firstly, it turned out that we also must have V4L2_CID_PIXEL_RATE for omap3isp
compatibility
(see
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?=0bc77f3f06fcf2ca7b7fad782d70926cd4d235f1
).
And secondly, I have tried to add some SXGA config and it looks good by
Hi Nikolaus,
I would propose to work first on YUV support, so you can test a YUV VGA
grabbing using your OMPA3 setup, I will add this support then in patch
serie.
For the co-work, let's continue on IRC (irc.freenode.net), chat #v4l, my
pseudo is "hfr".
BR,
Hugues.
On 06/26/2017 06:28 PM, H.
Hi Nikolaus,
I would propose to work first on YUV support, so you can test a YUV VGA
grabbing using your OMPA3 setup, I will add this support then in patch
serie.
For the co-work, let's continue on IRC (irc.freenode.net), chat #v4l, my
pseudo is "hfr".
BR,
Hugues.
On 06/26/2017 06:28 PM, H.
> Am 26.06.2017 um 13:16 schrieb Pavel Machek :
>
> Hi!
>
>>> You may want to try this one:
>>>
>>> commit 0eae9d2a8f096f703cbc8f9a0ab155cd3cc14cef
>>> Author: Pavel
>>> Date: Mon Feb 13 21:26:51 2017 +0100
>>>
>>> omap3isp: fix VP2SDR bit so capture (not
> Am 26.06.2017 um 13:16 schrieb Pavel Machek :
>
> Hi!
>
>>> You may want to try this one:
>>>
>>> commit 0eae9d2a8f096f703cbc8f9a0ab155cd3cc14cef
>>> Author: Pavel
>>> Date: Mon Feb 13 21:26:51 2017 +0100
>>>
>>> omap3isp: fix VP2SDR bit so capture (not preview) works
>>>
>>> This
Nikolaus,
some comments about pixel format/resolution below:
On 06/26/2017 10:39 AM, Pavel Machek wrote:
> On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
>> Hi Pavel,
>>
>>> Am 25.06.2017 um 11:18 schrieb Pavel Machek :
>>>
>>> Hi!
>>>
* unfortunately we still get no
Nikolaus,
some comments about pixel format/resolution below:
On 06/26/2017 10:39 AM, Pavel Machek wrote:
> On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
>> Hi Pavel,
>>
>>> Am 25.06.2017 um 11:18 schrieb Pavel Machek :
>>>
>>> Hi!
>>>
* unfortunately we still get no image :(
Hi!
> > You may want to try this one:
> >
> > commit 0eae9d2a8f096f703cbc8f9a0ab155cd3cc14cef
> > Author: Pavel
> > Date: Mon Feb 13 21:26:51 2017 +0100
> >
> >omap3isp: fix VP2SDR bit so capture (not preview) works
> >
> >This is neccessary for capture (not preview)
Hi!
> > You may want to try this one:
> >
> > commit 0eae9d2a8f096f703cbc8f9a0ab155cd3cc14cef
> > Author: Pavel
> > Date: Mon Feb 13 21:26:51 2017 +0100
> >
> >omap3isp: fix VP2SDR bit so capture (not preview) works
> >
> >This is neccessary for capture (not preview) to work
Hi Nikolaus,
On 06/22/2017 05:41 PM, H. Nikolaus Schaller wrote:
>
>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>
>> This patchset enables OV9655 camera support.
>>
>> OV9655 support has been tested using STM32F4DIS-CAM extension board
>> plugged on connector P1 of
Hi Nikolaus,
On 06/22/2017 05:41 PM, H. Nikolaus Schaller wrote:
>
>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>
>> This patchset enables OV9655 camera support.
>>
>> OV9655 support has been tested using STM32F4DIS-CAM extension board
>> plugged on connector P1 of STM32F746G-DISCO board.
Hi Pavel,
> Am 26.06.2017 um 10:39 schrieb Pavel Machek :
>
> On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
>> Hi Pavel,
>>
>>> Am 25.06.2017 um 11:18 schrieb Pavel Machek :
>>>
>>> Hi!
>>>
* unfortunately we still get no image :(
The
Hi Pavel,
> Am 26.06.2017 um 10:39 schrieb Pavel Machek :
>
> On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
>> Hi Pavel,
>>
>>> Am 25.06.2017 um 11:18 schrieb Pavel Machek :
>>>
>>> Hi!
>>>
* unfortunately we still get no image :(
The latter is likely a setup issue
On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
> Hi Pavel,
>
> > Am 25.06.2017 um 11:18 schrieb Pavel Machek :
> >
> > Hi!
> >
> >> * unfortunately we still get no image :(
> >>
> >> The latter is likely a setup issue of our camera interface (OMAP3 ISP =
> >> Image
On Mon 2017-06-26 08:05:04, H. Nikolaus Schaller wrote:
> Hi Pavel,
>
> > Am 25.06.2017 um 11:18 schrieb Pavel Machek :
> >
> > Hi!
> >
> >> * unfortunately we still get no image :(
> >>
> >> The latter is likely a setup issue of our camera interface (OMAP3 ISP =
> >> Image Signal Processor)
Hi Pavel,
> Am 25.06.2017 um 11:18 schrieb Pavel Machek :
>
> Hi!
>
>> * unfortunately we still get no image :(
>>
>> The latter is likely a setup issue of our camera interface (OMAP3 ISP =
>> Image Signal Processor) which
>> we were not yet able to solve. Oscilloscoping signals
Hi Pavel,
> Am 25.06.2017 um 11:18 schrieb Pavel Machek :
>
> Hi!
>
>> * unfortunately we still get no image :(
>>
>> The latter is likely a setup issue of our camera interface (OMAP3 ISP =
>> Image Signal Processor) which
>> we were not yet able to solve. Oscilloscoping signals on the
Hi Hugues,
> Am 23.06.2017 um 12:25 schrieb H. Nikolaus Schaller :
>
> Hi Hugues,
>
>> Am 22.06.2017 um 17:41 schrieb H. Nikolaus Schaller :
>>
>>
>>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>>
>>> This patchset enables
Hi Hugues,
> Am 23.06.2017 um 12:25 schrieb H. Nikolaus Schaller :
>
> Hi Hugues,
>
>> Am 22.06.2017 um 17:41 schrieb H. Nikolaus Schaller :
>>
>>
>>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>>
>>> This patchset enables OV9655 camera support.
>>>
>>> OV9655 support has been tested
Hi!
> * unfortunately we still get no image :(
>
> The latter is likely a setup issue of our camera interface (OMAP3 ISP = Image
> Signal Processor) which
> we were not yet able to solve. Oscilloscoping signals on the interface
> indicated that signals and
> sync are correct. But we do not
Hi!
> * unfortunately we still get no image :(
>
> The latter is likely a setup issue of our camera interface (OMAP3 ISP = Image
> Signal Processor) which
> we were not yet able to solve. Oscilloscoping signals on the interface
> indicated that signals and
> sync are correct. But we do not
Hi Hugues,
> Am 22.06.2017 um 17:41 schrieb H. Nikolaus Schaller :
>
>
>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>
>> This patchset enables OV9655 camera support.
>>
>> OV9655 support has been tested using STM32F4DIS-CAM extension board
>>
Hi Hugues,
> Am 22.06.2017 um 17:41 schrieb H. Nikolaus Schaller :
>
>
>> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>>
>> This patchset enables OV9655 camera support.
>>
>> OV9655 support has been tested using STM32F4DIS-CAM extension board
>> plugged on connector P1 of STM32F746G-DISCO
> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>
> This patchset enables OV9655 camera support.
>
> OV9655 support has been tested using STM32F4DIS-CAM extension board
> plugged on connector P1 of STM32F746G-DISCO board.
> Due to lack of OV9650/52 hardware support, the
> Am 22.06.2017 um 17:05 schrieb Hugues Fruchet :
>
> This patchset enables OV9655 camera support.
>
> OV9655 support has been tested using STM32F4DIS-CAM extension board
> plugged on connector P1 of STM32F746G-DISCO board.
> Due to lack of OV9650/52 hardware support, the modified related code
This patchset enables OV9655 camera support.
OV9655 support has been tested using STM32F4DIS-CAM extension board
plugged on connector P1 of STM32F746G-DISCO board.
Due to lack of OV9650/52 hardware support, the modified related code
could not have been checked for non-regression.
First patches
This patchset enables OV9655 camera support.
OV9655 support has been tested using STM32F4DIS-CAM extension board
plugged on connector P1 of STM32F746G-DISCO board.
Due to lack of OV9650/52 hardware support, the modified related code
could not have been checked for non-regression.
First patches
40 matches
Mail list logo