From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 15 13:32:38 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42E1E16A4CE for ; Mon, 15 Dec 2003 13:32:38 -0800 (PST) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (c-180-197-180.ka.dial.de.ignite.net [62.180.197.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60DE443D33 for ; Mon, 15 Dec 2003 13:31:55 -0800 (PST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk (NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk [2002:3eb4:c5b4:0:200:c0ff:fefc:19aa]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id hBFLVUc10935 verified NO) for ; Mon, 15 Dec 2003 22:31:32 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost)hBFLVUG06445; Mon, 15 Dec 2003 22:31:30 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Mon, 15 Dec 2003 22:31:30 +0100 (CET) Message-Id: <200312152131.hBFLVUG06445@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> X-Authentication-Warning: NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk: beer set sender to bounce@NOSPAM.dyndns.dk using -f From: Barry Bouwsma To: FreeBSD Hardware Wizards References: <200311050441.hA54fhJ54978@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> <200311210043.hAL0hDu01322@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> <20031121194845.GA87408@pit.databus.com> Subject: Re: USB camera compatibility question X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 21:32:38 -0000 [Drop my (IPv6-only) address if replying; I'll catch the archives] You wrote: > On Fri, Nov 21, 2003 at 01:43:13AM +0100, Barry Bouwsma wrote: > > > > Yes, because so far the images snarfed with my hacks are okay for the > > first 4096 bytes, thereafter failing to match the perfect images I can > > download with the `mtools' utilities from a printer cum card slot. > > There seem to be chunks of NULs present regularly throughout the file. > The "junk at byte 4097" symptom matches what I get with a Sony F707 > on -current using the OHCI usb controller. I believe it's a bug in > the ohci driver but don't know more than that. You may well be right. And either it fixed itself, or I've been `cmp'ing against a mis-labelled ``bad/good'' reference file. What I did in my frustration was to throw hardware around and swap in a UHCI+EHCI controller card I had, also to verify my memory of my EHCI performance. At that point, I saw no difference between the saved `good' image and that downloaded directly from the camera. Other issues with that driver caused me to revert to the OHCI+EHCI controller (also that it has firewire that I need too). Then it worked Just Right, and has never given me problems since, though with relative little use. This suddenly-working-after-trying-different-uhci-controller phenomenon also sounds like what I saw when trying to use libusb to talk to the printer I have, where I had no total success, until I swapped controller cards, then it suddenly started working, and continued after switching back to the ohci card. Don't ask me to understand this. Also, for a USB1 device and an msdos type filesystem, I see what I am led to understand is reasonable transfer rates of more than half the theoretical maximum speed, about which I shall not complain -- certainly beats the `mtools' access to the printer that I had had to use previously. I have vague memories of the uhci card giving transfer rates about ten times slower, but I could be confused with all the hardware juggling going on and trying to keep track of all the differences, expected and unexpected. Others are welcome to comment on these observations. I also may have used different usb-related kernel module sources, as I've been juggling more of those around based on -stable and -current of various vintages. Sheesh, I need to clean up my system -- I thought I was running the code based on -current since the last boot, but it turns out it's September-RELENG_4 ... Now I can't even remember what I was using when I saw the 4k problem, furrfu. thanks, Barry Bouwsma