From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MRBk4-0004zr-17 for qemu-devel@nongnu.org; Wed, 15 Jul 2009 17:10:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MRBjz-0004y4-56 for qemu-devel@nongnu.org; Wed, 15 Jul 2009 17:10:19 -0400 Received: from [199.232.76.173] (port=37492 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MRBjy-0004xy-VS for qemu-devel@nongnu.org; Wed, 15 Jul 2009 17:10:15 -0400 Received: from mail2.shareable.org ([80.68.89.115]:58991) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MRBjy-0005ai-J9 for qemu-devel@nongnu.org; Wed, 15 Jul 2009 17:10:14 -0400 Date: Wed, 15 Jul 2009 22:10:11 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] 2nd try: [PATCH] fix for bad macaddr of e1000 in Windows 2003 server with original Microsoft driver Message-ID: <20090715211011.GK3056@shareable.org> References: <4A5DC91F.7010009@redhat.com> <1247683862.3824.2.camel@slab.beaverton.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1247683862.3824.2.camel@slab.beaverton.ibm.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hollis Blanchard Cc: Naphtali Sprei , qemu-devel@nongnu.org On Wed, 2009-07-15 at 15:18 +0300, Naphtali Sprei wrote: > After comments from quintela@trasno.org and mst@redhat.com, here's the > 2nd try: > > The sequence of reading from eeprom is "offset by one" moved because > of a false detection of a clock cycle after an eeprom reset. Keeping > the last clock value after a reset keeps it in sync. Isn't it more likely that the real hardware resets the clock value to a fixed level - the polarity being the opposite of what QEMU currently does, so that there's no edge caused by the first write? -- Jamie