[PATCH 08/12] i5k_amb: Load automatically on all 5000/5400 chipsets

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 09, 2008 at 01:43:53PM +0200, Jean Delvare wrote:

> sure why the AMB device would be any different. How comes that the PCI
> devices know the AMB memory address if they aren't related? If the PCI
> devices do not own this memory mapping, who does?

On _most_ of my systems it's listed in the ACPI DSDT as one of the
"system board resources" (SBD1).  Unfortunately, this SBD1 object lists
a bunch of memory regions and I/O ports, without any indication of what
each of those regions is for, other than "not for general OS use".  It's
a little confusing here--the PCI config register has ultimate control
over where the region lives, but ACPI claims it as part of its own
system board "do not use" map.

I suppose it wouldn't be hard to do this with a pci_device_id and
MODULE_DEVICE_TABLE instead of a direct MODULE_ALIAS.  But since I only
need the PCI device for a brief moment I'm trying to avoid bloating the
driver with all the pci_driver support code.

--D




[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux