Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758249AbZFZMcK (ORCPT ); Fri, 26 Jun 2009 08:32:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753043AbZFZMcD (ORCPT ); Fri, 26 Jun 2009 08:32:03 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:39936 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752482AbZFZMcB (ORCPT ); Fri, 26 Jun 2009 08:32:01 -0400 Date: Fri, 26 Jun 2009 13:33:18 +0100 From: Alan Cox To: Ingo Molnar Cc: "Pan, Jacob jun" , "linux-kernel@vger.kernel.org" , "H. Peter Anvin" Subject: Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags Message-ID: <20090626133318.5b8de81b@lxorguk.ukuu.org.uk> In-Reply-To: <20090626122254.GA9959@elte.hu> References: <43F901BD926A4E43B106BF17856F07556412B7E2@orsmsx508.amr.corp.intel.com> <20090626071955.GG14078@elte.hu> <20090626101310.4110a290@lxorguk.ukuu.org.uk> <20090626093859.GA12571@elte.hu> <20090626111603.758ec7fb@lxorguk.ukuu.org.uk> <20090626110429.GB12446@elte.hu> <20090626125653.5e30bae4@lxorguk.ukuu.org.uk> <20090626122254.GA9959@elte.hu> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1694 Lines: 47 > That's a pretty bogus claim - on x86 a bootloader generally knows > very little about 'what it is running on'. We do most of the > enumeration in early platform code and retrieve information via > standard BIOS interfaces. Stop thinking about existing x86 PC systems running grub for a bit. Highly embedded systems usually boot from ROM firmware direct into the kernel. They have a very good idea what they are running on because they were flashed specifically for the device. I'm not worried about PC/ISA v PC/MCA v Voyager v CBus v CompaqSMP v Intel MP 1.4 SMP v PCI v PCI/X v PCI Express v OLPC v Voyager etc, we can clearly tell all those apart via bus probing. But those are all basically a PC. > > How about "they tried other methods and they didn't work" > > The thing is, you are trying to defend a v1 patch-set here that is > really indefensible: it's ugly and deficient in numerous smaller and > larger details. I outlined numerous deficiencies already - and i'll > review v2 too to see what else is there to fix. No I'm trying to understand what you actually want the thing to look like. Are we talking /* Fixed struct not pointer for speed */ struct platform_ops platform_ops; memcpy(platform_ops, platform_op_list[detect_platform_type()], sizeof(struct platform_ops)); platform->add_private_resources(); platform->timer_foo(); platfomr->timer_bar(); or platform->init(); timer = platform->timer; timer->begin() -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/