From: "T.P. Reitzel" <4066724035@vzwmail.net>
To: linux-media@vger.kernel.org
Subject: gspca_spca505
Date: Wed, 21 Jan 2009 15:07:30 -0700 [thread overview]
Message-ID: <49779CA2.8050608@vzwmail.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
OK, I've raised the level of debug to 15 as you requested. Personally, I
hope the code for the internal capture card is still intact and bugs
simply prevent its use. Time will tell. ;) Evidently Intel isn't much
use as a source for documentation of equipment manufactured for them. I
wonder who wrote the Windows driver for the chipset used in this camera,
the chipset manufacturer? Somebody has the documentation and should be
willing to release it after this number of years has elapsed. You
developers know the process...so I HTH. I apologize for overlooking the
debug level on the first go.
[-- Attachment #2: image.dat --]
[-- Type: application/octet-stream, Size: 1013 bytes --]
[-- Attachment #3: kernel.txt --]
[-- Type: text/plain, Size: 1197 bytes --]
agpgart-amd64 0000:00:00.0: AGP 3.0 bridge
agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode
pci 0000:01:00.0: putting AGP V3 device into 8x mode
[drm] Setting GART location based on new memory map
[drm] Loading R300 Microcode
[drm] Num pipes: 1
[drm] writeback test succeeded in 1 usecs
usb 1-1: USB disconnect, address 4
usb 3-1: new full speed USB device using uhci_hcd and address 3
usb 3-1: configuration #1 chosen from 1 choice
gspca: probing 0733:0430
gspca: probe ok
usb 3-1: New USB device found, idVendor=0733, idProduct=0430
usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 3-1: USB disconnect, address 3
gspca: device released
gspca: disconnect complete
usb 3-1: new full speed USB device using uhci_hcd and address 4
usb 3-1: configuration #1 chosen from 1 choice
gspca: probing 0733:0430
spca505: Initializing SPCA505
spca505: After vector read returns : 0x101 should be 0x0101
gspca: probe ok
usb 3-1: New USB device found, idVendor=0733, idProduct=0430
usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
gspca: hald-probe-vide open
gspca: open done
gspca: try fmt cap S505 10000x10000
gspca: hald-probe-vide close
gspca: close done
next reply other threads:[~2009-01-21 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 22:07 T.P. Reitzel [this message]
2009-01-22 12:33 ` gspca_spca505 Jean-Francois Moine
-- strict thread matches above, loose matches on Subject: below --
2009-01-22 18:56 gspca_spca505 T.P. Reitzel
2009-01-21 1:38 gspca_spca505 T.P. Reitzel
2009-01-21 18:47 ` gspca_spca505 Jean-Francois Moine
2009-01-20 0:13 gspca_spca505 T.P. Reitzel
2009-01-20 8:22 ` gspca_spca505 Jean-Francois Moine
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=49779CA2.8050608@vzwmail.net \
--to=4066724035@vzwmail.net \
--cc=linux-media@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