From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 11:38:59 +0200 [thread overview]
Message-ID: <20090626093859.GA12571@elte.hu> (raw)
In-Reply-To: <20090626101310.4110a290@lxorguk.ukuu.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > Why dont we have some clean and robust PCI config space based
> > enumeration instead of this boot ID based thing?
>
> That strikes me as a rather dumb question given that
It's an entirely legitimate question, given that many other current
modern subarchitectures detect themselves based on PCI config space
early accesses or (sometimes) BIOS data structures - and that both
of those methods are better than using boot flags.
> - Embedded x86 like devices are going to regularly occur without
> any PCI
This proposed Intel subarchitecture comes with PCI support,
obviously.
> - You need to know the platform in order to know how to access any
> PCI bus that may or may not hypothetically exist.
Uhm, not really.
Have a look at arch/x86/kernel/early-quirks.c. All you generally
need to know is a PCI ID that sits on the root bus.
Early PCI ID checks are typical and robust way to identify 'weird'
subarchitectures. Sometimes we do it via BIOS data structures. Only
as a last option do we want to use boot loader mechanisms - it's the
most inflexible one really.
Furtherore, Moorestown comes with SFI and there sure can be a BIOS
table that describes the platform properly. We can read such tables
very early during bootup, well before platform devices are set up.
Ingo
next prev parent reply other threads:[~2009-06-26 9:39 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 [this message]
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
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=20090626093859.GA12571@elte.hu \
--to=mingo@elte.hu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@linux.intel.com \
--cc=jacob.jun.pan@intel.com \
--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