From owner-freebsd-mobile Wed Jan 21 13:41:48 1998 Return-Path: Received: (from majordom@localhost) by catfish.freebsd.org (8.8.8/8.8.8) id NAA23766 for freebsd-mobile-outgoing; Wed, 21 Jan 1998 13:41:48 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by catfish.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23761 for ; Wed, 21 Jan 1998 13:41:46 -0800 (PST) (envelope-from owner-majordomo@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00237 for ; Wed, 21 Jan 1998 13:41:43 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA02057; Wed, 21 Jan 1998 14:41:43 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA14028; Wed, 21 Jan 1998 14:41:40 -0700 Date: Wed, 21 Jan 1998 14:41:40 -0700 Message-Id: <199801212141.OAA14028@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "SiGRiD Fenderson, Fnordkiller" Cc: "Nate Williams" , Subject: Re: PC-CARD woes In-Reply-To: <01bd26b1$c8c59220$2ac8bdcd@fnord2go.bconnex.net> References: <01bd26b1$c8c59220$2ac8bdcd@fnord2go.bconnex.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> specified in pccard.conf is the memory range - does it need to be stated explicitly? > > > >Yes. This is from the sample pccard.conf file that is distributed with > >FreeBSD. > > > Okay, here's my current config: > > io 0x240-0x360 > irq 10 11 > memory 0xd4000 96k Hmm, that looks fine. > I am now back to "driver allocation failed for Megahertz." *boggle* > Is there a good FAQ/handbook/manpage that explains the memory > addressing? I have tweaked the config stated above with various > values including the 0xd0000 address (which worked when I installed > FreeBSD) and various sizes, but to no avail. At this point, you're best bet is to put some printf's in the actual driver to see what resources it thinks it's getting, and to figure out which resource it doesn't like. (In reality, this sort of information should be made available to the user by default, but it isn't. :( ) Nate