From owner-freebsd-i386@FreeBSD.ORG Wed Feb 27 05:35:28 2008 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1C7D106566C for ; Wed, 27 Feb 2008 05:35:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 54D7913C45B for ; Wed, 27 Feb 2008 05:35:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8s) with ESMTP id 233535434-1834499 for multiple; Wed, 27 Feb 2008 00:33:40 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m1R5ZNcl026652; Wed, 27 Feb 2008 00:35:24 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: be_works_us Date: Wed, 27 Feb 2008 00:35:31 -0500 User-Agent: KMail/1.9.7 References: <418265.66662.qm@web58613.mail.re3.yahoo.com> In-Reply-To: <418265.66662.qm@web58613.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802270035.31617.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 27 Feb 2008 00:35:24 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/6006/Tue Feb 26 20:03:40 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-i386@freebsd.org Subject: Re: i386/119491: [i386] [patch] [request] padlock enable for new VIA C7 (CentaurHauls) cpuid 0x6d0 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 05:35:28 -0000 On Tuesday 26 February 2008 11:26:28 pm be_works_us wrote: > Thanks jhb. > > > I seem , > > + goto via_common; > + case 0x6d0: > + strcpy(cpu_model, "VIA C7 Eden"); > the name of "VIA C7 Eden" is confusing. > (Eden is a platform name?) > > "http://www.via.com.tw/en/products/processors/c7/" > says new C7 processor is "VIA C7 Esther C5J". Its not clear if the Esther C5J is the 0x6a0 that was already supported or the 0x6d0 that is this new CPU. I couldn't find any docs that explain the CPUID steppings for VIA CPUs, do you know of any? > And , > I want you to add correct cpu support flags on the /src/share/mk/bsd.cpu.mk > > i.e. > > MACHINE_CPU = k5 i586 i486 i386 > . elif ${CPUTYPE} == "c3" > MACHINE_CPU = 3dnow mmx i586 i486 i386 > . elif ${CPUTYPE} == "c3-2" > MACHINE_CPU = sse mmx i586 i486 i386 > /* new support for VIA Esther C5J */ > . elif ${CPUTYPE} == "c5j" > MACHINE_CPU = sse3 sse2 sse mmx i686 i586 i486 i386 > > > if you can do it. Seemingly this should be for 'c7' rather than 'c5j'? We use 'c3' for the VIA C3 Nehemiah rather than 'c5p'. -- John Baldwin