summaryrefslogtreecommitdiffstats
path: root/sys/scsi
Commit message (Collapse)AuthorAgeFilesLines
* This commit fixes various 64bit portability problems required fordfr1998-06-0710-31/+31
| | | | | | | | | | FreeBSD/alpha. The most significant item is to change the command argument to ioctl functions from int to u_long. This change brings us inline with various other BSD versions. Driver writers may like to use (__FreeBSD_version == 300003) to detect this change. The prototype FreeBSD/alpha machdep will follow in a couple of days time.
* Allow devfs to support the 'uk' devicejulian1998-06-011-3/+27
| | | | Submitted by: Micha Class <michael_class@hp.com>
* Add sctargattach that initializes the bufq data structure.gibbs1998-06-011-9/+21
|
* Reformat some comments to not overflow 80 chars.julian1998-05-241-69/+63
|
* An effort to make SLICE/DEVFS play with SCSI.julian1998-05-071-79/+102
| | | | | | | | Apparently I didn't make my plans to make dev_t and devsw[] go away under DEVFS quite clear enough to Peter Dufault as he stitched the SCSI system together using them when he redid the configuration side of things. This made is rather an effort to remove all vestiges of dev_t and devsw[] entries from sd.c in DEVFS/SLICE mode.
* cleanup: remove duplicated dump code.julian1998-05-071-125/+39
| | | | fix oversight on SLICE ioctl code.
* Add dump support to the DEVFS/slice code.julian1998-05-061-2/+101
| | | | | | now we can actually catch our crashes :-) Submitted by: Luoqi Chen <luoqi@chen.ml.org> (the man who's everywhere)
* The CHIOGSTATUS ioctl of the SCSI media changer driver (sys/scsi/ch.c)phk1998-05-061-2/+2
| | | | | | | | | is broken. It omits the SCSI_DATA_IN flag in the SCSI READ ELEMENT STATUS command, which makes the 'chio status' command fail. PR: 6528 Reviewed by: phk Submitted by: Hans Huebner <hans@artcom.de>
* Fixed spelling of "fictitious" in diagnostics and commentsdes1998-04-273-13/+13
| | | | PR: kern/6429
* close() is no longer a SLICE method.julian1998-04-221-4/+11
| | | | | Close is simply an open with no-read and no-write once internal to SLICE (it still exports a close to the rest of the kernel)
* Add changes and code to implement a functional DEVFS.julian1998-04-191-6/+207
| | | | | | | | | | | | | | | | | | | | | This code will be turned on with the TWO options DEVFS and SLICE. (see LINT) Two labels PRE_DEVFS_SLICE and POST_DEVFS_SLICE will deliniate these changes. /dev will be automatically mounted by init (thanks phk) on bootup. See /sys/dev/slice/slice.4 for more info. All code should act the same without these options enabled. Mike Smith, Poul Henning Kamp, Soeren, and a few dozen others This code does not support the following: bad144 handling. Persistance. (My head is still hurting from the last time we discussed this) ATAPI flopies are not handled by the SLICE code yet. When this code is running, all major numbers are arbitrary and COULD be dynamically assigned. (this is not done, for POLA only) Minor numbers for disk slices ARE arbitray and dynamically assigned.
* Seventy-odd "its" / "it's" typos in comments fixed as per kern/6108.des1998-04-176-14/+14
|
* Attempt to fix BOUNCE_BUFFERS. I cannot test these drivers, but theypeter1998-04-162-2/+54
| | | | | seem to compile OK with the bounce buffer mods. I have only visually checked for missing bounce buffer support, I could have missed some.
* Attempt to get bounce_buffers working again for per-process kernel stackpeter1998-04-161-10/+40
| | | | | | data targets. At least st0 works for me again.... Also, scsi_scsi_cmd() looks like it's been exiting without a biodone() on an attached buffer in a number of error cases, leading to locked buffers.
* fix an obvious broken BOUNCE_BUFFER case.peter1998-04-161-1/+9
|
* Support compiling with `gcc -ansi'.bde1998-04-154-8/+8
|
* Add an ioctl to retrieve the next writable address.jmz1998-03-312-19/+109
| | | | | | Defer the WRITE SESSION command until the first write command, so that it works like the prepare track command, allowing the device to be closed after the command.
* Moved some #includes from <sys/param.h> nearer to where they are actuallybde1998-03-281-1/+2
| | | | used.
* Add a quirk entry for IO DATA CDC-TX86 6 CD changer.jkh1998-03-081-1/+6
| | | | | PR: 5942 Submitted by: Masanao Sasai <m_sasai@mxa.meshnet.ne.jp>
* Don't depend on "implicit int".bde1998-02-201-2/+2
|
* Put the SC_Q_NO_TAGS value in the correct field for the Iomega Jaz quirkmsmith1998-02-181-5/+5
| | | | | entry, and move it down with the other NO_TAGS device. Submitted by: bde
* Add HW_WDOG to LINT, and turn it into a new-style option.eivind1998-02-161-1/+2
|
* Based on the following message, disable tagged command queueing for allmsmith1998-02-161-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Iomaga Jaz drives. From: Steve Logue <stevel@mail.cdsnet.net> To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Subject: Jaz Drives / Tagged Command Queuing FreeBSD Lists, Due to my own problems as the owner of a Jaz drive, I have gotten word from Iomega that confirms the state of Tagged Command Queuing as the underlying problem. There is an error in all Jaz, and Jaz2 drives prior to BIOS level J.86 that has not shipped yet. Read the following, and make the appropriate corrections to your system present, and future: > Steve, > > I got a very fast response from the hardware engineer (Jaz and Jaz 2 > designer). The problem is this - The Jaz drive does not support > command queing, and revisions older than J.86 do not report it correctly. > For example, when your SCSI adapter says "I'm going to use command > queing" to the Jaz drive, the drive answers "OK, lets go", even though its > not supported. The J.86 drives will now answer "Sorry, command > queing is not supported". Iomega does not have any current plans to > support command queing. > > Thank's for your report, I will continue to forward it to the hardware > engineers. -STEVEl -- --------------------------------------------------------------------- Steve Logue http://home.cdsnet.net/~stevel Systems Integration nettek LLC --------------------------------------------------------------------- Submitted by: Steve Logue <stevel@mail.cdsnet.net>
* Staticize.eivind1998-02-091-2/+2
|
* Serves me right for committing code late at night...wollman1998-02-011-3/+9
| | | | | | Fix the SCIOCGETDEVINFO code so that it compiles, and while I'm at it, add support for human-readable device names so that I don't have to call devname(3) on the scd->dev to get it.
* Add a new ioctl, SCSIOCGETDEVINFO, which takes a device ID and uses itwollman1998-02-011-2/+16
| | | | | | | to look up information about that device. Right now, all it does is give back the dev_t for the device, if known, since that's all I needed, but hopefully the SCSI mavens will come up with a more generally useful structure.
* Make all file-system (MFS, FFS, NFS, LFS, DEVFS) related option new-style.eivind1998-01-249-9/+20
| | | | | | | | This introduce an xxxFS_BOOT for each of the rootable filesystems. (Presently not required, but encouraged to allow a smooth move of option *FS to opt_dontuse.h later.) LFS is temporarily disabled, and will be re-enabled tomorrow.
* Add SCSI-SCSI RAID from Infotrand as known deviceache1998-01-211-1/+5
|
* the pt driver should make one DEVFS entry for each one found rather thanjulian1998-01-061-20/+22
| | | | just one for the whole system..
* - Accept all models of the HP C1553A tape series as usable tapes. Thisnate1997-12-301-2/+2
| | | | | is necessary for my tape drive to be found, since it's apparently a later model.
* move punchline of joke up to rest of joke. (got moved by useful edits)julian1997-12-301-5/+5
|
* If available, use the device's LOGICAL blocksize as reported byjulian1997-12-291-53/+69
| | | | | | | | | | | | | the "READ_CAPACITY" command, rather than the physical blocksize reported in the physical geometry code-page. Also don't print out worrying bogus messages when probing a device that has no media. There's no point in printing out something that is unknowable. It just confuses things. Move the check for valid blocksize out of 'open()' to the subroutine that actually finds this out, thus probe/attach can also report and act on the problem.
* back out previous commitjulian1997-12-281-24/+13
| | | | got a better version.
* Move the sector size check to the right place,julian1997-12-281-14/+25
| | | | | also cope with some drives that return funny values. The correct fix will come in a few days.
* Fix some breakage that prevented the Plasmon burners from being usedjoerg1997-12-261-67/+66
| | | | | | | | | | | | | | | | | | under -current. The actual preparation of the next track will now be deferred until just before the first write operation. Otherwise, opening the device with write intent will cause the execution of commands that are illegal in `limited command set mode' (i.e., after the write channel has been opened). While i was at it, cleaned up the worm_open() function a bit. Removed the volume overflow pre-check in worm_strategy(). It was time-consuming, and rather useless in many cases anyway (with the size being reported for just the entire volume only), so we can as well let the actual SCSI command fail instead, where it'll properly be reported as EIO. Partially submitted by & discussed with: jmz
* Add a PARITITON arg to SCSI_MKFIXED, and use it tobrian1997-12-232-5/+10
| | | | | | specify RAW_PART for the suopen() in sscioctl(). Now you can `scsi -f /dev/ssc -p'.
* Duplicate the entry for the Plasmon CD-R device, so both possibilitiesjoerg1997-12-201-4/+7
| | | | | (read/only and write/once) will be covered. This is necessary in order to fill in the proper device information record.
* Protect against a null pointer dereferencation in the case of anjoerg1997-12-201-1/+12
| | | | | | | unknown drive. Such a drive will be configured by worm(4) nevertheless (albeit with a warning), but cannot be opened except of the SCSI control device (so scsi(8) or cdrecord will continue to work).
* Ifdefed some conditionally used declarations.bde1997-12-202-2/+6
|
* Removed a stray semicolon.bde1997-12-201-2/+1
|
* Allow slow SCSI CDROMs more time to start up.jraynard1997-12-141-1/+13
| | | | | PR: 5181 Submitted by: Wilko Bulte <wilko@yedi.iaf.nl>
* Use ENOIOCTL instead of -1 (= ERESTART) for diskslice ioctls that arebde1997-12-062-4/+4
| | | | not handled at a particular level.
* In all such uses of struct buf: 's/b_un.b_addr/b_data/g'phk1997-12-028-17/+17
|
* Fixed misuse of O_ACCMODE. Cosmetic.bde1997-11-231-2/+2
| | | | Not fixed in: sound driver
* Fixed the sector size frobbing in sd_strategy() at least not tobde1997-11-231-8/+7
| | | | | | | | break for the usual sector size. dscheck() adjusts b_bcount to handle EOF, so we must scale it and not preserve it. i/o beyond the end of partitions has been broken since rev.1.96. Not fixed in: od driver
* Remove a bunch of variables which were unused both in GENERIC and LINT.phk1997-11-071-1/+6
| | | | Found by: -Wunused
* Make the Nakamichi CD-ROM changer detection detect more recent devices,joerg1997-11-061-2/+2
| | | | too.
* Use a MODE SELECT command to reset the block size, instead of calling thejmz1997-10-271-13/+33
| | | | prepare_track() function, which caused fixation problems with some drives.
* Make the Sun OEM version of the DLT a known multi-LUN device so changersjoerg1997-10-191-1/+5
| | | | | | | will work. PR: kern/4802 Submitted by: dawes@physics.usyd.edu.au (David Dawes)
* Remove the call to scsi_start_unit() from sd_open(). It was causingjoerg1997-10-122-8/+9
| | | | | | | | | | | | | | much grieve to owners of IBM drives when used in conjunction with tagged command queuing, and didn't serve any purpose at all (since experiments have proven that it simply didn't work). Instead, call scsi_start_unit() once in sd_attach(), so in case the drive has been configured to `remote start', it will spin up there. (If it has spun down later, it must have been because of administrator action (scsi(8)) anyway.) While i was at it, bump the timeout for scsi_start_unit() to 30 seconds. 10 seconds were way too few for most drives.
OpenPOWER on IntegriCloud