On Tuesday 17 February 2004 16:28, you wrote:
> On Tue, 17 Feb 2004, Dominik Kuhlen wrote:
> > Hello
> Try this patch and tell us if it works.
>
> Alan Stern
>
>
> = config.c 1.28 vs edited =
> --- 1.28/drivers/usb/core/config.cFri Sep 26 12:37:44 2003
Hello
If I connect my camera I'll get this messages:
---snip
Feb 16 09:36:00 doku kernel: drivers/usb/core/config.c:107: unexpected descriptor 0x5,
expecting interface, 0x4
Feb 16 09:36:00 doku kernel: usb 1-1.1: can't read configurations, error -22
---snip
and the device isn't listed in /proc/bu
t directories and positions)
> - Dave
>
>
> - Original Message -
> From: "Dominik Kuhlen" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, April 16, 2002 4:09 PM
> Subject: [linux-usb-devel] Mistake in usb.c
>
>
> Hell
Hello !
After some source investigations I discovered a harmless mistake:
The description of the usb_control_msg(...) function says
it returns 0, or less than 0 if an error occured, but
the usb_internal_control_msg returns length, which is sometimes >0
(success) or <0 if error.
Thanks
PRODUCT_SX330Z 0x3300
#define USB_REQ_RESERVED 0x04
#define USB_DIR_VENDOR 0x40
#define DRIVER_VERSION "v0.1"
#define DRIVER_DESC "Traveler SX330z Camera Driver"
#define SX330Z_MINOR_BASE 65
MODULE_AUTHOR("Dominik Kuhlen <[EMAIL PROTECTED]>");
MODULE_DESCRIPTION(DRI
Here are some fragments of my (1.try) code:
I used some professional USB sniffer (CATC USBChief) to get an idea what
the computer says to the camera and vice versa.
Then I replayed the packets (at least I hope so) to
achieve the same behaviour.
As I mentioned the TOC works.
- snip
Hello List!
I'm new to Kernel- and USB programming.
My digital camera does some USB Spec violation (eg : Request type 0x04
(reserved for future use)), so I'm not sure if its a good idea to write a
driver.
The next question is how to implement it.
Best would be libusb support -> gphoto support
