All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: linux-kernel@vger.kernel.org
Cc: Olivier Galibert <galibert@pobox.com>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] update MMConfig patches w/915 support
Date: Sun, 7 Jan 2007 11:44:16 -0800	[thread overview]
Message-ID: <200701071144.16045.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <200701071142.09428.jbarnes@virtuousgeek.org>

On Sunday, January 07, 2007 11:42 am, Jesse Barnes wrote:
> This patch updates Oliver's MMConfig bridge detection patches with
> support for 915G bridges.  It seems to work ok on my 915GM laptop.
>
> I also tried adding 965 support, but it doesn't work (at least not on my
> G965 box).  When I enable MMConfig support when the register value is
> 0xf00000003 (should be a 256M enabled window at 0xf0000000) the box
> hangs at boot, so I'm not sure what I'm doing wrong...

For reference, here's the probe routine I tried for 965, probably something 
dumb wrong with it that I'm not seeing atm.

static __init const char *pci_mmcfg_intel_965(void)
{
	u64 pciexbar, mask = 0, len = 0;
	u32 lo, hi;

	pci_mmcfg_config_num = 1;

	pci_conf1_read(0, 0, PCI_DEVFN(0,0), 0x60, 4, &lo);
	pci_conf1_read(0, 0, PCI_DEVFN(0,0), 0x64, 4, &hi);
	pciexbar = ((u64)hi << 32) | lo;

	/* Enable bit */
	if (!(pciexbar & 1))
		pci_mmcfg_config_num = 0;

	/* Size bits */
	switch ((pciexbar >> 1) & 3) {
	case 0:
		mask = 0xff0000000UL;
		len  = 0x10000000U;
		break;
	case 1:
		mask = 0xff8000000UL;
		len  = 0x08000000U;
		break;
	case 2:
		mask = 0xffc000000UL;
		len  = 0x04000000U;
		break;
	default:
		pci_mmcfg_config_num = 0;
	}

	if (pci_mmcfg_config_num) {
		pci_mmcfg_config = kzalloc(sizeof(pci_mmcfg_config[0]),
					   GFP_KERNEL);
		pci_mmcfg_config[0].base_address = pciexbar & mask;
		pci_mmcfg_config[0].pci_segment_group_number = 0;
		pci_mmcfg_config[0].start_bus_number = 0;
		pci_mmcfg_config[0].end_bus_number = (len >> 20) - 1;
	}

	return "Intel Corporation G965 Express Memory Controller Hub";
}

Thanks,
Jesse

P.S.  Hooray for Intel for publishing their bridge specs!  Makes stuff like 
this a bit easier.

  reply	other threads:[~2007-01-07 19:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07 19:42 [PATCH] update MMConfig patches w/915 support Jesse Barnes
2007-01-07 19:44 ` Jesse Barnes [this message]
2007-01-08 20:45   ` Olivier Galibert
2007-01-08 21:27     ` Jesse Barnes
2007-01-16 19:28       ` Olivier Galibert
2007-01-22 21:55         ` Jesse Barnes
2007-01-08 20:32 ` Olivier Galibert
2007-01-08 21:22   ` Jesse Barnes

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=200701071144.16045.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=arjan@infradead.org \
    --cc=galibert@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.