Subject: Re: fxp - unable to map device registers
To: Manuel Bouyer <bouyer@antioche.eu.org>
From: Adam Glass <adam@clarity.net>
List: port-i386
Date: 04/15/2003 21:43:12
Manuel wrote:
> Can you post the diffs between GENERIC and CUSTOM ?

I think they'd be pretty long, so I'll post them on my website
instead.  The URLs are below.

Note that fxp1 is detected & works correctly in the DEBUG kernel,
and the only difference between the DEBUG kernel and the CUSTOM
kernel (where fxp1 does not work) is this:

  foo# cat diff-CUSTOM-DEBUG
  1c1
  < # CUSTOM NetBSD kernel configuration:
  ---
  > # DEBUG NetBSD kernel configuration:
  13c13
  < ident                 "CUSTOM"
  ---
  > ident                 "DEBUG"
  17c17
  < options               MSGBUFSIZE=32767
  ---
  > options               MSGBUFSIZE=512344
  161c161
  < #options      PCI_CONFIG_DUMP # verbosely dump PCI config space
  ---
  > options       PCI_CONFIG_DUMP # verbosely dump PCI config space

The GENERIC config we all know and love:
 http://www.clarity.net/adam/netbsd/config-GENERIC

The CUSTOM config, where fxp1 returns "unable to map device registers":
 http://www.clarity.net/adam/netbsd/config-CUSTOM

The DEBUG config, where fxp1 works again:
 http://www.clarity.net/adam/netbsd/config-DEBUG

diff(1) between CUSTOM and DEBUG (same as above):
 http://www.clarity.net/adam/netbsd/diff-CUSTOM-DEBUG

diff(1) between GENERIC and CUSTOM:
 http://www.clarity.net/adam/netbsd/diff-GENERIC-CUSTOM

diff(1) between GENERIC and DEBUG:
 http://www.clarity.net/adam/netbsd/diff-GENERIC-DEBUG

Any assistance that you could provide would be much appreciated.

Adam