From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Hans de Goede <hdegoede@redhat.com>,
Joerg Heckenbach <joerg@heckenbach-aw.de>,
Dwaine Garden <dwainegarden@rogers.com>,
linux-media@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usbvision: remove (broken) image format conversion
Date: Tue, 03 May 2011 07:29:45 -0300 [thread overview]
Message-ID: <4DBFD919.3090409@redhat.com> (raw)
In-Reply-To: <201104262240.40497.linux@rainbow-software.org>
Em 26-04-2011 17:40, Ondrej Zary escreveu:
> On Tuesday 26 April 2011 14:33:20 Hans Verkuil wrote:
> After digging in the code for hours, I'm giving this up. It's not worth it.
>
> The ISOC_MODE_YUV422 mode works as V4L2_PIX_FMT_YVYU with VLC and
> mplayer+libv4lconvert, reducing the loop (and dropping strech_*) in
> usbvision_parse_lines_422() to:
> scratch_get(usbvision, frame->data + (frame->v4l2_linesize * frame->curline),
> 2 * frame->frmwidth);
>
> The ISOC_MODE_YUV420 is some weird custom format with 64-byte lines of YYUV.
> usbvision_parse_lines_420() is real mess with that scratch_* crap everywhere.
>
> ISOC_MODE_COMPRESS: There are callbacks to usbvision_request_intra() and also
> usbvision_adjust_compression(). This is not going to work outside the kernel.
>
>
> So I can redo the conversion removal patch to keep the RGB formats and also
> provide another one to remove the testpattern (it oopses too). But I'm not
> going to do any major changes in the driver.
While in a perfect world, this should be moved to userspace, I'm ok on keeping
it there, but the OOPS/Panic conditions should be fixed.
Could you please work on a patch fixing the broken stuff, without removing the
conversions?
Thanks,
Mauro
next prev parent reply other threads:[~2011-05-03 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 21:23 [PATCH] usbvision: remove (broken) image format conversion Ondrej Zary
2011-04-26 6:32 ` Hans Verkuil
2011-04-26 8:30 ` Ondrej Zary
2011-04-26 11:54 ` Hans de Goede
2011-04-26 12:33 ` Hans Verkuil
2011-04-26 20:40 ` Ondrej Zary
2011-05-03 10:29 ` Mauro Carvalho Chehab [this message]
2011-05-03 16:37 ` Ondrej Zary
2011-06-11 12:13 ` Mauro Carvalho Chehab
2011-06-16 14:28 ` Hans de Goede
2011-04-26 11:11 ` Hans de Goede
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=4DBFD919.3090409@redhat.com \
--to=mchehab@redhat.com \
--cc=dwainegarden@rogers.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=joerg@heckenbach-aw.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@rainbow-software.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 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).