From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: 9fans@9fans.net
Date: Sat, 27 Sep 2008 15:43:04 +0000
Message-Id: <092720081543.518.48DE5488000954C00000020622218675169B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Subject: [9fans] The late upamalloc
Topicbox-Message-UUID: 15a42ba2-ead4-11e9-9d60-3106f5b1d025

Okay, I've been taking a crack at the broadcom driver
that's been lying around.  It's pretty old and used
the upamalloc call.  But upamalloc is now gone and
I don't seem to be able to find the right way to
replace it.  After looking at other drivers and at
the old upamalloc code on sourcesdump, I've tried
several way to replace it, but most end up in a panic.
The original code (edited to the relevant lines)
looked like:

port =3D upamalloc(bar & ~0x0F, p->mem[0].size, 0);
ctlr->port =3D port;
ctlr->nic =3D KADDR(ctlr->port);

My most recent attempt replaced the upamalloc call
with:

upareserve(bar & ~0x0F, p->mem[0].size);
pdbmap(MACH(0)->pdb, bar & ~0x0F, 0, p->mem[0].size);
port =3D bar & ~0x0F;

There is currently a upaalloc call, and the comment
to it seems to imply that vmap should be used either
in conjunction with upaalloc or by it self.  I've
tried a few permutations of that with no luck.

If someone knows off the top of their head the right
way to replace an old upamalloc call, it would save
me some time, and I could get on to seeing if I can
manage to get the controller to work.

Thanks in advance,
BLS