From owner-freebsd-hackers Sat May 27 3: 7:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id BED0E37B88D for ; Sat, 27 May 2000 03:07:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 12vdVO-0009dq-0Y; Sat, 27 May 2000 11:07:42 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA69266; Sat, 27 May 2000 11:14:49 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 27 May 2000 11:13:18 +0100 (BST) From: Doug Rabson To: Joy Ganguly Cc: freebsd-hackers Subject: Re: S5933 PCI Adapter..?? In-Reply-To: <392E9C0E.4B9EB0FB@falcon.niksun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 May 2000, Joy Ganguly wrote: > hi all, > > i have a atm oc3 care which uses the amcc S5933 PCI adapter. however the > driver reports "unable to map mem" at boot time. i used pciconf to read > the configuration space base address registers and all of them showed > 0x00000000. however when i write all 1's t the base registers they give > me the proper mask. the device and vendor id configuration registers > show the right values. i think the bios is unable to assign physical > addresses. > > how can i solve this problem?? one way out is to have the driver assign > physical addresses to map the pci space. however for that i need the > physical map...what data structure holds that?? Can you check your BIOS and make sure it does *not* think you have a Plug-n-Play OS. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message