From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MVrCS-0000FK-KF for qemu-devel@nongnu.org; Tue, 28 Jul 2009 14:14:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MVrCS-0000ER-14 for qemu-devel@nongnu.org; Tue, 28 Jul 2009 14:14:56 -0400 Received: from [199.232.76.173] (port=52515 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MVrCR-0000EO-TJ for qemu-devel@nongnu.org; Tue, 28 Jul 2009 14:14:55 -0400 Received: from mail-gx0-f220.google.com ([209.85.217.220]:51744) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MVrCR-000831-M1 for qemu-devel@nongnu.org; Tue, 28 Jul 2009 14:14:55 -0400 Received: by gxk20 with SMTP id 20so581315gxk.10 for ; Tue, 28 Jul 2009 11:14:54 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 28 Jul 2009 20:14:51 +0200 Message-ID: Subject: Re: [Qemu-devel] [patch] esp.c fast SCSI-bus reset From: Artyom Tarasenko Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel > Unfortunately it also makes BSDs think that the bus reset hasn't happened: How about this one? Seems to be fine with NetBSD. Not "fast" though, emulates more precisely what would happen on a real hw. --- qemu-master/hw/esp.c.master 2009-07-28 19:42:24.161417594 +0200 +++ qemu-master/hw/esp.c 2009-07-28 20:08:15.683543101 +0200 @@ -448,6 +448,11 @@ // Clear interrupt/error status bits s->rregs[ESP_RSTAT] &= ~(STAT_GE | STAT_PE); esp_lower_irq(s); + // Clear bus reset + if(INTR_RST==s->rregs[ESP_RINTR]) { + s->rregs[ESP_RINTR] = 0; + return INTR_RST; + } break; default: break;