From owner-freebsd-mobile Fri Aug 25 18:10:20 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from spock.org (cm-24-92-52-10.nycap.rr.com [24.92.52.10]) by hub.freebsd.org (Postfix) with ESMTP id E026C37B43C for ; Fri, 25 Aug 2000 18:10:14 -0700 (PDT) Received: (from jon@localhost) by spock.org serial EF600Q3T-B7F; Fri, 25 Aug 2000 21:10:12 -0400 (EDT) (envelope-from jon) Date: Fri, 25 Aug 2000 21:10:12 -0400 From: Jonathan Chen To: Kenneth Wayne Culver Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: fe575 (again) Message-ID: <20000825211012.A74017@spock.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from culverk@wam.umd.edu on Fri, Aug 25, 2000 at 12:27:58PM -0400 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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: 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