Date: Thu, 15 Mar 2001 12:05:09 -0500 From: Andrew Gallatin <gallatin@cs.duke.edu> To: Peter Wemm <peter@FreeBSD.org> Cc: ps@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/pci intpm.c Message-ID: <20010315120509.A6168@grasshopper.cs.duke.edu> In-Reply-To: <200103150656.f2F6upR54225@freefall.freebsd.org>; from peter@FreeBSD.org on Wed, Mar 14, 2001 at 10:56:51PM -0800 References: <200103150656.f2F6upR54225@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm [peter@FreeBSD.org] wrote: > peter 2001/03/14 22:56:51 PST > > Modified files: > sys/pci intpm.c > Log: > Add a placeholder for the ServerWorks OSB4 device id. The SMBus > interface on this chip is compatable with the PIIX4. The catch is that > this interferes with isab0 which wants to attach to the same PCI node. > It seems to work, but we only tested it on systems with no ISA cards. Does this actually work for you? On what type of motherboard? On both a SuperMicro 370DER & Dell PowerEdge 1550, any attempt to access the smb device causes the machine to lock solid. On both machines, I see the intpm device attached as: intpm0: <ServerWorks OSB4 PCI to ISA Bridge> port 0x580-0x58f irq 9 at device 15.0 on pci0 intpm0: I/O mapped 580 intpm0: intr SMI enabled revision 0 smbus0: <System Management Bus> on intsmb0 smb0: <SMBus general purpose I/O> on smbus0 intpm0: PM Memory 33f0 Thanks, Drew -- ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 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?20010315120509.A6168>