From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 11:52:32 2004 Return-Path: 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 7F31416A4F4 for ; Sun, 25 Jan 2004 11:52:32 -0800 (PST) Received: from server.vk2pj.dyndns.org (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD28743D1F for ; Sun, 25 Jan 2004 11:52:30 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])i0PJqOPf045945; Mon, 26 Jan 2004 06:52:24 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.12.10/8.12.10/Submit) id i0PJqOck045944; Mon, 26 Jan 2004 06:52:24 +1100 (EST) (envelope-from peter) Date: Mon, 26 Jan 2004 06:52:24 +1100 From: Peter Jeremy To: freebsd-current@freebsd.org Message-ID: <20040125195224.GA45925@server.vk2pj.dyndns.org> References: <20040124074052.GA12597@cirb503493.alcatel.com.au> <20040125143203.G29442@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040125143203.G29442@gamplex.bde.org> User-Agent: Mutt/1.4.1i Subject: Re: 80386 support in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 19:52:32 -0000 On Sun, Jan 25, 2004 at 05:28:31PM +1100, Bruce Evans wrote: >SMP is now in GENERIC, so support for it is more important than when >I386_CPU was removed from GENERIC. > >The ifdef tangle for this stuff combined with lack of testing seems to >have broken the 386 support in practice. Interesting. Does anyone on this list actually use -CURRENT on a 386? Unfortunately(?) my 386 laptop died terminally some years ago (the HDD died and the BIOS only supports 80MB and 120MB HDDs) and my 386 motherboard collection got trashed last year as part of a move. > Libraries are now chummy with >the kernel implementation of atomic operations, but not chummy enough to >know when it actually works in userland. libthr uses the kernel >atomic_cmpset_*(), but this never works on plain i386's in userland >(the I386_CPU version doesn't work unless the application gains i/o >privilege since it uses cli/sti, and the !I386_CPU version doesn't >work because it uses cmpxchg). Is it time to bite the bullet and fully desupport the 80386? It looks like threads don't work and it's likely that other bitrot will set in in the absence of active testing. Peter