From owner-freebsd-hackers Fri Nov 8 15:03:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA16405 for hackers-outgoing; Fri, 8 Nov 1996 15:03:34 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA16379 for ; Fri, 8 Nov 1996 15:03:21 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-47.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA28484 (5.67b/IDA-1.5 for ); Sat, 9 Nov 1996 00:03:03 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id AAA05902; Sat, 9 Nov 1996 00:03:03 +0100 (MET) Message-Id: <199611082303.AAA05902@x14.mi.uni-koeln.de> Date: Sat, 9 Nov 1996 00:03:02 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: smp@csn.net (Steve Passe) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers), chuckr@glue.umd.edu (Chuck Robey), joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: motherboard chipset identification In-Reply-To: <199611082240.PAA02599@clem.systemsix.com>; from Steve Passe on Nov 8, 1996 15:40:08 -0700 References: <199611082240.PAA02599@clem.systemsix.com> X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steve Passe writes: > Hi, > > > I need to be able to tell which chipset is being used on a motherboard > > during the boot process (Neptune, Triton, Natoma, etc.) Could someone > > point me towards the code in the kernel that determines this info??? > > Several people have pointed out sys/pci/pcisupport.c. This is a starting > point, but the chips of interest to me are non-PCI things, like system > controller chips (combo chips that are typically part of the MB "chip-set" > and contain the timers, icus, etc.) The IO APIC is sometimes contained Hmmm, but did you take a look at "pcisupport.c" ? Check out the code that dumps the support chip registers if "bootverbose" is true ... > in these, and comes in different flavors that need slightly different > programming techniques. My specific problem is that you need (so the manuals > claim) to access the IOSELREG via byte writes on some flavors, but DWORD writes > on others. so its a catch-22 situation, I need to know which flavor it is > before I can access it, but I can't safely probe it for clues, cause I don't > know which flavor it is. (thank you very much, #$&^*&# Intel) What does it depend on ? Why can't you probe for it ? (Does a probe lock up the system if the wrong flavor is assumed ?) > The closest I will come is by knowing what types of other system chips > are used, then deducing which IO APIC is most likely to be present from that. > The MP spec defines boards without PCI busses, so I need a more general > mechanism. > > Note that it might not be quite this problematic, all I know right now is we > have flavors that aren't working, and this appears to be a likely reason. Regards, STefan