Date: Thu, 31 Aug 2000 13:51:55 -0700 From: Mike Smith <msmith@freebsd.org> To: Ron Rosson <insane@lunatic.oneinsane.net> Cc: freebsd-mobile@freebsd.org Subject: Re: USB Message-ID: <200008312051.NAA01582@mass.osd.bsdi.com> In-Reply-To: Your message of "Thu, 31 Aug 2000 13:22:34 PDT." <20000831132234.A86433@lunatic.oneinsane.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Mike Smith (msmith@freebsd.org) wrote: > > > > We've been seeing this problem (the I/O ports for your USB controller > > don't appear to be being set) a little on -current for a while now, but > > we haven't pinned the actual problem down. > > > > On my laptop, I can check the base address register for this: > > > > mass# pciconf -r pci0:7:2: 32 > > 0x00001061 > > > > Please check the above (I expect it to be correct), just in case your > > BIOS is doing something odd. > > Here is what I get when I do it: > > mental# pciconf -r pci0:7:2: 32 > 0x0000f4c1 Ok, it looks like this is the same PCI configuration space parsing bug that we're seeing in -current. I have *no* idea what's causing this yet. If you're feeling inspired, can you print the value of cfg->nummaps at the beginning of pci_add_resources in sys/pci/pci.c ? The value we're interested in is the one that would be printed just before the USB controller's output. Thanks! -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] 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?200008312051.NAA01582>