All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Devin Heitmueller" <devin.heitmueller@gmail.com>
To: "Hans Verkuil" <hverkuil@xs4all.nl>
Cc: video4linux-list@redhat.com
Subject: Re: Template for a new driver
Date: Mon, 15 Dec 2008 09:35:15 -0500	[thread overview]
Message-ID: <412bdbff0812150635x7187a9feh9e8a42b3034c67df@mail.gmail.com> (raw)
In-Reply-To: <200812151106.24382.hverkuil@xs4all.nl>

On Mon, Dec 15, 2008 at 5:06 AM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
> On Monday 15 December 2008 02:01:14 Devin Heitmueller wrote:
>> Hello,
>>
>> I am writing a new driver for a video decoder, and wanted to ask if
>> there was any particular driver people would suggest as a model to
>> look at for new drivers.  For example, I am not completely familiar
>> with which interfaces are deprecated, and want to make sure I use a
>> driver as a template that reflects the latest standards/conventions.
>>
>> Suggestions welcome.
>>
>> Thanks in advance,
>>
>> Devin
>
> Hi Devin,
>
> You definitely want to use the new v4l2_subdev framework for this. Read
> Documentation/video4linux/v4l2-framework.txt for more info.
>
> A good example template is probably saa7115.c. Not as big and
> complicated as the audio-video decoder cx25840, but still a good
> non-trivial example.
>
> I also recommend using struct v4l2_i2c_driver_data if you desire to be
> compatible with older kernels. The main reason for having this struct
> is to hide all the ugly kernel #ifdefs.
>
> Regards,
>
>        Hans

Thanks for the feedback.  Because I didn't wait for more responses
last night, I ended up using the cx25840 driver as the base, which
seems to have been a good choice.

Cheers,

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

      reply	other threads:[~2008-12-15 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15  1:01 Template for a new driver Devin Heitmueller
2008-12-15  4:41 ` Hiremath, Vaibhav
2008-12-15 10:06 ` Hans Verkuil
2008-12-15 14:35   ` Devin Heitmueller [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=412bdbff0812150635x7187a9feh9e8a42b3034c67df@mail.gmail.com \
    --to=devin.heitmueller@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=video4linux-list@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.