From: Andres Salomon <dilinger@queued.net>
To: Daniel Drake <dsd@laptop.org>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] OLPC: Only enable PCI configuration type override on XO-1
Date: Thu, 23 Sep 2010 16:39:04 -0700 [thread overview]
Message-ID: <20100923163904.7fd9a790@debxo> (raw)
In-Reply-To: <20100923162805.0F6549D401B@zog.reactivated.net>
Looks good to me!
Acked-by: Andres Salomon <dilinger@queued.net>
On Thu, 23 Sep 2010
17:28:04 +0100 (BST) Daniel Drake <dsd@laptop.org> wrote:
> This configuration type override is for XO-1 only and must not happen
> on XO-1.5.
>
> Signed-off-by: Daniel Drake <dsd@laptop.org>
> ---
>
> Replaces earlier patches:
> [PATCH 1/3] OLPC: extended board revision detection
> [PATCH 2/3] PCI: OLPC configuration cleanup
>
> Due to the fact that CONFIG_OLPC is associated with multiple laptop
> models (not only the XO-1), it makes sense to keep this as a separate
> configuration option.
>
> We decided against adding functions to distinguish between
> XO-1/XO-1.5 as we don't want to encourage laptop checking in this
> way. There should only be one or two cases where this actually
> matters (here is one of them).
>
> arch/x86/Kconfig | 2 +-
> arch/x86/kernel/olpc.c | 6 ++++--
> arch/x86/pci/olpc.c | 2 +-
> 3 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index cea0cd9..0ed4c9b 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1900,7 +1900,7 @@ config PCI_GODIRECT
> bool "Direct"
>
> config PCI_GOOLPC
> - bool "OLPC"
> + bool "OLPC XO-1"
> depends on OLPC
>
> config PCI_GOANY
> diff --git a/arch/x86/kernel/olpc.c b/arch/x86/kernel/olpc.c
> index 0e0cdde..635888c 100644
> --- a/arch/x86/kernel/olpc.c
> +++ b/arch/x86/kernel/olpc.c
> @@ -242,8 +242,10 @@ static int __init olpc_init(void)
> (unsigned char *) &olpc_platform_info.ecver,
> 1);
> #ifdef CONFIG_PCI_OLPC
> - /* If the VSA exists let it emulate PCI, if not emulate in
> kernel */
> - if (!cs5535_has_vsa2())
> + /* If the VSA exists let it emulate PCI, if not emulate in
> kernel.
> + * XO-1 only. */
> + if (olpc_platform_info.boardrev < olpc_board_pre(0xd0) &&
> + !cs5535_has_vsa2())
> x86_init.pci.arch_init = pci_olpc_init;
> #endif
>
> diff --git a/arch/x86/pci/olpc.c b/arch/x86/pci/olpc.c
> index b348154..13700ec 100644
> --- a/arch/x86/pci/olpc.c
> +++ b/arch/x86/pci/olpc.c
> @@ -304,7 +304,7 @@ static struct pci_raw_ops pci_olpc_conf = {
>
> int __init pci_olpc_init(void)
> {
> - printk(KERN_INFO "PCI: Using configuration type OLPC\n");
> + printk(KERN_INFO "PCI: Using configuration type OLPC
> XO-1\n"); raw_pci_ops = &pci_olpc_conf;
> is_lx = is_geode_lx();
> return 0;
next prev parent reply other threads:[~2010-09-23 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 16:28 [PATCH 1/2] OLPC: Only enable PCI configuration type override on XO-1 Daniel Drake
2010-09-23 20:04 ` [tip:x86/olpc] x86, olpc: " tip-bot for Daniel Drake
2010-09-23 23:39 ` Andres Salomon [this message]
2010-09-24 18:03 ` [PATCH 1/2] OLPC: " Jesse Barnes
2010-09-24 19:06 ` H. Peter Anvin
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=20100923163904.7fd9a790@debxo \
--to=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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