linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@skynet.be>
To: Maximus <john.maximus@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Porting V4L2 drivers to 2.6.20
Date: Tue, 13 Mar 2007 11:08:02 +0100	[thread overview]
Message-ID: <200703131108.03090.laurent.pinchart@skynet.be> (raw)
In-Reply-To: <3634de740703130300j12928fbeob860c067e46badbf@mail.gmail.com>

> 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

Best regards,

Laurent Pinchart

  reply	other threads:[~2007-03-13 10:08 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 [this message]
2007-03-17 20:05   ` Mauro Carvalho Chehab

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=200703131108.03090.laurent.pinchart@skynet.be \
    --to=laurent.pinchart@skynet.be \
    --cc=john.maximus@gmail.com \
    --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).