From owner-freebsd-current Tue May 9 18:46:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id A64BB37BE16 for ; Tue, 9 May 2000 18:46:38 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA21402; Tue, 9 May 2000 18:46:27 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005100146.SAA21402@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: shimon@simon-shapiro.org Cc: freebsd-current@freebsd.org Subject: Re: EVENTHANDLER_DECLARE In-reply-to: Your message of "Tue, 09 May 2000 21:44:12 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 May 2000 18:46:27 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sorry to bother y'll, but; > > Has anyone ever used that? I see no trace of any kernel > code calling it, and the at_shutdown code appears to be > gone. It's still used in the shutdown code; it was meant to be available for general use elsewhere, but I haven't seen anyone playing with it, so maybe the design tradeoffs were bad choices. > BTW, for all it is worth, any caching controller not using > this is guaranteed to lose data. Wrong layer. You should be using the bus shutdown method; look at eg. the Mylex driver to see how this is done. You should probably call your flush routine from the suspend method as well. (Note that the Mylex stuff doesn't correctly handle suspend/resume since we don't have a decent ACPI implementation yet) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message