From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267896AbUBRTNY (ORCPT ); Wed, 18 Feb 2004 14:13:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267899AbUBRTNX (ORCPT ); Wed, 18 Feb 2004 14:13:23 -0500 Received: from vitelus.com ([64.81.243.207]:54414 "EHLO vitelus.com") by vger.kernel.org with ESMTP id S267896AbUBRTNU (ORCPT ); Wed, 18 Feb 2004 14:13:20 -0500 Date: Wed, 18 Feb 2004 11:13:12 -0800 From: Aaron Lehmann To: Mikael Pettersson Cc: Kernel Mailing List Subject: Re: Intel vs AMD x86-64 Message-ID: <20040218191312.GQ5809@vitelus.com> References: <16435.14044.182718.134404@alkaid.it.uu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16435.14044.182718.134404@alkaid.it.uu.se> User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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.