public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] v4l-utils: Add the JPEG Lite decoding function
Date: Tue, 15 Feb 2011 20:30:25 +0100	[thread overview]
Message-ID: <4D5AD451.2020102@redhat.com> (raw)
In-Reply-To: <20110215102626.3e8e83d3@tele>

Hi,

On 02/15/2011 10:26 AM, Jean-Francois Moine wrote:
> Hi Hans,
>
> I got the permission to relicense the JPEG Lite decoding to the LGPL.
>

Ah, good, patch applied and pushed to git.

> If you want to test the nw80x driver, get the gspca tarball from my web
> page (2.12.12). I added your webcam which should directly work (p35u -
> chip nw801).

I've tested it and it works :) I also tested the JPGL -> YUV path.

I did find 2 bugs, the "if (gspca_dev->curr_mode)" test in sd_start,
needs to be inverted. In general it is a good idea to do a test
on gspca_dev->width, rather then curr_mode IMHO, it is more
readable and less error prone.

Talking about readability, I also found the

         if (sd->bridge == BRIDGE_NW800) {
		...
	} else {
		...
		if (sd->bridge == BRIDGE_NW802) {
			...
		} else {
			...
		}
	}

part in sd_init a bit hard to grok, can this be changed
to a switch case on sd->bridge ?

The other bug was a divide by zero -> kernel panic, in
do_autogain when sd->ae_res == 0, note this was when I was
messing around with the driver a bit (before I found the
issue with the inverted curr_mode check), but I think this
could happen in real life to depending on register values
and we should protect against this.

Regards,

Hans

  reply	other threads:[~2011-02-15 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15  9:26 [PATCH] v4l-utils: Add the JPEG Lite decoding function Jean-Francois Moine
2011-02-15 19:30 ` Hans de Goede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-14 12:36 Jean-Francois Moine
2011-02-14 19:20 ` 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=4D5AD451.2020102@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    /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