From owner-freebsd-hackers@FreeBSD.ORG Tue May 20 18:58:59 2008 Return-Path: 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 2C1F11065680; Tue, 20 May 2008 18:58:59 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id DCE6B8FC26; Tue, 20 May 2008 18:58:58 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JyX32-000HsT-9v; Tue, 20 May 2008 21:58:56 +0300 Message-ID: <48331F69.3070205@icyb.net.ua> Date: Tue, 20 May 2008 21:58:49 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: John Baldwin References: <1210616585.00069210.1210605002@10.7.7.3> <1211246591.00072455.1211234402@10.7.7.3> <4832D432.2050907@icyb.net.ua> <200805201124.23850.jhb@freebsd.org> In-Reply-To: <200805201124.23850.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, RW Subject: Re: i386 cpu_reset_real: code/comment mismatch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2008 18:58:59 -0000 on 20/05/2008 18:24 John Baldwin said the following: > On Tuesday 20 May 2008 09:37:54 am Andriy Gapon wrote: >> BTW, I understand that there is a difference between hard and soft reset >> in terms of hardware signals being asserted, but I don't quite >> understand general consequences. I.e. what is a practical difference >> between hard and soft reset? > > I've no idea. It may be that we should just always do a hard reset as that is > in effect what both Solaris and Linux do. I'll probably just change it to do > that. But I think it is already how the code works (maybe with extra port write that couldn't hurt anything). -- Andriy Gapon