From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Laurent Pinchart <laurent.pinchart@skynet.be>
Cc: Maximus <john.maximus@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Porting V4L2 drivers to 2.6.20
Date: Sat, 17 Mar 2007 18:05:21 -0200 [thread overview]
Message-ID: <1174161921.4419.15.camel@localhost> (raw)
In-Reply-To: <200703131108.03090.laurent.pinchart@skynet.be>
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@vger.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
prev parent reply other threads:[~2007-03-17 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 10:00 Porting V4L2 drivers to 2.6.20 Maximus
2007-03-13 10:08 ` Laurent Pinchart
2007-03-17 20:05 ` Mauro Carvalho Chehab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1174161921.4419.15.camel@localhost \
--to=mchehab@infradead.org \
--cc=john.maximus@gmail.com \
--cc=laurent.pinchart@skynet.be \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).