From owner-freebsd-hackers  Thu Jul 30 14:29:14 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA28127
          for freebsd-hackers-outgoing; Thu, 30 Jul 1998 14:29:14 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27969;
          Thu, 30 Jul 1998 14:28:36 -0700 (PDT)
          (envelope-from se@dialup124.zpr.uni-koeln.de)
Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124])
	by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id XAA14237;
	Thu, 30 Jul 1998 23:28:21 +0200 (MET DST)
Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id TAA03507; Thu, 30 Jul 1998 19:08:44 +0200 (CEST)
X-Face: "<d]#=8pzx);RzeqSKI86OVa7=!0/(uRa.+B.9Z9\eNUn@UG?!`y7yt2dFNn%k4'.}](uE%
 yCO)$e&Y1%3EO~ifu6Q-#YUM&JZ't,}JkPnAz,8Dj33u%@GBi%[Y#LHz$]h7a<p4)-jKI7~sKjlP-^
 EvA[G;]v&0]W!EL%shs,{7x0|oqN4YVIs5,NI#,V{9"WF):5&RkOhyj*#-IAG}Tnu;YCF,d
Message-ID: <19980730190843.A3467@mi.uni-koeln.de>
Date: Thu, 30 Jul 1998 19:08:43 +0200
From: Stefan Esser <se@FreeBSD.ORG>
To: Chris Csanady <cc@tarsier.ca.sandia.gov>, hackers@FreeBSD.ORG
Cc: Stefan Esser <se@FreeBSD.ORG>
Subject: Re: pci_map_mem() failing..
Mail-Followup-To: Chris Csanady <cc@tarsier.ca.sandia.gov>,
	hackers@FreeBSD.ORG
References: <199807281922.MAA12801@tarsier.ca.sandia.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93i
In-Reply-To: <199807281922.MAA12801@tarsier.ca.sandia.gov>; from Chris Csanady on Tue, Jul 28, 1998 at 12:22:35PM -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 1998-07-28 12:22 -0700, Chris Csanady <cc@tarsier.ca.sandia.gov> wrote:
> This is my second try at sending this message.. the first one did not
> seem to get through. :\
> 
> Anyways.. I am working on a device driver, and so far have not been able to
> get this seemingly simple aspect of it to work.  I am getting the following
> error:
> 	pci_map_mem failed: bad memory type=0xfffff004
> 
> It seems that the pci code does not know how to handle 64bit cards.  If
> I yank the lines in pci.c that check the memory type, it produces no
> errors, although the mapping still does not work.  What am I missing
> here?
> 
> This is on a 2.2.6 box.

Ummm, I see ...

Well, this should work under 3.0-current, but I didn't 
find a card to actually verify this ... ;-)

It shouldn't be too hard to make the 2.2.x PCI code deal
with 64bit maps, provided the high address bits are just
zero (I expect the address to be "unsigned").

I'll try to provide you with a patch, which will DTRT if
the map register is 64 bits long and the map resides in
the first 4GB of address space.

Sorry, I'm still overloaded (fetched mail from my ISP for
the first time after more than a week for lack of time all
those previous days ...) and it may be only after the weekend
that I can offer a fix ...

Regards, STefan

PS: I'd love to know whether the PCI code in -current can
    deal with that 64 bit map. If you can't boot a -current
    kernel, then please send "pciconf -r" results for the 
    map registers of that device (instructions on request :)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message