From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Pan, Jacob jun" <jacob.jun.pan@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags
Date: Fri, 26 Jun 2009 20:45:36 +0200 [thread overview]
Message-ID: <20090626184536.GA30885@elte.hu> (raw)
In-Reply-To: <20090626095119.15067a53@jbarnes-g45>
* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Fri, 26 Jun 2009 09:19:55 +0200
> Ingo Molnar <mingo@elte.hu> wrote:
> > > void platform_feature_init_default(int subarch_id)
> > > {
> > > - printk(KERN_INFO "Use default X86 platform feature set\n");
> > > + if ((subarch_id >= 0) && (subarch_id < N_X86_SUBARCHS)) {
> > > + if (subarch_id == X86_SUBARCH_MRST) {
> > > + setup_mrst_default_feature();
> > > + return;
> > > + }
> > > + } else {
> > > + printk(KERN_INFO "Use default X86 platform feature
> > > set\n");
> > > + }
> > > }
> >
> > Why dont we have some clean and robust PCI config space based
> > enumeration instead of this boot ID based thing?
>
> MRST has special PCI support that depends on having the platform
> identified already, so if you want to use something other than a
> flag here, maybe we could use an SFI string instead.
An SFI flag would be nicer than any PCI space method i guess - if it
can be accessed early enough.
Ingo
prev parent reply other threads:[~2009-06-26 18:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 0:14 [PATCH 3/9] x86/moorestown: add moorestown platform flags Pan, Jacob jun
2009-06-26 7:19 ` Ingo Molnar
2009-06-26 9:13 ` Alan Cox
2009-06-26 9:38 ` Ingo Molnar
2009-06-26 10:16 ` Alan Cox
2009-06-26 11:04 ` Ingo Molnar
2009-06-26 11:56 ` Alan Cox
2009-06-26 12:22 ` Ingo Molnar
2009-06-26 12:33 ` Alan Cox
2009-06-26 12:51 ` Ingo Molnar
2009-06-26 13:34 ` Alan Cox
2009-06-26 14:44 ` Ingo Molnar
2009-06-26 14:29 ` Ingo Molnar
2009-06-26 16:32 ` Thomas Gleixner
2009-06-26 16:54 ` Jesse Barnes
2009-06-30 6:35 ` Pavel Machek
2009-07-01 17:25 ` Jesse Barnes
2009-07-01 20:48 ` Ingo Molnar
2009-06-26 15:00 ` Ingo Molnar
2009-06-26 16:51 ` Jesse Barnes
2009-06-26 18:45 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090626184536.GA30885@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@linux.intel.com \
--cc=jacob.jun.pan@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox