From owner-freebsd-hackers Sun Feb 28 9:10:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id D965715255 for ; Sun, 28 Feb 1999 09:10:19 -0800 (PST) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port23.netsvr1.cst.vastnet.net [207.252.73.23]) by etinc.com (8.8.8/8.6.9) with SMTP id MAA00353 for ; Sun, 28 Feb 1999 12:11:58 -0500 (EST) Message-Id: <199902281711.MAA00353@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sun, 28 Feb 1999 12:19:18 -0500 To: hackers@freebsd.org From: Dennis Subject: CPU-type question Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What does the "cpu" directive in the kernel config actually do? In the context of a binary driver, is there a potential problem if the binary was compiled on one type of cpu and that cpu type was not specified in the target machine's config? (that is that the driver was compiled on a i586 and the target machine only specified i686). I suppose this has some relevance to loadable drivers as well. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message