All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 03 Jun 2010 12:17:48 -0400	[thread overview]
Message-ID: <4C07D5AC.2000404@tmr.com> (raw)
In-Reply-To: <4C07C711.5040900@redhat.com>

Hans de Goede wrote:
> Hi,
>
> On 06/03/2010 04:58 PM, Bill Davidsen wrote:
>> Hans de Goede wrote:
>>> Hi,
>>>
>>> On 06/01/2010 07:19 PM, Bill Davidsen wrote:
>>>> Hans de Goede wrote:
>>> >
>>>> 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.
>>>>
>>>
>>> I have the same usb-id, but I'm working on the driver now and it
>>> seems XirLink distinguishes between different models by bcdversion,
>>> instead of using different usb ids for each product.
>>>
>>> Can you send me a mail with the output of "lsusb -v", then I can
>>> see if you have the same version as I have for testing.
>>>
>>
>> Sure, attached.
>>
>
> Thx,
>
> Your device has a revision of 3.0a (the firmware programmers did not
> seem to fully grasp the concept of the d in bcd (it stands for decimal),
> which is different from mine which is revision 3.01 . Your version is
> referred to as a model2 by the old driver, where as mine is a model3.
>
> This is both bad and good news, the bad news is I cannot give you an
> already tested driver to fix your issues. The good news is, that this
> means that, assuming that you are willing to help out with testing, we
> can now also verify that model 2 cams will work with the new driver.
>
> So would you be willing to test the new driver (when it is finished) ?
>
Sure, just let me know what kernel the patch is against. As you say, my 
cams are Model2 in the old nomenclature.

Interesting that the size is set to 352x240 rather than CIF 352x288. And 
while xawtv sort of works with the latest 2.6.33.5-112.fc13.x86_64 koji 
kernel, cheese doesn't, not that I need it, but it worked on the early 
kernels.

-- 
Bill Davidsen <davidsen@tmr.com>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein


  reply	other threads:[~2010-06-03 16:19 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
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 [this message]
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=4C07D5AC.2000404@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 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.