Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Oct 2004 11:42:34 -0700
From:      "David O'Brien" <obrien@freebsd.org>
To:        Ruslan Ermilov <ru@freebsd.org>, cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org
Subject:   Re: cvs commit: src/lib/libc/i386/net htonl.S ntohl.S
Message-ID:  <20041018184234.GC10529@dragon.nuxi.com>
In-Reply-To: <20041018183118.GA80703@falcon.midgard.homeip.net>
References:  <200410181719.i9IHJa9l097436@repoman.freebsd.org> <20041018173516.GB89681@ip.net.ua> <20041018174511.GA6079@dragon.nuxi.com> <20041018183118.GA80703@falcon.midgard.homeip.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 18, 2004 at 08:31:18PM +0200, Erik Trulsson wrote:
> On Mon, Oct 18, 2004 at 10:45:11AM -0700, David O'Brien wrote:
> > Yes.  You missed the discussion in freebsd-current on this?
..
> I have certainly not seen any message stating that on -current.

 To: freebsd-current@freebsd.org
 Subject: [PATCH] optimizing X now that we don't support i386 CPU's on 6-CURRENT
 Message-ID: <20041016174925.GA96809@dragon.nuxi.com>

 
> I know that the GENERIC kernel does not work on a i386, so that you
> need a custom-built kernel to install on a real i386.
> I also know that support for FPU-less systems has been dropped, which
> means that most 386-based systems (those without an '387) (as well as
> systems with a 486sx w/o a 487sx) will not run RELENG_5 or -CURRENT.
> 
> Neither of these means that a real 80386+80387 is unsupported, just
> that you need to build a new kernel first.

I see nothing wrong with having to build a new userland before it will
run on I386 since we already have to do that with the kernel.


> I think you people need to decide to either drop support for 80386
> completely (in which case all the '#ifdef I386_CPU' and similar can go
> away) or decide to keep support for it, in which case most things
> should just work 'out of the box' on a 80386 (without recompilation
> needed more than absolutely necessary.)

That is a whole nother issue, and I welcome you to bring it up in
freebsd-arch@ (vs. as a follow up to this commit) where all can debate
it.

-- 
-- David  (obrien@FreeBSD.org)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041018184234.GC10529>