From owner-freebsd-current Mon Apr 20 21:03:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16688 for freebsd-current-outgoing; Mon, 20 Apr 1998 21:03:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16637 for ; Tue, 21 Apr 1998 04:03:34 GMT (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA03122; Mon, 20 Apr 1998 22:03:27 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA04369; Mon, 20 Apr 1998 22:03:24 -0600 Date: Mon, 20 Apr 1998 22:03:24 -0600 Message-Id: <199804210403.WAA04369@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: Nate Williams , Charlie ROOT , FreeBSD-Current Subject: Re: [CAM]?DEVFS not for PCMCIA? In-Reply-To: <353C1637.31D2DE92@whistle.com> References: <353BAF9E.6201DD56@whistle.com> <199804202347.RAA03390@mt.sri.com> <353BE7E0.5656AEC7@whistle.com> <199804210310.VAA04208@mt.sri.com> <353C1637.31D2DE92@whistle.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Nate, what context does the 'attach' code for a driver get > > > called from in the case of a OC-CARD insertion? > > > > > > is it in the kernel level context of a daemon, or is it > > > run from an interrupt level event? > > > > It's inside of the kernel, with interrupts disabled (but allocated, > > which is a known bug). > > So you call it from the interrup layer? bummer. No, but I turn off interrupts because they would kill us. > because that makes it hard to run justin's stuff from there directly.. > we'd have to "schedule it to run at a later time". (maybe a timeout()) Card insertions happen at interrupt level, but the powering on and other 'intialization' all happens with timeouts. > Imagine if you will that a SCSI card is probed at boot. > it schedules itself to have it's scsi bus probed at a later time > after interrupts are turned on. > All such requests are run near the end of boot... And the advantage of this is?? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message