public inbox for linux-media@vger.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>,
	V4L Mailing List <linux-media@vger.kernel.org>,
	Thomas Kaiser <thomas@kaiser-linux.li>,
	Theodore Kilgore <kilgota@auburn.edu>,
	Kyle Guinn <elyk03@gmail.com>
Subject: Re: [PATCH 3/3] gspca pac7302/pac7311: separate the two subdrivers
Date: Sun, 08 Nov 2009 08:41:35 +0100	[thread overview]
Message-ID: <4AF6762F.6040208@redhat.com> (raw)
In-Reply-To: <4AF11D25.1080607@freemail.hu>

Hi Németh,

I'm getting similar reports for other (non pac73xx) model webcams with
2.6.32 on eeepc's and other computers using the uhci usb driver.

Can you try installing an older kernel (so 2.6.30) and then building
and installing the latest v4l-dvb tree (with your changes in) over that ?

I think what you are seeing here is a bug outside of the v4l subsystem,
this is just a hunch though.

Regards,

Hans



On 11/04/2009 07:20 AM, Németh Márton wrote:
> Dear Jef,
>
> although I tested my patch on my development computer together with Labtec
> Webcam 2200 (gspca_pac7302 driver) it seems that the patch may cause regression
> on some computers. For example I tested the gspca_pac7302 driver from
> http://linuxtv.org/hg/~jfrancois/gspca/ on top of Linux kernel 2.6.32-rc5 on
> an EeePC 901. I get the following error message in dmesg:
>
> [ 4476.992201] usb 3-2: new full speed USB device using uhci_hcd and address 11
> [ 4477.230485] usb 3-2: New USB device found, idVendor=093a, idProduct=2626
> [ 4477.230507] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> [ 4477.231139] usb 3-2: configuration #1 chosen from 1 choice
> [ 4477.417456] Linux video capture interface: v2.00
> [ 4477.437131] gspca: main v2.7.0 registered
> [ 4477.443214] gspca: probing 093a:2626
> [ 4477.453491] gspca: /dev/video0 created
> [ 4477.453541] gspca: probing 093a:2626
> [ 4477.453549] gspca: intf != 0
> [ 4477.453598] gspca: probing 093a:2626
> [ 4477.453605] gspca: intf != 0
> [ 4477.453755] usbcore: registered new interface driver pac7302
> [ 4477.453771] pac7302: registered
> [ 4489.552153] gspca: set alt 8 err -71
>
> I bisected the problem on EeePC 901 and the changeset 13373:99c23949b411
> (gspca - pac7302/pac7311: Separate the two subdrivers.) was marked as the first bad
> commit.
>
> On my development computer the same configuration works correctly:
>
> [ 7872.020222] usb 3-1: new full speed USB device using uhci_hcd and address 4
> [ 7872.251240] usb 3-1: configuration #1 chosen from 1 choice
> [ 7872.744755] Linux video capture interface: v2.00
> [ 7872.785032] gspca: main v2.7.0 registered
> [ 7872.797061] gspca: probing 093a:2626
> [ 7872.807577] gspca: /dev/video0 created
> [ 7872.809747] usbcore: registered new interface driver pac7302
> [ 7872.809798] pac7302: registered
>
> Is the separated driver working for you?
> Do you have any idea what could went wrong? Maybe some timing problem?
>
> Regards,
>
> 	Márton Németh
>
> Németh Márton wrote:
>> From: Márton Németh<nm127@freemail.hu>
>>
>> All PAC7311 specific functions remain in pac7311.c. All PAC7302 specific
>> functions are moved to pac7302.c. The USB device table is also divided into
>> two parts. This makes it possible to remove the sensor specific decisions
>> from different functions and also remove sensor infromation from the USB
>> device table.
>>
>> The common functions are just copied to both subdrivers. These common
>> functions can be separated later to a common file or helper module.
>>
>> Signed-off-by: Márton Németh<nm127@freemail.hu>
>> Cc: Thomas Kaiser<thomas@kaiser-linux.li>
>> Cc: Theodore Kilgore<kilgota@auburn.edu>
>> Cc: Kyle Guinn<elyk03@gmail.com>

      reply	other threads:[~2009-11-08  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 21:59 [PATCH 3/3] gspca pac7302/pac7311: separate the two subdrivers Németh Márton
2009-11-04  6:20 ` Németh Márton
2009-11-08  7:41   ` 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=4AF6762F.6040208@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=elyk03@gmail.com \
    --cc=kilgota@auburn.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox