Jesse Barnes wrote:
On Monday, April 30, 2007 4:20 pm Robert Hancock wrote:
Right, but you patch should obsolete this stuff anyway. I'll test
it out in the next few days.
We likely still want this chipset-specific support, it will catch the
case where the MCFG table lists a location which is r
On Monday, April 30, 2007 4:20 pm Robert Hancock wrote:
> > Right, but you patch should obsolete this stuff anyway. I'll test
> > it out in the next few days.
>
> We likely still want this chipset-specific support, it will catch the
> case where the MCFG table lists a location which is reserved in
Jesse Barnes wrote:
On Sunday, April 29, 2007 7:10 pm Robert Hancock wrote:
Jesse Barnes wrote:
Add support for Intel 915 bridge chips to the new PCI MMConfig
detection code. Tested and works on my sole 915 based platform (a
Toshiba laptop). I added register masking per Oliver's suggestion,
a
On Sunday, April 29, 2007 7:10 pm Robert Hancock wrote:
> Jesse Barnes wrote:
> > Add support for Intel 915 bridge chips to the new PCI MMConfig
> > detection code. Tested and works on my sole 915 based platform (a
> > Toshiba laptop). I added register masking per Oliver's suggestion,
> > and mov
Jesse Barnes wrote:
Add support for Intel 915 bridge chips to the new PCI MMConfig detection
code. Tested and works on my sole 915 based platform (a Toshiba laptop). I
added register masking per Oliver's suggestion, and moved the __init
qualifier to after the 'static const char' to match Ogawa-
5 matches
Mail list logo