From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Olivier Galibert <galibert@pobox.com>
Cc: linux-kernel@vger.kernel.org, Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] update MMConfig patches w/915 support
Date: Mon, 8 Jan 2007 13:22:46 -0800 [thread overview]
Message-ID: <200701081322.47481.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20070108203212.GA15481@dspnet.fr.eu.org>
On Monday, January 8, 2007 12:32 pm, Olivier Galibert wrote:
> > The routines could probably be consolidated into a single
> > probe_intel_9xx routine or something, but I really looked at that
> > yet (though there are many similarities between the 91[05], 945 and
> > 965 families, they may not be enough that the code would actually
> > be simpler if shared.
>
> The individual functions are so simple, it's probably way better for
> maintainance simplicity to keep them separate, at least for now.
Yeah, sounds good.
> > + pci_conf1_read(0, 0, PCI_DEVFN(0,0), 0x48, 4, &pciexbar);
> > +
> > + /* No enable bit or size field, so assume 256M range is enabled.
> > */ + len = 0x10000000U;
> > + pci_mmcfg_config_num = 1;
> > +
> > + pci_mmcfg_config = kzalloc(sizeof(pci_mmcfg_config[0]),
> > GFP_KERNEL); + pci_mmcfg_config[0].base_address = pciexbar;
>
> Hmmm, I'd mask out the reserved bits if I were you. Paranoia :-)
Wouldn't hurt I suppose, want me to post a new patch?
Thanks,
Jesse
prev parent reply other threads:[~2007-01-08 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 19:42 Jesse Barnes
2007-01-07 19:44 ` Jesse Barnes
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 [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=200701081322.47481.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome