From: Dinesh Bhat <dbhat@linsys.ca>
To: Video-4l-list <video4linux-list@redhat.com>
Subject: V4L for DVB ASI
Date: Thu, 24 Jul 2008 11:36:27 -0500 [thread overview]
Message-ID: <4888AF8B.9030609@linsys.ca> (raw)
Hello,
We are DVB ASI PCI/PCIe card manufacturers in Canada. Some of you may
have heard about our distributors: DVEO/Computer Modules. We encourage
open source and use open source to develop our Linux products. I have
been doing some research on getting our already open sourced DVB ASI
drivers to work with either v4l or the regular DVB API.
I had asked a question to the community a while ago and have had few
responses. The question was mainly to find out if there is any interest
in the community towards this goal. We will be happy to work with you.
The initial response was to work on v4l as opposed to the DVB API. Since
the cards support PID filtering and other transport stream analysis, I
am encouraged to use DVB API instead of V4L because of TS feature
support at the software level. But then I could be wrong since I have
not done a lot of research on these two APIs. Sigmund Augdal had listed
out the pros and cons to my previous question:
Use the DVB Api:
pros:
* you can take advantage of the software pid and section filters in the
dvb framework
* if your device supports hardware pid/section filters, apis will be
available to take advantage of them
* userspace applications that handle mpeg2 ts often use this api, and
would be easy to adapt.
cons:
* you might need to extend the apis to handle asi cards
Use the v4l2 api:
pros:
* semantics are well defined.
* provides an extensible api using so called "controls"
cons:
* adapting user space applications will be more difficult
* no reuse of software filters
If Anybody wants to look at the drivers, they are available at http://www.linsys.ca in customer support section.
Thanks for any advice and help.
Kind Regards,
Dinesh
--
Linear Systems Ltd
Unit 1, 1717 Dublin Ave
Winnipeg, Manitoba, R3H 0H2
Canada
Ph:204-632-4300 Extn: 30
Fx: 204-697-2417
www.linsys.ca
CONFIDENTIALITY WARNING
The information contained in the e-mail and any documents or attachments accompanying this transmission are private and confidential and intended for the specific individual, or group, or entity named in the recipient fields of this message. If the reader of this message is not the intended recipient, or the authorized agent thereof, the reader is hereby notified that any dissemination, distribution or copying of this transmission is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone at 204-632-4300 and delete all copies of the original message. No warranties are made or implied in this communication. Thank you.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-07-24 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 16:36 Dinesh Bhat [this message]
2008-07-25 10:36 ` V4L for DVB ASI Hans Verkuil
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=4888AF8B.9030609@linsys.ca \
--to=dbhat@linsys.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox