All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: Jean-Francois Moine <moinejf@free.fr>,
	Thomas Kaiser <thomas@kaiser-linux.li>,
	V4L Mailing List <linux-media@vger.kernel.org>
Subject: Re: [RFC, PATCH] gspca pac7302: propagate footer to userspace
Date: Tue, 26 Jan 2010 13:29:19 +0100	[thread overview]
Message-ID: <4B5EE01F.2080702@redhat.com> (raw)
In-Reply-To: <4B5C8172.1090306@freemail.hu>

Hi Németh,

On 01/24/2010 06:20 PM, Németh Márton wrote:
> Hi,
>
> I'm dealing with Labtec Webcam 2200 and I found that the pac7302 driver does not
> forward the image footer information to userspace. This footer contains some information
> which might be interesting to the userspace. What exactly this footer means is
> not clear as of this writing, but it is easier to analyze the data in
> userspace than in kernel space.
>
> I modified the sd_pkt_scan() in order the footer is transfered to the userspace together
> with the image. This, however, breaks the image decoding in libv4lconvert. This is
> can be easily solved by passing the image buffer to v4lconvert_convert() truncated by
> 0x4f bytes.
>
> What do you think the right way would be to transfer image footer to userspace?

I agree that in retrospect sending the footer to userspace is a good
idea, but see below.

> Is it necessary to add a new V4L2_PIX_FMT_* format in order not to brake userspace
> programs?
>

Yes that is the only sensible way I see to do this, which IMHO is a too high price
to pay for just getting this info out of the kernel while we are not doing anything
with it. Now if we actually find a good use for this in userspace, then I think
we can do this, but until then I think you need to do this with a local
patch.

Regards,

Hans

      reply	other threads:[~2010-01-26 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 17:20 [RFC, PATCH] gspca pac7302: propagate footer to userspace Németh Márton
2010-01-26 12:29 ` Hans de Goede [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=4B5EE01F.2080702@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    --cc=nm127@freemail.hu \
    --cc=thomas@kaiser-linux.li \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.