Date: Fri, 25 Aug 2000 21:10:12 -0400 From: Jonathan Chen <jon@spock.org> To: Kenneth Wayne Culver <culverk@wam.umd.edu> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: fe575 (again) Message-ID: <20000825211012.A74017@spock.org> In-Reply-To: <Pine.GSO.4.21.0008251225410.20848-100000@rac1.wam.umd.edu>; from culverk@wam.umd.edu on Fri, Aug 25, 2000 at 12:27:58PM -0400 References: <Pine.GSO.4.21.0008251219160.20848-100000@rac1.wam.umd.edu> <Pine.GSO.4.21.0008251225410.20848-100000@rac1.wam.umd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 25, 2000 at 12:27:58PM -0400, Kenneth Wayne Culver wrote:
> > Alright, here's the latest, I added my pci id for my cardbus chip (ti
> > 1225) to the hack driver, and it detects.. but says:
> >
> > pccbb: Could not map register memory
> >
> > What should I do to the code to fix this? I'm a bit stumped because I've
> > been sitting here for a while now trying to get this to work.
> >
> >
> Alright, I've been looking at the code some more, and I found this:
>
> /* The IBM TP600E is gracious enough to pre-allocate a memory
> * space for the PCI-CardBus bridge, so all we need to do is map
> * it in, and save the address in the softc register */
> rid=PCIR_CARDBUS_BASE_2;
> sc->cb_base_res=bus_alloc_resource(dev, SYS_RES_MEMORY, &rid,
> 0,~0,1, RF_ACTIVE);
>
> Basically this looks to me like you're assuming that all laptops
> pre-allocate a memory space for the pci-cardbus bridge... and that's why
> my laptop can't map the register space... because it's not pre-allocating
> memory for the bridge. I'm looking into how to do this, and when I am
> done, I'll make patchs to your patchs :-) for those of us who got this
> ethernet card with their Dell Inspiron 3800's :)
AFAIK, the PCI specs *REQUIRES* the PCI bus to pre allocate space that the
attached devices requests. I don't have access to the PCI spec right now
(why can't everybody put spec sheets online for free?!) but this should
apply to the PCI-Cardbus bridge as well. (If I'm wrong, please correct me)
In anycase, I might be able to figure out what exactly is the problem if
you show me your bootup dmesg as well as the output to the following
comands:
pciconf -r pci0:X:Y 0x10
pciconf -r pci0:X:Y 0x14
pciconf -r pci0:X:Y 0x18
pciconf -w pci0:X:Y 0x10 0xffffffff
pciconf -r pci0:X:Y 0x10
substitute the correct device numbers for X and Y - you can find that on
the kernel bootup output when it says something like:
pccbbhack0: <Blah blah> mem blah-blah irq blah on at device X.Y pci0
--
(o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o)
\\\_\ Jonathan Chen jon@spock.org /_///
<____) No electrons were harmed during production of this message (____>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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?20000825211012.A74017>