From owner-freebsd-hackers Mon Jun 23 13:46:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29541 for hackers-outgoing; Mon, 23 Jun 1997 13:46:52 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA29515; Mon, 23 Jun 1997 13:45:53 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-1.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA26597 (5.67b/IDA-1.5); Mon, 23 Jun 1997 22:44:21 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id WAA06203; Mon, 23 Jun 1997 22:44:18 +0200 (CEST) X-Face: " Date: Mon, 23 Jun 1997 22:44:17 +0200 From: Stefan Esser To: Chris Csanady Cc: hackers@FreeBSD.ORG, Stefan Esser Subject: Re: pci_map_mem failed... References: <199706201726.MAA15908@friley01.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199706201726.MAA15908@friley01.res.iastate.edu>; from Chris Csanady on Fri, Jun 20, 1997 at 12:26:11PM -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 20, Chris Csanady wrote: > I am working on an ethernet driver, but when I try to > map the cards registers, I get the following.. > > pci_map_mem failed: device's memrange 0x6100-0x61ff is incompatible with its > bridge's memrange 0x2000000-0xffffffff > > There seems to be some comment in German in pci.c about > this case, so I was wondering if something is broken.. Well, don't worry about that comment in German. I put it in, when I was not sure about a reported problem being real, but that comment is of no good use to anybody anymore :) > If not, what am I doing wrong here? The address range seems to be invalid for a memory mapped region, since it obviously conflicts with system RAM. As somebody else already mentioned, this might actually be a port map, but there should have been a warning that you are trying to map a "bad memory type". Please send me a *verbose* boot message log and your attach code, at least the part that contains the call to pci_map_mem(). This will allow me to understand what's going on ... Regards, STefan