The Design and Implementation of the FreeBSD Operating System, Second Edition
Now available: The Design and Implementation of the FreeBSD Operating System (Second Edition)


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]

FreeBSD/Linux Kernel Cross Reference
sys/dev/isa/README.seagate

Version: -  FREEBSD  -  FREEBSD-13-STABLE  -  FREEBSD-13-0  -  FREEBSD-12-STABLE  -  FREEBSD-12-0  -  FREEBSD-11-STABLE  -  FREEBSD-11-0  -  FREEBSD-10-STABLE  -  FREEBSD-10-0  -  FREEBSD-9-STABLE  -  FREEBSD-9-0  -  FREEBSD-8-STABLE  -  FREEBSD-8-0  -  FREEBSD-7-STABLE  -  FREEBSD-7-0  -  FREEBSD-6-STABLE  -  FREEBSD-6-0  -  FREEBSD-5-STABLE  -  FREEBSD-5-0  -  FREEBSD-4-STABLE  -  FREEBSD-3-STABLE  -  FREEBSD22  -  l41  -  OPENBSD  -  linux-2.6  -  MK84  -  PLAN9  -  xnu-8792 
SearchContext: -  none  -  3  -  10 

    1 #       $NetBSD: README.seagate,v 1.3 2003/05/03 18:11:25 wiz Exp $
    2 
    3 The hardware:
    4 
    5 The ST01/02, and Future Domain 950 are very simple SCSI controllers. They are
    6 not busmastering, so the processor must do all transfers a la IDE. They support
    7 blind transfer by adding wait states (up to a certain limit). Interrupt is
    8 generated for reconnect and parity errors (maybe also for some other events).
    9 
   10 The card consists of one command port that writes to scsi control lines, reads
   11 status lines, and a data port that read/writes to the 8 data lines. The address
   12 decoding gives both data and control ports large memory areas to a single
   13 port. This is used by the code.
   14 
   15 The ST01/02 differs from the FD950 in memory address location and SCSI id.
   16 
   17 Probing for the card:
   18 
   19 A card is recognized by comparing the BIOS signature with known signatures. A
   20 new card may not be recognized if the BIOS signature has changed. Please send
   21 new signatures to me.
   22 
   23 Driver function:
   24 
   25 A scsi command is sent to scsi_cmd function. The command is either placed in
   26 the queue or an retryable message is returned. The routine may wait for
   27 completion of the command depending on the supplied flags. A timer is started
   28 for every command placed in the queue. The commands are added in the order they
   29 are received. There is a possiblity to make all REQUEST SENSE commands be
   30 queued before all other commands, but I dont think it is a good thing (Linux
   31 do however use this). 
   32 
   33 The card is mostly controlled by the sea_main function. It is called by
   34 scsi_cmd, the interrupt routine, and the timeout routine. The sea_main routine
   35 runs as long there are something to do (transfer data, issue queued commands,
   36 and handle reconnected commands).
   37 
   38 The data transfers may be done in two different ways: Blind and polled
   39 transfers. They differ in the way the driver does it handshaking with the
   40 target. During a blind transfer, the driver code blindly transfers a block
   41 of data without checking for changed phase. During polled transfers, the
   42 phase is checked between every character transfered. The polled transfers
   43 are always used for status information and command transfers.
   44 
   45 Because the card does not use DMA in any way, there is no need to handle
   46 physical addresses. There is no problem with the isa-bus address limit of
   47 16MB, making bounce-buffers unnecessary.
   48 
   49 The data structures:
   50 
   51 Every card has a sea_softc structure keeping the queues of commands waiting to
   52 be issued, and commands currently disconnected. The type of card (Seagate or
   53 Future Domain), data and control port addresses, scsi id, busy flags for all
   54 possible targets, and interrupt vector for the card.
   55 
   56 Every scsi command to be issued are stored in a sea_scb structure. It contains
   57 a flag describing status/error of the command, current data buffer position,
   58 and number of bytes remaining to be transfered.
   59 
   60 
   61 PROBLEMS
   62 
   63 I have had problems getting the ST02 boot using the boot floppies. I think it
   64 is some problem with BIOS calls not working. It is unfortunately impossible to
   65 disconnect the ST02 floppy controller.
   66 
   67 I have had problem to get the driver talk to a 40 MB Seagate disk. I dont have
   68 access to it any more, so I can't do any more checks on that.
   69 
   70 NOTE: The ST02 creates its own description of the disk attached. This is not
   71 the same as the disk says. This translation problem may cause problems when
   72 sharing a disk between both DOS and BSD. It is however not impossible.

Cache object: c6e611fe8d889e1d11cf6be8e3d4a48a


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]


This page is part of the FreeBSD/Linux Linux Kernel Cross-Reference, and was automatically generated using a modified version of the LXR engine.