From owner-freebsd-drivers@FreeBSD.ORG Tue Apr 1 05:29:04 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBC92106568F; Tue, 1 Apr 2008 05:29:04 +0000 (UTC) (envelope-from root@mmu.edu.my) Received: from staff.cyber.mmu.edu.my (staff.cyber.mmu.edu.my [203.106.62.12]) by mx1.freebsd.org (Postfix) with ESMTP id D210A8FC16; Tue, 1 Apr 2008 05:29:03 +0000 (UTC) (envelope-from root@mmu.edu.my) Received: by staff.cyber.mmu.edu.my (Postfix, from userid 0) id 3E79A4D5A01; Tue, 1 Apr 2008 13:20:55 +0800 (MYT) Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mmu.edu.my (Postfix) with ESMTP id ED08755E487 for ; Fri, 28 Mar 2008 03:53:08 +0800 (MYT) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 823C2175C98; Thu, 27 Mar 2008 19:52:49 +0000 (UTC) (envelope-from owner-freebsd-hackers@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id AE7E510656A3; Thu, 27 Mar 2008 19:52:46 +0000 (UTC) (envelope-from owner-freebsd-hackers@freebsd.org) Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E4A51065676 for ; Thu, 27 Mar 2008 19:52:39 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.237]) by mx1.freebsd.org (Postfix) with ESMTP id ECC698FC13 for ; Thu, 27 Mar 2008 19:52:38 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so7949535qbd.7 for ; Thu, 27 Mar 2008 12:52:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=v3fLq7AcFlwF1CfhZs5TIQX/3aS1ipFqOlYKh1b94z8=; b=KVrKl+ktO03zeyJ++KHA0cBDXTjAV891RTWQHFLuVaBHdMB9nN7qUoXvWzzvktQcztdtWwNj1eDhbu9ESAmeeaZ18VcDmGsKdvgDprHUAaGNkJQhS2FONR4fzmB5ncc3PEV+QdpK0px/D0U0OggFQx+8Y9LgvtOsp5K+YPis1Ss= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tZRD/IjlO+7bifnQjjV/oZBbFHhH8aEH4N9IAFUpm5Jql2uDwRZtN8Wbi+MulRxDPQuulWVbvMFCghHxKYXyR5eUHz4cn1+q0yOLb34pD60bAeHpEnLTV/KBIztyNZD+y5hudPpOZ9JRi9e9HkdPr86hWCjopfQ5kgPRx001r6g= Received: by 10.142.172.12 with SMTP id u12mr1739497wfe.16.1206647557589; Thu, 27 Mar 2008 12:52:37 -0700 (PDT) Received: by 10.142.147.6 with HTTP; Thu, 27 Mar 2008 12:52:37 -0700 (PDT) Message-ID: <3c0b01820803271252m488159ebi2af2255461f10358@mail.gmail.com> Date: Thu, 27 Mar 2008 15:52:37 -0400 From: "Alexander Sack" To: "Julian Elischer" In-Reply-To: <47EBF498.9090409@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3c0b01820803270851x24bfe739pea0bd4fb0ebecfb0@mail.gmail.com> <47EBF498.9090409@elischer.org> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-hackers@freebsd.org Errors-To: owner-freebsd-hackers@freebsd.org Cc: freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: Stupid driver build/debug questions X-BeenThere: freebsd-drivers@freebsd.org List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2008 05:29:05 -0000 On Thu, Mar 27, 2008 at 3:25 PM, Julian Elischer wrote: > Alexander Sack wrote: > > Hello: > > > > New to the FreeBSD kernel and I'm investigating a driver problem > > (wasn't sure what list this should go on). > > > > I was wondering how to make a driver statically built instead of a > > loadable module? Is this an artifact of the driver source build or > > the generic kernel configuration mechanism via options etc.? i.e. > > does a driver need to use something different than the bsd.kmod.mk > > template make file to build a static driver. > > > > What I am trying to do is break at attach time more easily than > > stepping through driver_probe_and_attach()/driver_attach_child() until > > the attach routine gets called. I realize I can add a kdb_enter() but > > I was trying to do this on a live system without rebuilding the kernel > > (I understand this contradicts my first question but I still want to > > know how to build drivers statically). > > put the filennames in /sys/conf/files or files.i386 (or whatever) > > at one stage you could also have a files.{CONFIGNAME} but I haven't > tried that for a long time. Thanks for the response. I will try this but I do have an obvious question, the build scripts do not need to be edited at all with the extra directory/files? It will just pickup my driver directory and link against the kernel automagically? -aps -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"