Date: Wed, 26 May 1999 08:55:06 -0700 (PDT) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: mike@smith.net.au (Mike Smith) Cc: roger@cs.strath.ac.uk (Roger Hardiman), nick.hibma@jrc.it (Nick Hibma), roger@FreeBSD.ORG (Roger Hardiman), cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/conf options Message-ID: <199905261555.IAA87427@troutmask.apl.washington.edu> In-Reply-To: <199905261515.IAA03133@dingo.cdrom.com> from Mike Smith at "May 26, 1999 08:15:44 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Smith wrote: > > Nick > > > > > Are the Brooktree cards the only bus master cards that suffer from > > > this problem? > > > > While on the subject, I want the bt848 driver to read the > > PCI Host chipset ID and select the 'compatibility' mode > > automatically. (Just like the Windows and Linux drivers do) > > > > But I've no idea how to do this. > > It's actually annoyingly hard to perform a PCI bus enumeration from > within a driver; I need to do this for the AGP driver that I'm trying > to write as well. I think you're going to have to scan the entire list > of connected PCI devices manually, at least in 2.x and 3.x systems. > Under new-bus in 4.x it ought to be possible to query your parent bus > controller(s) to find out what they are. > Is it posible to add sysctl variables that are set as the various busses are probed? Then, one could iterate over the sysctl variables. From my dmesg: pcib0: <PCI host bus adapter> on motherboard pci0: <PCI bus> on pcib0 chip0: <Intel 82440FX (Natoma) PCI and memory controller> at device 0.0 on pci0 isab0: <Intel 82371SB PCI to ISA bridge> at device 7.0 on pci0 The sysctl varaibles become: hw.bus.pci0 = "82440FX" hw.bus.pci1 = NULL hw.bus.isa0 = "82371SB" hw.bus.isa1 = NULL -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905261555.IAA87427>