From owner-freebsd-mobile  Wed Dec  3 22:30:38 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA25925
          for mobile-outgoing; Wed, 3 Dec 1997 22:30:38 -0800 (PST)
          (envelope-from owner-freebsd-mobile)
Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA25911
          for <mobile@freebsd.org>; Wed, 3 Dec 1997 22:30:33 -0800 (PST)
          (envelope-from mike@word.smith.net.au)
Received: from word (localhost [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id QAA01864;
	Thu, 4 Dec 1997 16:55:44 +1030 (CST)
Message-Id: <199712040625.QAA01864@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: "Glenn Dicus" <gdicus@nomadix.com>
cc: mobile@freebsd.org
Subject: Re: Help 
In-reply-to: Your message of "Wed, 03 Dec 1997 21:53:14 -0800."
             <199712040551.VAA15167@mail.nomadix.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 04 Dec 1997 16:55:43 +1030
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I'm keeping this cc'd to the list; there's every chance that this 
information is useful to other people as well.

> Sorry, you have to excuse me.  I have been trying to get the PC Card on the
> ElanSC400 Evaluation Board for 3 weeks 24-7 with no luck what so ever.  The
> problems have been to many to name.  However,  my present situation is that
> FreeBSD does not recognize the second slot when a card is inserted.  The
> cards that I have tried have been Eagle Technology's NE2000,  Fujitsu
> MBH10302, 3Com 3C3589C/D.  

OK.  You still haven't identified the PCIC on this board; is it 
integrated into the SC400, or is it a separate part?  If the latter, 
what is it?  Do you have datasheets for it?

> Also, a reoccurring problem has been pccardc's inability to read the CIS,
> returning "no entry in database for "null" ("null")".  

It sounds like this is indicative of a pretty major problem; if pccardc 
can't read the CIS information, pccardd (which uses the same code) is 
not going to be able to determine what the card is.

First step is to identify the pcic and work out what's not working.

mike