Date: Fri, 31 May 1996 13:59:54 -0400 (EDT) From: Peter Dufault <dufault@hda> To: grog@lemis.de (Greg Lehey) Cc: hackers@FreeBSD.org Subject: Re: Mustek/Paragon 6000CX scanner: Any help with SCSI ioctls? Message-ID: <199605311759.NAA06805@hda> In-Reply-To: <199605311242.OAA26369@allegro.lemis.de> from "Greg Lehey" at May 31, 96 02:42:43 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> ..., on the other hand the man pages scsi([34]) > leave a lot to the imagination. I can probably fight my way through > (*and* I'm prepared to fix the man pages), but if somebody has > anything else they can point me to, I'd be very grateful. If you can find a scsi spec then scsi(3) will make more sense to you, since it assumes you can figure out what the fields in the scsi_request structure do based on familiarity with SCSI. Here is a url for an HTML one: http://abekas.com:8080/SCSI2/ It looks almost easy to port that Linux application. You could cut it in at the "scsi_cmd" call, setting up our scsireq structure and doing scsireq_enter. One problem will be figuring out where commands end and data begins - the Linux interface writes by sending a command followed by data in one write call and reads by writing the command and then reading back data. Our interface has command, command length, data, data length, and direction members in the structure. I'll send a sketch privately. -- Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605311759.NAA06805>