Date: Wed, 12 Dec 2007 14:30:49 -0500 From: Coleman Kane <cokane@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hardware@freebsd.org Subject: Re: Overlapping PCI Memory Locations Message-ID: <476036E9.9010002@FreeBSD.org> In-Reply-To: <200712121311.06777.jhb@freebsd.org> References: <4759730F.6090302@FreeBSD.org> <200712121311.06777.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------010007030104080402060906
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
John Baldwin wrote:
> On Friday 07 December 2007 11:21:35 am Coleman Kane wrote:
>
>> Hi,
>>
>> I've got a problem where two components on my system have overlapping
>> PCI memory regions:
>>
>> atapci0: <ATI ATA controller> port
>>
> 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem
> 0xd0609000-0xd06093ff irq 16 at device 18.0 on pci0
>
>> atapci0: [ITHREAD]
>>
>> pcm0: <ATI SB600 High Definition Audio Controller> mem 0xd0608000-0xd060bfff
>>
> irq 16 at device 20.2 on pci0
>
>> pcm0: hdac_mem_alloc: Unable to allocate memory resource
>>
>>
>>
>> Because of this, I cannot use the sound hardware on this system. In
>> addition, the memory range used by atapci0 is the SATA AHCI space. The
>> ata-chipset.c doesn't currently identify the ATI IXP600 SATA controller
>> (just the paired PATA controller), so I can actually use my drives
>> through the PATA/IDE compatibility registers in the I/O space. However,
>> if I modify ata-chipset.c to add support for the IXP600 SATA controller,
>> I get weird results using ATA_INL(..) calls, which look like something
>> is interfering with the data I *should* be getting from the SATA mem space.
>>
>> In addition, the pcm0 refuses to attach, as above.
>>
>> Also, this is a notebook and has one of those crummy notebook BIOSes
>> that don't allow fiddling with this sort of stuff in BIOS. Is there any
>> facility in the kernel to force these to be remapped (or to perform the
>> mappings ourselves and ignore what BIOS tells us)?
>>
>
> No. You can hack the pci driver to zero out the BAR in either device during
> boot though as a test.
>
What would the kernel do if the BAR were to be zeroed out?
I applied the attached fixup to sys/dev/pci/pci.c that allows me to
specify the desired base address from a loader.conf tunable. Is there a
better way? Is there a project to make a better way?
--
Coleman Kane
--------------010007030104080402060906
Content-Type: text/x-patch;
name="pci.c-hp6715b.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="pci.c-hp6715b.diff"
--- sys/dev/pci/pci.c.orig 2007-12-08 23:57:21.000000000 -0500
+++ sys/dev/pci/pci.c 2007-12-09 22:34:05.000000000 -0500
@@ -2235,6 +2235,9 @@
& PCIM_CMD_MEMEN) != 0;
}
+static unsigned int hp6715b_membase_for_hd_audio = 0;
+TUNABLE_INT("hw.pci.hp6715b_membase_for_hd_audio", &hp6715b_membase_for_hd_audio);
+
/*
* Add a resource based on a pci map register. Return 1 if the map
* register is a 32bit map register or 2 if it is a 64bit register.
@@ -2267,6 +2270,12 @@
ln2size = pci_mapsize(testval);
ln2range = pci_maprange(testval);
base = pci_mapbase(map);
+ if((pci_get_devid(dev) == 0x43831002) && (hp6715b_membase_for_hd_audio != 0)) {
+ device_printf(dev, "Applying PCI membase fixup for HDA Audio on an HP 6715b notebook to: %08x\n",
+ hp6715b_membase_for_hd_audio);
+ base = (pci_addr_t)hp6715b_membase_for_hd_audio;
+ pci_write_config(dev, 0x10, base | 4, 4);
+ }
barlen = ln2range == 64 ? 2 : 1;
/*
--------------010007030104080402060906--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?476036E9.9010002>