From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ingo Molnar <mingo@elte.hu>
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 10:13:10 +0100 [thread overview]
Message-ID: <20090626101310.4110a290@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090626071955.GG14078@elte.hu>
> 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
- Embedded x86 like devices are going to regularly occur without any PCI
- You need to know the platform in order to know how to access any PCI
bus that may or may not hypothetically exist.
Take a look at how ARM and PPC address this. They do it via platform
features and descriptors for good reason.
One thing PPC does nice is to encapsulate pretty much all of it into a
struct of function pointers for each platform to keep the if conditionals
down. The ARM file layout of arch/foo/platform/bar might also be a good
idea before mrst and olpc and other stuff like this starts to make the
main x86 directory hard to read ?
Alan
next prev parent reply other threads:[~2009-06-26 9:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 0:14 Pan, Jacob jun
2009-06-26 7:19 ` Ingo Molnar
2009-06-26 9:13 ` Alan Cox [this message]
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
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=20090626101310.4110a290@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hpa@linux.intel.com \
--cc=jacob.jun.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®