patch-2.3.40 linux/Documentation/usb/dc2xx.txt

• Lines: 125
• Date: Thu Jan 20 09:48:48 2000
• Orig file: v2.3.39/linux/Documentation/usb/dc2xx.txt
• Orig date: Thu Jan 6 12:57:47 2000

diff -u --recursive --new-file v2.3.39/linux/Documentation/usb/dc2xx.txt linux/Documentation/usb/dc2xx.txt
@@ -1,4 +1,4 @@
-13 November 1999
+19 January 2000
 david-b@pacbell.net
 
 This is an overview of how to use the "dc2xx" USB driver with certain
@@ -15,14 +15,13 @@
 (www.gphoto.org), since version 0.4 and later know how to use it to talk
 to Kodak DC-240 and DC-280 cameras over USB.
 
-In addition the DC-260, DC-265, and DC-290 are currently recognized.
+In addition the DC-220, DC-260, DC-265, and DC-290 are also recognized.
 However, like other cameras using the "Digita OS" (from www.flashpoint.com)
 there is no gPhoto support for this camera.  At this writing the best
 known support for these cameras is a Python script that supports image
 downloading from those cameras.  (See archives of the linux-usb mailing
-list.)  The DC-220 should also work with this driver, given information
-about the USB product IDs.  When it becomes available, the HP PhotoSmart
-C500 should also work ... it's another Digita OS camera with USB support.)
+list.)  When it becomes available, the HP PhotoSmart C500 should also
+work ... it's another Digita OS camera with USB support.
 
 It's likely that other digital still cameras can also use this USB driver,
 even if they're not from Kodak and don't use Digita.  The reason is that
@@ -35,30 +34,33 @@
 
 This has been shown to work on x86 OHCI and UHCI (Intel) chipsets.  OHCI has
 been trouble free; not so with UHCI, which was first seen to be happy with
-2.3.24 kernels, and has not been as fast as OHCI.
+2.3.24 kernels, and has not been as fast as OHCI.  Users on the PowerMac
+platform have had success, although the stock kernel doesn't yet support
+that platform.
 
 Note that in some cases changes in BIOS settings may be needed before
 your USB works.  At least one user has reported a need for SMP-related 
 settings as well.
 
-As yet, no reports have come from Linux users on non-Intel hardware.
-(You could color coordinate your iMac with a DC-240i ... :-)
-
 
 SETUP
 
-Configure in the DC2XX USB driver, and have it in your kernel.  Recently I
-compile it right in, but I've done it as a module in the past.
-
-Create a device, perhaps like this (both read and write):
+Configure in the DC2XX USB driver, and have it in your kernel.  It works
+as a module, or compiled in directly.
 
-    # mknod -m 0666 /dev/kodak c 10 170
+Create at least one device, perhaps like this (both read and write):
 
-That "170" is not formally assigned, and this command may change.  If you're
-using a non-Kodak camera, you may prefer another name.
-
-Don't plug in more than one compatible camera at this time.  One of them
-will be ignored, but I'd not be sure which one!
+    # mknod -m 0666 /dev/kodak00 c 180 80
+    # mknod -m 0666 /dev/kodak01 c 180 81
+    ...
+
+The driver supports multiple device nodes.  The USB framework supports
+a maximum of sixteen device nodes (up to minor device number 96), though
+by default fewer devices are available.
+
+When you plug in one camera, it will use the first device node (kodak00
+in the example above).  A second camera will use the second device node,
+and so on.
 
 
 SANITY TESTING
@@ -66,14 +68,11 @@
 First:  if you've got /proc support, make sure that the driver has hooked
 itself up correctly.
 
-    - you should see an entry in /proc/misc for the a Kodak DC-2xx
-      minor device number
-
-    - you should see an entry in /proc/bus/usb/drivers for "dc2xx",
-      if you also enabled USB /proc support.
+    - You should see an entry in /proc/bus/usb/drivers for "dc2xx",
+      if you enabled USB /proc support.
 
 Second:  when you connect your camera to the computer, does it get recognized
-by the driver?
+by the driver?  (Make sure the camera is powered on!)
 
     - if you've got /proc/bus/usb/devices, you should see an entry
       something like this.  The "ProdID" may be different if you didn't
@@ -87,19 +86,16 @@
 	E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
 	E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
 
-    - if you don't have /proc support for USB, see if "dmesg" output
-      tells you that you plugged in your camera.
+    - see if "dmesg" output tells you that you plugged in your camera.
 
-	USB new device connect, assigned device number 1
 	Manufacturer: Eastman Kodak Company
 	Product: KODAK DC240 Zoom Digital Camera
-	USB Camera is connected
-	usbcore: dc2xx driver claimed interface c3a68600
-	ohci-control thread sleeping
+	Serial Number: ?
+	dc2xx.c: USB Camera #0 connected
 
 Third:  (optional) can you use gPhoto to talk to the camera?
 
-    - When you configure your camera, tell it to use "/dev/kodak" (or
+    - When you configure your camera, tell it to use "/dev/kodak00" (or
       whatever name you used).  Right now, gPhoto emits a diagnostic
       message (non-GUI) saying that it since it didn't act like a TTY,
       it's assuming it's got a USB connection.
@@ -108,3 +104,10 @@
       talk to the camera -- and tell you you're using USB.
 
 If you got that far, you should be able to use everything fine.
+
+
+ADDITIONAL INFORMATION
+
+You may find that you need more driver-specific information, which is
+currently accessible through a link from http://www.linux-usb.org/
+along with other Linux USB resources.