All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jean-Francois Moine <moinejf@free.fr>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: video4linux-list@redhat.com, bugme-daemon@bugzilla.kernel.org,
	linuxkernel@lanrules.de
Subject: Re: [Bugme-new] [Bug 11776] New: Regression: Hardware working with old stock gspca module fails with 2.6.27 module
Date: Mon, 20 Oct 2008 16:55:37 -0700	[thread overview]
Message-ID: <20081020165537.9bb9ae8a.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-11776-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

gspca doesn't seem to have a MAINTAINERS record.  Or it is entered
under something unobvious so my search failed?


On Fri, 17 Oct 2008 17:48:54 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=11776
> 
>            Summary: Regression: Hardware working with old stock gspca module
>                     fails with 2.6.27 module
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.27
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: drivers_other@kernel-bugs.osdl.org
>         ReportedBy: linuxkernel@lanrules.de
> 
> 
> Latest working kernel version: 2.6.26.5
> Earliest failing kernel version: 2.6.27
> Distribution: ArchLinux
> Hardware Environment: i686 Lenovo T16P laptop, Lenovo USB 2.0 Webcam (40Y8519)
> Problem Description:
> I used gspca-1.0 from mxhaard.free.fr as a driver for my webcam. The driver
> worked. gspca is now included in the mainline kernel. The driver doesn't work
> anymore. The camera is detected, but the image is not shown. Instead, colorful
> noise is shown.
> 
> This is the information about the webcam given by the old gspca module, still
> working with 2.6.26:
> Camera found: lenovo MI1310_SOC
> Bridge found: VC0323
> StreamId: JPEG Camera
> quality 7 autoexpo 1 Timeframe 0 lightfreq 50
> Available Resolutions width 640  heigth 480 native
> Available Resolutions width 352  heigth 288 native
> Available Resolutions width 320  heigth 240 native *
> Available Resolutions width 176  heigth 144 native
> Available Resolutions width 160  heigth 120 native
> unable to probe size !! 
> 
> I don't see any significant difference in the output of the module included in
> 2.6.27. Tell me how I can provide more useful information.
> 

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

       reply	other threads:[~2008-10-20 23:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11776-10286@http.bugzilla.kernel.org/>
2008-10-20 23:55 ` Andrew Morton [this message]
2008-10-21  9:10   ` [Bugme-new] [Bug 11776] New: Regression: Hardware working with old stock gspca module fails with 2.6.27 module Hans de Goede
2008-10-21 11:15     ` Mauro Carvalho Chehab

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=20081020165537.9bb9ae8a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linuxkernel@lanrules.de \
    --cc=mchehab@infradead.org \
    --cc=moinejf@free.fr \
    --cc=video4linux-list@redhat.com \
    /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.