From owner-cvs-all Tue Jul 18 12: 1: 0 2000 Delivered-To: cvs-all@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EC76137B9F3; Tue, 18 Jul 2000 12:00:52 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA32162; Tue, 18 Jul 2000 12:00:39 -0700 Date: Tue, 18 Jul 2000 12:00:32 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alexander Langer Cc: Jeroen Ruigrok van der Werven , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/isp asm_pci.h isp.c isp_freebsd.c isp_freebsd.h isp_inline.h isp_target.c isp_target.h isp_tpublic.h ispmbox.h ispreg.h ispvar.h src/sys/pci isp_pci.c In-Reply-To: <20000718205154.A9257@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Revision Changes Path > > > 1.4.2.9 +13964 -26356src/sys/dev/isp/Attic/asm_pci.h > > Curious one. Intended or I am missing something very subtle here? > > Well, obviously this is just true - he changed the Firmware revision > :) (a firmware in source is -- uhm - WEIRD! :) No, it's not. It is microcode which, if I had the source to, I could actually *fix* some of the !)$*!)*$~)@$~)$~)$)~_@$!)_ problems I've had to program around in the driver instead of taking another incoming from Qlogic that fixes problem #B only to unfix problem #B that was fixed last week. > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/isp/Attic/asm_pci.h.diff?r1=1.4.2.8&r2=1.4.2.9 > > > - * Firmware Version 7.65.00 (14:17 Jul 20, 1999) > + * Firmware Version 7.55.00 (16:16 Mar 20, 1998) > */ > -#define ISP_1040_RISC_CODE isp_1040_risc_code > static const u_int16_t isp_1040_risc_code[] = { > - 0x0078, 0x103a, 0x0000, 0x4057, 0x0000, 0x2043, 0x4f50, > 0x5952, > *thousandsoflines* > > I wonder if he wrote that manually :) Yes, I did. Sure. Like I have time to even answer this thread..... This reminds me of when we put SparcStation 1 into manufacturing- somebody over in EB4 in Milpitas *insisted* that we do a hex dump of the boot prom and print it out because that was what they would be putting into the safe room that manufacturing maintained as 'gold copies' of stuff. This of course raised the question of "Should a disaster occur and you have to re-enter this, who're you gonna get to type in (and *validate*) the four inches thick of printout of hex numbers?" -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message