Does anyone know if the kernel has any issues running on a platform that
provides SMBIOS v2.5?
Thanks,
Dan Yeisley
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.
On Wed, 2007-03-21 at 16:57 -0700, Greg KH wrote:
> On Wed, Mar 21, 2007 at 09:37:52AM -0400, Daniel Yeisley wrote:
> > On Tue, 2007-03-20 at 13:26 -0700, Greg KH wrote:
> > > On Tue, Mar 20, 2007 at 01:25:38PM -0400, Daniel Yeisley wrote:
> > > > On Tue, 2007-03-20
On Tue, 2007-03-20 at 13:26 -0700, Greg KH wrote:
> On Tue, Mar 20, 2007 at 01:25:38PM -0400, Daniel Yeisley wrote:
> > On Tue, 2007-03-20 at 11:00 -0700, Greg KH wrote:
> > > On Tue, Mar 20, 2007 at 12:18:24PM -0400, Daniel Yeisley wrote:
> > > > It has been menti
It has been mentioned before that large systems with a lot of PCI buses
have issues with the 64k I/O space limit. The ES7000 has a BIOS option
to either assign I/O space to all adapters, or only to those that need
it. A list of supported adapters that don't need it is kept in the
BIOS. When this
On Tue, 2007-03-20 at 11:00 -0700, Greg KH wrote:
> On Tue, Mar 20, 2007 at 12:18:24PM -0400, Daniel Yeisley wrote:
> > It has been mentioned before that large systems with a lot of PCI buses
> > have issues with the 64k I/O space limit. The ES7000 has a BIOS option
> > to ei
There's an existing quirk for the kernel to use 1k IO space granularity
on the Intel P64H2. It turns out however that pci_setup_bridge() in
drivers/pci/setup-bus.c reads in the IO base and limit address register
masks it off to the nearest 4k, and writes it back. This causes the
kernel to be on 1
6 matches
Mail list logo
