From owner-freebsd-hackers Fri Nov 8 14:40:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15151 for hackers-outgoing; Fri, 8 Nov 1996 14:40:20 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA15140 for ; Fri, 8 Nov 1996 14:40:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id PAA02599; Fri, 8 Nov 1996 15:40:08 -0700 Message-Id: <199611082240.PAA02599@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: freebsd-hackers@freebsd.org (FreeBSD hackers) cc: Chuck Robey , joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: motherboard chipset identification In-reply-to: Your message of "Fri, 08 Nov 1996 22:41:52 +0100." <199611082141.WAA07413@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Nov 1996 15:40:08 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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 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) 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. -- Steve Passe | powered by smp@csn.net | FreeBSD -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzHe7tEAAAEEAM274wAEEdP+grIrV6UtBt54FB5ufifFRA5ujzflrvlF8aoE 04it5BsUPFi3jJLfvOQeydbegexspPXL6kUejYt2OeptHuroIVW5+y2M2naTwqtX WVGeBP6s2q/fPPAS+g+sNZCpVBTbuinKa/C4Q6HJ++M9AyzIq5EuvO0a8Rr9AAUR tBlTdGV2ZSBQYXNzZSA8c21wQGNzbi5uZXQ+ =ds99 -----END PGP PUBLIC KEY BLOCK-----