On Wed, 27 Nov 2002 @ 4:09pm (+0900), Jorgen Lundman wrote:

JL>
JL> Since there has been some great work done on USB I thought I'd see how
JL> far I can get with my Ricoh RDC-i500 camera. It has a Type 2 PCMCIA slot
JL> in it, and currently an IBM Microdrive (340MB).
JL>
JL> It works in a strange manner on windows in that the camera enters
JL> something similar to DHCP query, the window's side driver hands it an IP
JL> (generally 127.0.0.1) and you can connect to that, port 80 and browse.
JL>
JL> Not really interested in that per say, it would be nice if I could
JL> access the Microdrive, or internal memory, but perhaps that is an
JL> extension of the IP section mentioned?
JL>
JL> If I plug it into a generic 1.6 kernel I get:
JL>
JL> Nov 27 22:34:57 afro /netbsd: umass0 at uhub1 port 1 configuration 1
JL> interface 0
JL> Nov 27 22:34:57 afro /netbsd:
JL>
JL> (yes, comes up with a blank line)
JL>
JL> and eventually:
JL>
JL> Nov 27 22:35:38 afro /netbsd: umass0: at uhub1 port 1 (addr 2) disconnected
JL> Nov 27 22:35:38 afro /netbsd: umass0 detached

scsibus0 should attach to umass0...are you running a custom kernel? you might
have seen anything SCSI and just assumed wack it out of there

my sony:

umass0 at uhub0 port 1 configuration 1 interface 0
umass0: Sony Sony DSC, rev 1.00/3.28, addr 2
umass0: using RBC over CBI
scsibus1 at umass0: 2 targets, 1 luns per target
scsibus1: waiting 2 seconds for devices to settle...
sd4 at scsibus1 target 1 lun 0: <Sony, Sony DSC, 3.28> SCSI0 0/direct removable
sd4: mode sense (4) returned nonsense; using fictitious geometry
sd4: 63424 KB, 61 cyl, 64 head, 32 sec, 512 bytes/sect x 126848 sectors
sd4: mode sense (4) returned nonsense; using fictitious geometry
sd4: no disk label

-lava

JL>
JL> when the camera times out. (Or I turn off).
JL>
JL>
JL>
JL> I turned on usbdebugging, and had a look around, this message comes up:
JL>
JL> Nov 28 00:13:50 afro /netbsd: usbd_submatch port=1,-1 configno=-1,-1
JL> ifaceno=-1,-1 vendor=1482,-1 product=8738,-1 release=0,-1
JL> Nov 28 00:13:50 afro last message repeated 24 times
JL> Nov 28 00:13:50 afro /netbsd: usbd_print dev=0xc0bc8800
JL> Nov 28 00:13:50 afro /netbsd: usbd_probe_and_attach: no device specific
JL> driver found
JL>
JL> I edited "usbdevs" to add in Ricoh, and the product, rebuild the .h
JL> files, and also added an entry in "umass_quirks.c" - with some generic
JL> looking defaults ( is that right? all devices are in there, or only
JL> those with quirks? )
JL>
JL> Not got any further however, anything else I can try?, or would it
JL> require far too much work to be worth it?
JL>
JL>
JL> Lundy
JL>
JL>
JL>
JL>
JL> --
JL> Jorgen Lundman       | <lundman@lundman.net>
JL> Unix Administrator   | +81 (0)3 -5456-2687 ext 1017 (work)
JL> Shibuya-ku, Tokyo    | +81 (0)90-5578-8500          (cell)
JL> Japan                | +81 (0)3 -3375-1767          (home)
JL>

later -           | _BonaFide[] = { coder, author, | /~\ The ASCII Ribbon
Brian A. Seklecki | problem solver, scholar, BOFH, | \ / Campaign Against
                  | vegetarian, runner, NetBSD     |  X  Exchange, Outlook
                  | advocate, spiritual machine }; | / \ & HTML Email

PGP: 0111 4618 0111 4618 4AB2 24EB C853 6611 75C4 A91E A7A7 4973

"Any sufficiently advanced technology is indistinguishable from magic." -- Arthur C. Clark