From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 12 18:21:09 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AA7A16A59C; Wed, 12 Dec 2007 18:21:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id C14E813C4EE; Wed, 12 Dec 2007 18:21:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8r) with ESMTP id 224131964-1834499 for multiple; Wed, 12 Dec 2007 13:21:11 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lBCIKvC5082643; Wed, 12 Dec 2007 13:21:01 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org, cokane@freebsd.org Date: Wed, 12 Dec 2007 13:11:06 -0500 User-Agent: KMail/1.9.6 References: <4759730F.6090302@FreeBSD.org> In-Reply-To: <4759730F.6090302@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712121311.06777.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 12 Dec 2007 13:21:02 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/5104/Wed Dec 12 11:42:07 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Subject: Re: Overlapping PCI Memory Locations X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2007 18:21:09 -0000 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: 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: 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. -- John Baldwin