From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1faRbH-0000gM-9z for qemu-devel@nongnu.org; Tue, 03 Jul 2018 16:08:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1faRbG-0004HV-GQ for qemu-devel@nongnu.org; Tue, 03 Jul 2018 16:08:35 -0400 Received: from mail-oi0-x242.google.com ([2607:f8b0:4003:c06::242]:42984) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1faRbG-0004HC-CE for qemu-devel@nongnu.org; Tue, 03 Jul 2018 16:08:34 -0400 Received: by mail-oi0-x242.google.com with SMTP id n84-v6so6302973oib.9 for ; Tue, 03 Jul 2018 13:08:34 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180703184922.GA14422@roeck-us.net> References: <20180626200008.GA680@roeck-us.net> <20180702162733.GB32333@roeck-us.net> <20180702170522.GA9885@roeck-us.net> <20180702175740.GA14904@roeck-us.net> <20180702183717.GA22482@roeck-us.net> <20180703184922.GA14422@roeck-us.net> From: Peter Maydell Date: Tue, 3 Jul 2018 21:08:13 +0100 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] [PATCH] hw/char/cmsdk-apb-timer: Correctly identify and set one-shot mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Guenter Roeck Cc: qemu-arm , QEMU Developers On 3 July 2018 at 19:49, Guenter Roeck wrote: > Oddly enough, I now seem to be unable to reproduce the problem either. > Weird, when I wrote the patch it was absolutely necessary. > > The only other change I can think of would be the code to set the > serial baud rate in the boot loader, which I did not have initially. > Is it possible that the hangup could have been caused by that ? Seems unlikely -- unless you're actually connecting the emulated serial port to a real host serial port, we don't do anything with the baudrate in the cmsdk uart model except complain if the guest hasn't set it to something valid. > Is it worth tracking it down, or are we ok ? It does worry me a little, but if neither you nor I can repro it at the moment there's not a lot we can do about it I think. Looking at the ptimer and cmsdk timer code I think it *should* now implement what the hardware does... If you see the problem again in future let me know and we can have another go at figuring out what's going on. > The series WFM as well. I'll send out a Tested-by: in a minute. Thanks for the testing. -- PMM