From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264313AbUBSGCL (ORCPT ); Thu, 19 Feb 2004 01:02:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264919AbUBSGCL (ORCPT ); Thu, 19 Feb 2004 01:02:11 -0500 Received: from aun.it.uu.se ([130.238.12.36]:60072 "EHLO aun.it.uu.se") by vger.kernel.org with ESMTP id S264313AbUBSGCJ (ORCPT ); Thu, 19 Feb 2004 01:02:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16436.20830.133480.544844@alkaid.it.uu.se> Date: Thu, 19 Feb 2004 07:02:06 +0100 From: Mikael Pettersson To: Aaron Lehmann Cc: Kernel Mailing List Subject: Re: Intel vs AMD x86-64 In-Reply-To: <20040218191312.GQ5809@vitelus.com> References: <16435.14044.182718.134404@alkaid.it.uu.se> <20040218191312.GQ5809@vitelus.com> X-Mailer: VM 7.17 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Aaron Lehmann writes: > On Wed, Feb 18, 2004 at 10:56:44AM +0100, Mikael Pettersson wrote: > > What about naming? IA-64 is taken, AMD64 is too specific, Intel's > > "IA-32e" sounds too vague, and I find x86-64 / x86_64 difficult to type. > > "x64" perhaps? > > I feel that AMD64 is appropriate. We've been calling all the AMD/Cyrix > chips IA32 processors, and this is no different. Actually I would call them x86, never IA32.