All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Gast <schorsch_76@gmx.de>
To: linux-media@vger.kernel.org
Subject: Some Questions from a noobie v4l driver developer
Date: Sat, 10 Sep 2011 12:51:39 +0200	[thread overview]
Message-ID: <4E6B413B.8040802@gmx.de> (raw)

Hi all!

Currently i try to write a driver for a "Technisat Skysat2 HD eXpress"
DVB-S2 card. My current module is able to register the pci device and
unload. And now begins the journey to v4l ;)

As there is no driver available for linux i decided to write it myself.

Subdevice IDs: 1ae4:0700

My device contains the folowing ics:
SAA7160 rev3 (PCIe Bridge)
STV0903B (decoder)
STV6110A (tuner)

For the two frontends STV0903B and the tuner STV6110A exists already
driver. I dived a little through the linux kernel code and found the
driver for the "Technisat DVB-S/S2 USB 2.0 device" (from Patrick
Boettcher) which contains the same chips except the pcie bridge.

I read in the documentation of the linux kernel (Debian Wheezy - kernel
3.0.0), that v4l(1) was droped in 2.6.37 and new drivers should use
v4l2. The documentation of video4linux2 in the linux kernel shows that
there is a important function where all "ops" are registered.
v4l2_subdev_init(). In my "reference" driver (technisat-usb2.c for the
technisat usb device) that function is not used. Patrick Boettcher
speeks of a DVB-USB framework on his
homepage(http://www.wi-bw.tfh-wildau.de/~pboettch/home/index.php).

So my questions are:
a) What framework should i use? V4L2?
b) Is it reasonable that i could refactor most of the code of Patrick
Boettchers Technisat USB Driver?
c) Is the documentation for video4linux2 uptodate in the kernel? Or
should i use an other documentation?
d) There is a driver namned saa716x from Manu Abrahams. Is this driver
in  state where i could modify it that it supports my device?

Best Regards
Georg Gast

                 reply	other threads:[~2011-09-10 10:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4E6B413B.8040802@gmx.de \
    --to=schorsch_76@gmx.de \
    --cc=linux-media@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 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.