linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Szmigiero <mhej@o2.pl>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	Antti Palosaari <crope@iki.fi>,
	Malcolm Priestley <tvboxspy@gmail.com>,
	Patrick Boettcher <pboettcher@kernellabs.com>,
	Martin Wilks <m.wilks@technisat.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Andy Walls <awalls@md.metrocast.net>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Sven Barth <pascaldragon@googlemail.com>,
	Lucas De Marchi <lucas.demarchi@profusion.mobi>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH]Medion 95700 analog video support
Date: Sun, 04 Sep 2011 23:01:09 +0200	[thread overview]
Message-ID: <4E63E715.6020708@o2.pl> (raw)
In-Reply-To: <CAOcJUbzXKVoOsfLA+YewyfDKmxuX0PgB8mWdfG49ArdS1fpyfA@mail.gmail.com>

W dniu 04.09.2011 21:46, Michael Krufky pisze:
> Maciej,
> 
> I'm excited to see some success getting analog to work in the dvb-usb
> framework.  Some people have been asking for this support in the cxusb
> driver for a long time.
> 
> I have a device (DViCO FusionHDTV5 usb) that should work with this
> patch with some small modifications -- i will try it out.
> 
> I see that this patch adds analog support to cxusb... have you thought
> at all about adding generic analog support callbacks to the dvb-usb
> framework?  There are some other dvb-usb devices based on the dib0700
> chipset that also also use the cx25840 decoder for analog -- it would
> be great if this can be done in a way to benefit both the dib0700 and
> cxusb drivers.
> 
> I will let you know how things go after I try this code on my own device, here.
> 
> Thanks for your patch.
> 
> -Mike Krufky

Hi and thanks for reply,

I think whether the code should be moved to dvb-usb framework really 
depends on how much the devices have in common - Medion uses a
generic Cypress FX2 USB bridge which is programmed (by firmware) to post an
ISO buffer once there is exactly 1010 bytes received on its parallel interface.

This parallel interface is 8-bit wide and has data inputs connected to cx25840
video interface data output and clock input to cx25840 pixel clock output.
USB bridge does not modify this data in any way, nor it does any alignment.
So we have a raw BT.656 (or VESA VIP) stream coming from the device.

Because there are 3 such 1010-byte packets per (micro)frame 
the URB frame descriptor has to be 3030 bytes in length (or more) or data will
be truncated, which will result in parts of field being all-green.

If your device has similar characteristics then it is just matter of substituting
a few commands in code (and maybe changing CXUSB_VIDEO_PKT_SIZE to different value
if it does not use 3*1010 byte frames).

Otherwise, for example if device outputs simple YUV data without any framing, the code
will pretty much be different - other than a bit of V4L2 driver glue code which can be shared.

Best regards and hope this helps,
Maciej Szmigiero

  reply	other threads:[~2011-09-04 21:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04 18:51 [PATCH]Medion 95700 analog video support Maciej Szmigiero
2011-09-04 19:05 ` Arnaud Lacombe
2011-09-04 19:10   ` Maciej Szmigiero
2011-09-04 19:46 ` Michael Krufky
2011-09-04 21:01   ` Maciej Szmigiero [this message]
2011-09-23 19:32   ` Mauro Carvalho Chehab
2011-09-23 19:39     ` Michael Krufky
2011-09-23 21:06       ` Andy Walls
2011-09-23 21:15         ` Maciej Szmigiero
2011-09-24 20:21           ` Andy Walls
2011-09-26 21:37             ` Maciej Szmigiero
2011-09-26 23:53               ` Andy Walls
2011-10-02 19:12                 ` Maciej Szmigiero
2012-08-13 23:35                   ` Mauro Carvalho Chehab
2012-08-15 10:56                     ` Maciej S. Szmigiero

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=4E63E715.6020708@o2.pl \
    --to=mhej@o2.pl \
    --cc=awalls@md.metrocast.net \
    --cc=crope@iki.fi \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=m.wilks@technisat.com \
    --cc=mchehab@infradead.org \
    --cc=mkrufky@linuxtv.org \
    --cc=pascaldragon@googlemail.com \
    --cc=pboettcher@kernellabs.com \
    --cc=tvboxspy@gmail.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;
as well as URLs for NNTP newsgroup(s).