All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-usb@vger.kernel.org, linux-media@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org, davidsen@tmr.com
Subject: Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
Date: Fri, 28 May 2010 15:46:35 -0700	[thread overview]
Message-ID: <20100528154635.129b621b.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-16050-10286@https.bugzilla.kernel.org/>


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

On Tue, 25 May 2010 23:02:23 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=16050
> 
>                URL: https://bugzilla.redhat.com/show_bug.cgi?id=588900
>            Summary: The ibmcam driver is not working
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.34
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: USB
>         AssignedTo: greg@kroah.com
>         ReportedBy: davidsen@tmr.com
>         Regression: Yes
> 
> 
> This driver has been working, and around the 1st of May I updated my Fedora
> kernel (FC13-RC) to current. The camera stopped working, so I built the latest
> 2.6.34-rc version and verified the problem. When 2.6.34 final released I
> repeated the test and the driver is still not working.
> 
> Originally reported against Fedora (not going to be fixed in FC13) the
> information in the Fedora report may be enough to identify the problem. I can
> do a bit of test almost any day, but the cams are on a video monitoring system,
> so I'm not able to do long bisects and such.
> 

It's a 2.6.33 -> 2.6.34 regression, I think.  I don't know whether it's
a v4l problem or a USB one..


       reply	other threads:[~2010-05-28 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16050-10286@https.bugzilla.kernel.org/>
2010-05-28 22:46 ` Andrew Morton [this message]
2010-05-29  3:19   ` [Bugme-new] [Bug 16050] New: The ibmcam driver is not working Bill Davidsen
2010-05-29 13:11   ` Bill Davidsen
2010-06-01  8:48   ` Hans de Goede
2010-06-01 17:19     ` Bill Davidsen
2010-06-03 13:53       ` Hans de Goede
2010-06-03 14:58         ` Bill Davidsen
2010-06-03 15:15           ` Hans de Goede
2010-06-03 16:17             ` Bill Davidsen
2010-06-09 14:51               ` 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=20100528154635.129b621b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=davidsen@tmr.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@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 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.