ADC: MUP desired behavior

Banther, Michael michael.banther at hp.com
Fri Mar 4 11:16:53 PST 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Banther, Michael" <michael.banther at hp.com>
*
This is a multi-part message in MIME format.

------_=_NextPart_001_01C520EE.B91F64BD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

 Hi Kevin,

I agree with Paul.

Regards,
Michael Banther
Hewlett-Packard Ltd.
Telephone +44 (117) 312-9503


-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of
Paul.A.Suhler at certance.com
Sent: 02 March 2005 12:58
To: Kevin D Butt
Cc: owner-t10 at t10.org; t10 at t10.org
Subject: Re: ADC: MUP desired behavior

* From the T10 Reflector (t10 at t10.org), posted by:
* Paul.A.Suhler at certance.com
*

Hi, Kevin.

My opinion is that if the drive (not automation) front panel allows
confirmation that the inserted cartridge is indeed a microcode
cartridge, then that should be considered equivalent to setting the MUE
bit and the update should proceed.  I guess that means that the
protection is against your first option, automated insertion, although
"unconfirmed insertion"
might be a better term for what's being prevented.

Perhaps in ADC-2 we should amend the description to include means =
beyond
the scope of the standard, blah blah blah.

Cheers,

Paul
+++++++++++++++++++++++++
Paul Suhler
Firmware Engineer
Quantum Corporation
1650 Sunflower Avenue
Costa Mesa, California  92626
(714) 641-2485 (voice)
(714) 966-7328 (fax)


=20

                      "Kevin D Butt"

                      <kdbutt at us.ibm.co        To:       t10 at t10.org

                      m>                       cc:

                      Sent by:                 Subject:  ADC: MUP
desired behavior                                                    =20
                      owner-t10 at t10.org

=20

=20

                      03/02/2005 07:37

                      AM

=20

=20






ADC guru's,

The MUP bit is defined as:
<< A microcode update protect (MUP) bit set to one shall prevent the DT
device from performing a microcode update process upon the loading of a
medium containing a microcode image. A MUP bit set to zero shall not
prevent the DT device from performing a microcode update process upon
the loading of a medium containing a microcode image. >>

Is the intent of this bit only to protect against automated insertion =
or
is it also intended to protect against manual attempts such as through =
a
drive maintenance panel (i.e. A user manually sets the drive for a =
ucode
update through a drive panel and then a cartridge is inserted)?

Thanks,

Kevin D. Butt
Fibre Channel & SCSI Architect, IBM Tape Firmware, 6TYA, 9000 S. Rita
Rd., Tucson, AZ  85744 Tie-line 321; Office: 520-799-5280, Lab:
799-5751, Fax: 799-4138, Email:
kdbutt at us.ibm.com





*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


------_=_NextPart_001_01C520EE.B91F64BD
Content-Type: text/x-vcard;
	name="BANTHER,MICHAEL (HP-UnitedKingdom,ex2).vcf"
Content-Transfer-Encoding: base64
Content-Description: BANTHER,MICHAEL (HP-UnitedKingdom,ex2).vcf
Content-Disposition: attachment;
	filename="BANTHER,MICHAEL (HP-UnitedKingdom,ex2).vcf"

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOkJBTlRIRVI7TUlDSEFFTA0KRk46QkFOVEhFUixN
SUNIQUVMIChIUC1Vbml0ZWRLaW5nZG9tLGV4MikNCk9SRzpIUC1Vbml0ZWRLaW5nZG9tLGV4MjtD
NjAwLTUzMDINClRFTDtXT1JLO1ZPSUNFOjMxMi05NTAzDQpURUw7V09SSztWT0lDRTorNDQgMTE3
IDMxMiA5NTAzDQpBRFI7V09SSzo7TVMgMkIyMjs7QlJJU1RPTCwgR0INCkxBQkVMO1dPUks7RU5D
T0RJTkc9UVVPVEVELVBSSU5UQUJMRTpNUyAyQjIyPTBEPTBBQlJJU1RPTCwgR0INCkVNQUlMO1BS
RUY7SU5URVJORVQ6bWljaGFlbF9iYW50aGVyQGhwLmNvbQ0KUkVWOjIwMDMwNzE3VDA4Mjk0OFoN
CkVORDpWQ0FSRA0K

------_=_NextPart_001_01C520EE.B91F64BD--





More information about the T10 mailing list