Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 May 1996 20:07:41 -0700 (PDT)
From:      "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
To:        joerg_wunsch@uriah.heep.sax.de
Cc:        scsi@FreeBSD.ORG, handy@sag.space.lockheed.com
Subject:   Re: Exabyte Tape Drive Firmware
Message-ID:  <199605170307.UAA07489@GndRsh.aac.dev.com>
In-Reply-To: <199605161045.MAA01593@uriah.heep.sax.de> from J Wunsch at "May 16, 96 12:45:02 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
> As Brian N. Handy wrote:
> 
> > I just called TTI with this same question.  I'm not at all clear on if
> > I'll ever even have to do a firmware upgrade.  At any rate, the way they
> > said firmware updates are handled is just by spinning a special firmware
> > upgrade tape in the drive. 
> 
> That's surprising.  SCSI-2 has precautions for downloading firmware
> (it's done via a WRITE BUFFER command), so i wonder why they didn't
> pick this route?  I know that at least the Exabyte 2502 drives do use
> WRITE BUFFER.

Picking the WRITE BUFFER route would require them to support N operating
systems and M controllers, it is much simpler for the vendor to support
a ``stuff this tape in your drive and magic will happen''.  It works no
matter what OS your using, and no matter what controller.

Archive/Conner does this for the Python DAT drive series as well.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605170307.UAA07489>