Date: Tue, 05 May 1998 15:03:11 -0700 From: Julian Elischer <julian@whistle.com> To: Hans Huebner <hans@artcom.de> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ch.c: CHIOGSTATUS is broken - How should I fix it? Message-ID: <354F8C9F.794BDF32@whistle.com> References: <Pine.BSF.3.96.980505191042.17499A-100000@transrapid.artcom.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hans Huebner wrote: > > Hello there, > > today I moved our Q47 DLT robot from an SGI to a FreeBSD we intend to > dedicate to backups. The Q47 talks SCSI-2, thus I assumed that the ch > driver included with FreeBSD should do fine to control the thing. > Unfortunatly, the 'chio status' command did not work. I tracked the > problem down to a bug in the driver - The SCSI_DATA_IN flag in the > scsi_scsi_cmd call is missing, and as such the driver is unable to > transfer the status information from the robot. This was easy to fix, of > course. > > As our DLT robot has a barcode reader, I now intend to add a way to read > the complete status information including the barcode label information > from the robot. Currently, only a restricted set of flags can be read > through the ch driver into the user mode application. > > This raises the question whether I should actually add a new ioctl (say > CHIOGSTATUSEXT) to the ch driver or change the current meaning of the > CHIOGSTATUS call to return complete status information to the calling > application. > > The first option would be transparent to binaries making use of the > current ch interface, but it would add another ioctl which does behave > similar to CHIOGSTATUS, only better. The second option could be > implemented with source-level compatibility, requiring a recompile for > applications which use the current interface, but it would also keep the > ch driver free from redundancy. > > Given that most FreeBSD users use only software they have the source for, > I'd rather change CHIOSTATUS to be smarter. This will only affect a few, > if any, users of the ch driver since CHIOCSTATUS is currently broken > anyhow. > > By the way: If anyone volunteers to commit the updated ch driver, I'd > promise a manual page update for ch(4) as well ;) > > Opinions, anyone? so few people have these devices that anyone who has one is encouraged to submit patches and fixes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?354F8C9F.794BDF32>