From owner-freebsd-arch Tue Nov 14 11:42: 7 2000 Delivered-To: freebsd-arch@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id A816337B4C5; Tue, 14 Nov 2000 11:42:05 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp245.osd.bsdi.com [204.216.28.245]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAEJflB96057; Tue, 14 Nov 2000 11:41:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200011141936.MAA49406@harmony.village.org> Date: Tue, 14 Nov 2000 11:42:17 -0800 (PST) From: John Baldwin To: Warner Losh Subject: Re: RANDOMDEV inspired realitycheck regarding i386/i486... Cc: arch@FreeBSD.org, Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Nov-00 Warner Losh wrote: > In message John Baldwin writes: >: What is the current processor of choice for embedded stuff? Is x86 even a >: good architecture for embedded work? That is the only place that I would >: see >: the 386 still being alive... > > Timing Solutions has several 486 based machines. There are very few > 386 machines out there still in the SBC arena, but I understand that > the 386EX is still alive and kicking in the "put a cpu on the board" > market. > > The random device seeding issue is still a problem. It must complete > in << 10 s on slow hardware and << 1s on fast hardware. Mark Murray > and I talked about this at BSDcon and he indicated to me that he'll be > fixing the speed aspect of it soon, or at least in the fullness of time. > > Warner Would anyone have a heart attack if we removed I386_CPU from GENERIC but did not remove the 386 code? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message