From: Pete <pete@sensoray.com>
To: video4linux-list@redhat.com
Cc: Greg KH <greg@kroah.com>, Dean Anderson <dean@sensoray.com>
Subject: go7007 development
Date: Fri, 17 Oct 2008 08:21:51 -0700 [thread overview]
Message-ID: <1224256911.6327.11.camel@pete-desktop> (raw)
Hello,
I am working on adding the Sensoray 2250 to the go7007 staging tree,
starting from GregKH's staging patch here:
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
gregkh-05-staging-2.6.27.patch
In particular, we are stuck how to change the MPEG format with standard
IOCTL calls. In particular, this comment in the driver go7007.h below
needs explanation:
/* DEPRECATED -- use V4L2_PIX_FMT_MPEG and then call GO7007IOC_S_MPEG_PARAMS
* to select between MPEG1, MPEG2, and MPEG4 */
#define V4L2_PIX_FMT_MPEG4 v4l2_fourcc('M','P','G','4') /* MPEG4 */
The existing driver, for backward-compatibility , allowed
V4L2_PIX_FMT_MPEG4 to be used for v4l2_format.pixelformat with
VIDIOC_S_FMT.
GO7007IOC_S_MPEG_PARAMS is a custom ioctl call and we would rather have
this done through v4l2 calls. We also can't seem to find where MPEG1,
MPEG2, and MPEG4 elementary streams are defined in the V4L2 API. We
checked other drivers, but could not find anything. The closest thing
we found was the V4L2_CID_MPEG_STREAM_TYPE control, but the enums do not
define elementary streams nor MPEG4.
Your advice is appreciated.
Thanks.
--
Pete Eberlein
Sensoray Co., Inc.
Email: pete@sensoray.com
http://www.sensoray.com
--
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-10-17 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:21 Pete [this message]
2008-10-17 15:36 ` go7007 development Hans Verkuil
2008-10-17 16:07 ` Dean Anderson
2008-10-17 16:21 ` Hans Verkuil
2008-10-24 23:43 ` [PATCH] Add MPEG4 and Elementary streams (was Re: go7007 development) Pete Eberlein
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=1224256911.6327.11.camel@pete-desktop \
--to=pete@sensoray.com \
--cc=dean@sensoray.com \
--cc=greg@kroah.com \
--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