From owner-freebsd-current  Mon Mar 12  0:10:49 2001
Delivered-To: freebsd-current@freebsd.org
Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3F45937B71B; Mon, 12 Mar 2001 00:10:41 -0800 (PST)
	(envelope-from sobomax@FreeBSD.org)
Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112])
	by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f2C8ARJ02259;
	Mon, 12 Mar 2001 10:10:28 +0200
Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1])
	by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f2C8ATG84687;
	Mon, 12 Mar 2001 10:10:29 +0200 (EET)
	(envelope-from sobomax@FreeBSD.org)
Message-ID: <3AAC8474.186B4D58@FreeBSD.org>
Date: Mon, 12 Mar 2001 10:10:28 +0200
From: Maxim Sobolev <sobomax@FreeBSD.org>
Organization: Vega International Capital
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: uk,ru,en
MIME-Version: 1.0
To: Kris Kennaway <kris@obsecurity.org>,
	Mario Sergio Fujikawa Ferreira <lioux@uol.com.br>,
	freebsd-current@FreeBSD.org, jkh@FreeBSD.org
Subject: Re: make.conf lack of CPUTYPE=k6-3 support
References: <200103120646.f2C6kjp84242@vic.sabbo.net>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Maxim Sobolev wrote:

> >
> >
> > --AhhlLboLdkugWU4S
> > Content-Type: text/plain; charset=us-ascii
> > Content-Disposition: inline
> > Content-Transfer-Encoding: quoted-printable
> >
> > On Mon, Mar 12, 2001 at 12:29:58AM -0300, Mario Sergio Fujikawa Ferreira wr=
> > ote:
> > > Hi,
> > >=20
> > >     Is there anything against adding support for
> > > k6-3 to the just added CPUTYPE mechanism? :)
> > >     My little machine feels left out. Hehehhe
> > >     I made a simple patch to etc/defaults/make.conf
> > > and share/mk/bsd.cpu.mk
> > >     Should I have touched anything else?
> > >=20
> > >     Regards,
> > >=20
> > > ps: I think this can be MFCed asap (even during the
> > > veil period) since it is very straightforward.
> >
> > Looks fine to me. I'll commit it.
>
> I see no reason for it. k6-3 is essentially k6-2 core with extra cache on
> chip. Threre are no other significant differencies in the features or
> instruction set.

Not even to mention that there is such a beast as k6-2+....

I would suggest to rename k6-2 into k6/3dnow (similarly to what we have for
i586/mmx) and put a note saying that k6/3dnow should be used for k6-2/k6-2+/k6-3.

-Maxim


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message