From owner-freebsd-alpha Mon Oct 11 12:34:28 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.netbsd.org (redmail.netbsd.org [155.53.200.193]) by hub.freebsd.org (Postfix) with SMTP id 4D16C15ACE for ; Mon, 11 Oct 1999 12:34:08 -0700 (PDT) (envelope-from cgd@netbsd.org) Received: (qmail 7133 invoked by uid 1000); 11 Oct 1999 19:34:07 -0000 To: Wilko Bulte Cc: freebsd-alpha@freebsd.org (FreeBSD-alpha mailing list) Subject: Re: DEC3000/400 SRM bootp overview References: <199910111913.VAA01776@yedi.iaf.nl> From: cgd@netbsd.org (Chris G. Demetriou) Date: 11 Oct 1999 12:34:07 -0700 In-Reply-To: Wilko Bulte's message of Mon, 11 Oct 1999 21:13:49 +0200 (CEST) Message-ID: <87ln9966a8.fsf@redmail.netbsd.org> Lines: 25 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > * SRM 7.0 (latest available revision) > - does not do BOOTP correctly, "? T_ERR_NI - RECEIVE_TIMEOUT" > - this rev is useless for bootp network boot > > * SRM 6.9 > - does not do BOOTP correctly, "? T_ERR_NI - RECEIVE_TIMEOUT" > - this rev is useless for bootp network boot There are similar issues with some versions of the firmware for 3000/300 models, too. I ran into them when I was developing the NetBSD/alpha code at CMU. I/we pushed on it a bit with various contacts that we had at DEC, and it came back that apparently the SRM folks said that it was due to a "hardware problem"... never mind that previous revisions of the firmware worked fine. "stupid, stupid, stupid." cgd -- Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html Disclaimer: Not speaking for NetBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message