From: Bill Davidsen <davidsen@tmr.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-usb@vger.kernel.org, linux-media@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
Date: Tue, 01 Jun 2010 13:19:01 -0400 [thread overview]
Message-ID: <4C054105.6020806@tmr.com> (raw)
In-Reply-To: <4C04C942.6000900@redhat.com>
Hans de Goede wrote:
> Hi,
>
> On 05/29/2010 12:46 AM, Andrew Morton wrote:
>>
>> (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..
>>
>
> It may very well be a regression, I don't know. But in general the
> usbvideo drivers
> (of which the ibmcam is one) have been unmaintained for a long while,
> and they are
> still v4l1 drivers. I've been slowly working on converting all old
> v4l1 usb webcam
> drivers to the gspca usb webcam driver framework, removing a lot of
> code duplication
> (and other cruft such as controls being controlled through module
> parameters)
> from these drivers and making them v4l2 drivers in the progress.
>
> I really bough 2 ibmcam driver using webcams in the US and had them
> shipped to the
> Netherlands esp. for this purpose. I hope to have a new gspca
> subdriver to replace
> ibmcam soon.
>
> I know this is not really a fix for the problems with the existing
> ibmcam driver, but
> as it is destined to be replaced soon anyways I think this is the best
> way forward.
>
I tried the 2.6.34-11.fc13.x86_64 kernel, and the cameras "sort of" work
again, I had to change the size being used in the motion.conf file to
match what I found in the messages log, then I get imaging again, but
the kernel has multiple OOPS issues, which I have sent off to the
kerneloops folks. I don't feel comfortable using that kernel, even if it
doesn't actually die (or hasn't yet).
In case you don't have this information, here is a line from lsusb:
Bus 003 Device 002: ID 0545:8080 Xirlink, Inc. IBM C-It Webcam
Hopefully the items you have ordered are the same model.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
next prev parent reply other threads:[~2010-06-01 17:20 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 ` [Bugme-new] [Bug 16050] New: The ibmcam driver is not working Andrew Morton
2010-05-29 3:19 ` Bill Davidsen
2010-05-29 13:11 ` Bill Davidsen
2010-06-01 8:48 ` Hans de Goede
2010-06-01 17:19 ` Bill Davidsen [this message]
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=4C054105.6020806@tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hdegoede@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).