From owner-freebsd-current Fri Feb 28 13:10:32 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49B2837B401 for ; Fri, 28 Feb 2003 13:10:31 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52CD943FCB for ; Fri, 28 Feb 2003 13:10:30 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h1SLAQaa056632; Fri, 28 Feb 2003 22:10:26 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: "M. Warner Losh" Cc: current@FreeBSD.ORG Subject: Re: Any ideas why we can't even boot a i386 ? From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 28 Feb 2003 14:06:13 MST." <20030228.140613.25161750.imp@bsdimp.com> Date: Fri, 28 Feb 2003 22:10:26 +0100 Message-ID: <56631.1046466626@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20030228.140613.25161750.imp@bsdimp.com>, "M. Warner Losh" writes: >Also, 386-core based chips are still in production (or have been in >the last year). It has only been very recently that the embedded >chips have transitioned to 486. Calling them, as others have, 10 >years obsolete is a bit of an overstatement... My main concern would be if the chips have the necessary "umphf" to actually do a real-world job once they're done running all the overhead of 5.0-R. The lack of cmpxchg8 makes the locking horribly expensive. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message