From owner-freebsd-stable@FreeBSD.ORG Mon May 24 19:20:40 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD7DD16A4CE for ; Mon, 24 May 2004 19:20:40 -0700 (PDT) Received: from zircon.seattle.wa.us (dsl231-043-165.sea1.dsl.speakeasy.net [216.231.43.165]) by mx1.FreeBSD.org (Postfix) with SMTP id 85E1243D49 for ; Mon, 24 May 2004 19:20:40 -0700 (PDT) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 36935 invoked from network); 25 May 2004 02:20:07 -0000 Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; 25 May 2004 02:20:07 -0000 From: Joe Kelsey To: stable@freebsd.org Content-Type: text/plain Message-Id: <1085451607.3232.36.camel@zircon> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 24 May 2004 19:20:07 -0700 Content-Transfer-Encoding: 7bit Subject: Trouble Adding Device Driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2004 02:20:41 -0000 I wrote a *very* simple device driver. It really just manipulates a few fixed addresses on some customized PC-104 boards. However, I cannot seem to get the kernel to run the device probe and attach routines. I set it up to use a line like this in the config file: device vsbc at isa? port 0xe0 since the base address can get set to either 0xe0 or 0x1e0 by BIOS functions. It really just follows the simple-minded isa device driver structures of other examples in the system, but when probe and attach time comes around, a boot verbose prints vsbc0 failed to probe at port 0xe0 on isa0 Can anyone please help me out by explaining what incredibly simple-minded and stupid thing I forgot to do when setting this device up? I appreciate any help anyone can give. /Joe