From owner-freebsd-hackers Tue Oct 10 18:15:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id B15DD37B66C for ; Tue, 10 Oct 2000 18:15:14 -0700 (PDT) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA14781; Wed, 11 Oct 2000 10:45:05 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 11 Oct 2000 10:45:05 +0930 (CST) From: "Daniel O'Connor" To: Torbjorn Kristoffersen Subject: RE: Programming a USB driver Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Oct-00 Torbjorn Kristoffersen wrote: > It obviously found something there. Would it be hard to make a driver for > this camera? I would really appreciate some starting places and tips. If you can work out what the wire protocol is, you should be able to write a userland driver using the ugen driver. The ugen driver is a 'catch all' for USB drivers with no explicit kernel driver. I guess a good place to start would be to find the Linux driver which hopefully has source and read that. Then start fiddling :) As far as I understand it, each USB device has several 'end points' which can be different types, and the ugen driver allows access to these end points as different devices (eg ugen0.0 ugen0.1 etc). You can then open these (make sure you get the read/write'ness correct). The only experience I have with USB is a camera whose USB protocol is *identical* to the serial one :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message