On 1/28/19 11:41 AM, Sakari Ailus wrote:
> Hi Hans,
>
> On Mon, Jan 28, 2019 at 10:52:40AM +0100, Hans Verkuil wrote:
>> On 1/28/19 10:21 AM, Sakari Ailus wrote:
>>> Hi Hans,
>>>
>>> Thanks for the patch.
>>>
>>> On Sat, Jan 26, 2019 at 12:06:19PM +0100, Hans Verkuil wrote:
This patch adds an
Hi Hans,
On Mon, Jan 28, 2019 at 10:52:40AM +0100, Hans Verkuil wrote:
> On 1/28/19 10:21 AM, Sakari Ailus wrote:
> > Hi Hans,
> >
> > Thanks for the patch.
> >
> > On Sat, Jan 26, 2019 at 12:06:19PM +0100, Hans Verkuil wrote:
> >> This patch adds an extended version of VIDIOC_DQEVENT that:
> >>
On 1/28/19 10:21 AM, Sakari Ailus wrote:
> Hi Hans,
>
> Thanks for the patch.
>
> On Sat, Jan 26, 2019 at 12:06:19PM +0100, Hans Verkuil wrote:
>> This patch adds an extended version of VIDIOC_DQEVENT that:
>>
>> 1) is Y2038 safe by using a __u64 for the timestamp
>> 2) needs no compat32 conversi
Hi Hans,
Thanks for the patch.
On Sat, Jan 26, 2019 at 12:06:19PM +0100, Hans Verkuil wrote:
> This patch adds an extended version of VIDIOC_DQEVENT that:
>
> 1) is Y2038 safe by using a __u64 for the timestamp
> 2) needs no compat32 conversion code
> 3) is able to handle control events from 64-
This patch adds an extended version of VIDIOC_DQEVENT that:
1) is Y2038 safe by using a __u64 for the timestamp
2) needs no compat32 conversion code
3) is able to handle control events from 64-bit control types
by changing the type of the minimum, maximum, step and default_value
field to __u
