Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Jan 2001 13:14:48 +1030
From:      Greg Lehey <grog@lemis.com>
To:        Warner Losh <imp@bsdimp.com>
Cc:        Simon Epsteyn <seva@sevatech.com>, freebsd-mobile@FreeBSD.ORG, Bill Paul <wpaul@ee.columbia.edu>
Subject:   Re: AiroNet 'No card in database for "(null)"("(null)")' problem (4.2-STABLE)
Message-ID:  <20010105131448.I48589@wantadilla.lemis.com>
In-Reply-To: <200101050236.f052ai149246@harmony.village.org>; from imp@bsdimp.com on Thu, Jan 04, 2001 at 07:36:44PM -0700
References:  <20010105104705.I81284@wantadilla.lemis.com> <Pine.LNX.4.10.10101031356070.516-100000@null.cc.uic.edu> <200101040558.f045wU119690@harmony.village.org> <20010105104705.I81284@wantadilla.lemis.com> <200101050236.f052ai149246@harmony.village.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday,  4 January 2001 at 19:36:44 -0700, Warner Losh wrote:
> In message <20010105104705.I81284@wantadilla.lemis.com> Greg Lehey writes:
> : On my machine (Dell Inspiron 7500), 0xe0000 is not allocated (or
> : doesn't seem to be), but I can't use it anyway.  There is a hard-coded
> : limit (0xd0000-0xdffff) somewhere in the pccard code.  Even when I
> : remove it, though, I can't use the memory.  I haven't been able to
> : establish whether this is a hardware or software problem.
>
> On many machines that I've seen, the BIOS does, indeed, live at
> 0xe0000. 

No question.  On mine, it's in various chunks between 0xc0000 and
0xfffff.  

> We don't have code to read the ROM mapping tables that PnP provides,
> so unless you've done a memory dump of the area, it is almost
> impossible to know for sure if it is in use or not (well, windows
> might be able to tell you).

Even then, it's not completely possible.  I've taken a look at the
area, and it's "empty" (i.e. filled with 0s).  The trouble is, this
can either mean there's nothing there, or something that forces
zeroes.  The first should be usable, the second obviously not.

> The new bus kludge code does clip start and end to 0xd0000, but you
> are right that is bogus.  On most machines, this is the only space
> available.

Right, but we shouldn't rely on that.  Anyway, it's not the only
problem.

Greg
--
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010105131448.I48589>