From owner-cvs-all Wed Apr 10 10:44:42 2002 Delivered-To: cvs-all@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id B689237B400; Wed, 10 Apr 2002 10:44:27 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [IPv6:fec0::1:12]) by Awfulhak.org (8.12.2/8.11.6) with ESMTP id g3AHi9oi031697; Wed, 10 Apr 2002 18:44:09 +0100 (BST) (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.12.2/8.12.2) with ESMTP id g3AHi4OF056430; Wed, 10 Apr 2002 18:44:04 +0100 (BST) (envelope-from brian@freebsd-services.com) Message-Id: <200204101744.g3AHi4OF056430@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Scott Long Cc: Brian Somers , cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/digi digi.c digi.h digi_isa.c In-Reply-To: Message from Scott Long of "10 Apr 2002 10:25:43 CDT." <1018452343.10637.2.camel@hollin.btc.adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Apr 2002 18:44:04 +0100 From: Brian Somers Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Wed, 2002-04-10 at 09:32, Brian Somers wrote: > > > brian 2002/04/10 07:32:56 PDT > > > > Modified files: > > sys/dev/digi digi.c digi.h digi_isa.c > > Log: > > Yet another adjustment of digi_delay(). The delay is now consistent > > irrespective of whether tsleep() or DELAY() is used. > > > > Revision Changes Path > > 1.27 +8 -8 src/sys/dev/digi/digi.c > > 1.12 +2 -1 src/sys/dev/digi/digi.h > > 1.9 +9 -9 src/sys/dev/digi/digi_isa.c > > Brian, > > Instead of jumping through all of these hoops, why can't you do a > config_intrhook_establish() to have the delay-sensitive operations done > at a more appropriate time? This will work for both the at-boot and > post-boot cases. Hi, While this would be a clean way of doing things, I'd prefer not to defer the card initialisation. Ultimately I'd like to be able to use the device as a console. As a few people have pointed out, the ``delay'' thing is a more generic problem. Many drivers will want to give their hardware instructions and then poll waiting for completion during probe and attach. Having the clock available at module initialisation time is probably the best answer. > Scott -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message