lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1174161921.4419.15.camel@localhost>
Date:	Sat, 17 Mar 2007 18:05:21 -0200
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Laurent Pinchart <laurent.pinchart@...net.be>
Cc:	Maximus <john.maximus@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Porting V4L2 drivers to 2.6.20

Em Ter, 2007-03-13 às 11:08 +0100, Laurent Pinchart escreveu:
> > Hey,
> >          am porting V4L2 drivers from 2.6.13 to 2.6.20.
> >
> >      The driver is using a  structure 'video_device' which exists in
> > include/linux/videodev.h.
> >
> >      However, The linux kernel in 2.6.20 doesnot have that structure?.
> >
> >       Has the architecture changed between 2.6.13 to 2.6.20 for V4L2?.
> 
> The structure has been moved to include/media/v4l2-dev.h

Yes.

You should notice that, if you want to send those drivers to kernel
mainstream, they should also be ported to V4L2 API (since V4L1 API is
obsolete). So, you shouldn't include linux/videodev.h, but, instead,
linux/videodev2.h for v4l2 API (and v4l2-dev.h for the internal V4L2
structures). Also, please c/c me on v4l kernel patches submission, since
I'm the V4L maintainer.

Cheers,
Mauro.
> 
> Best regards,
> 
> Laurent Pinchart
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-- 
Cheers,
Mauro

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ