From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Sensoray Linux Development <linux-dev@sensoray.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 1/2][media] s2255drv: adding MJPEG format
Date: Mon, 02 May 2011 13:36:27 -0300 [thread overview]
Message-ID: <4DBEDD8B.7000905@redhat.com> (raw)
In-Reply-To: <4D9A0AFA.7090202@sensoray.com>
Em 04-04-2011 15:16, Sensoray Linux Development escreveu:
> adding MJPEG format
>
Please be careful when sending patches. I had to manually apply the hunks,
as whitespaces were completely wrong on this patchset.
> Signed-off-by: Dean Anderson <linux-dev@sensoray.com>
> ---
> drivers/media/video/s2255drv.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/media/video/s2255drv.c b/drivers/media/video/s2255drv.c
> index b12e28e..38e5c4b 100644
> --- a/drivers/media/video/s2255drv.c
> +++ b/drivers/media/video/s2255drv.c
> @@ -428,6 +428,10 @@ static const struct s2255_fmt formats[] = {
> .fourcc = V4L2_PIX_FMT_JPEG,
> .depth = 24
> }, {
> + .name = "MJPG",
> + .fourcc = V4L2_PIX_FMT_MJPEG,
> + .depth = 24
> + }, {
> .name = "8bpp GREY",
> .fourcc = V4L2_PIX_FMT_GREY,
> .depth = 8
> @@ -648,6 +652,7 @@ static void s2255_fillbuff(struct s2255_channel *channel,
> memcpy(vbuf, tmpbuf, buf->vb.width * buf->vb.height);
> break;
> case V4L2_PIX_FMT_JPEG:
> + case V4L2_PIX_FMT_MJPEG:
> buf->vb.size = jpgsize;
> memcpy(vbuf, tmpbuf, buf->vb.size);
> break;
> @@ -1032,6 +1037,7 @@ static int vidioc_s_fmt_vid_cap(struct file *file, void *priv,
> mode.color |= COLOR_Y8;
> break;
> case V4L2_PIX_FMT_JPEG:
> + case V4L2_PIX_FMT_MJPEG:
> mode.color &= ~MASK_COLOR;
> mode.color |= COLOR_JPG;
> mode.color |= (channel->jc.quality << 8);
prev parent reply other threads:[~2011-05-02 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 18:16 [PATCH 1/2][media] s2255drv: adding MJPEG format Sensoray Linux Development
2011-05-02 16:36 ` Mauro Carvalho Chehab [this message]
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=4DBEDD8B.7000905@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-dev@sensoray.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox