From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261668AbUBYWdD (ORCPT ); Wed, 25 Feb 2004 17:33:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261655AbUBYWc7 (ORCPT ); Wed, 25 Feb 2004 17:32:59 -0500 Received: from apegate.roma1.infn.it ([141.108.7.31]:10117 "EHLO apona.ape") by vger.kernel.org with ESMTP id S262328AbUBYWaQ (ORCPT ); Wed, 25 Feb 2004 17:30:16 -0500 Message-ID: <403D21F6.4080504@roma1.infn.it> Date: Wed, 25 Feb 2004 23:30:14 +0100 From: Davide Rossetti User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Re: Intel vs AMD x86-64 References: <8D4D7D09D4DA5F41BF3905582CF84ACB5D7068@tbanausc3a.dynextechnologies.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds wrote: >On Tue, 24 Feb 2004, Sean Fao wrote: > > >>Linus Torvalds wrote: >> >> >>>Now, I'm not above complaining about Intel (in fact, the Intel people seem >>>to often think I hate them because I'm apparently the only person who gets >>>quoted who complains about bad decisions publicly), but at least I try to >>>avoid complaining before-the-fact ;) >>> >>> >>> >>It must come with the territory ;-). Your message has already made it to >>Slashdot so I'm sure this time will be no different. >> >> > >Yeah, and that's unfair to Intel. They've done the right thing >technically, and I applaud them for that, but their marketing people are >pricks. > >Everybody else is "Intel-compatible" when they make x86 chips. Intel is >apparently a bit too used to _not_ saying "AMD-compatible". > >Oh, well. The marketing people are probably proud of their "branding", and >screw the confusion. > > actually, the real hungry peaple should be the Intel engineering staff who have been working on the first "ia32e" chip... they started working on it let's say 1, 1.5 years ago, maybe 2 or more??? I bet chip design-to-silicon time is not 6 months even for Intel... I kind of see Intel marketing people pressing on them saying: "... in the end it's just a backup project, just in case ia64, which is more money making, does not take off...". Maybe they already had a designed "x86 64bit" chip, only more different from AMD64 one, but they were forced to refactor it to make it x86-64 compatible.