From: Naphtali Sprei <nsprei@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [Qemu-devel] 2nd try: [PATCH] fix for bad macaddr of e1000 in Windows 2003 server with original Microsoft driver
Date: Thu, 16 Jul 2009 13:30:44 +0300 [thread overview]
Message-ID: <4A5F0154.8020408@redhat.com> (raw)
In-Reply-To: <20090715211011.GK3056@shareable.org>
Jamie Lokier wrote:
> 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?
The eeprom reset I referred to is actually a reset of the internal state of (part of) the device emulation in qemu.
The software drives the clock bit (SK) and the reset shouldn't change it.
>
> -- Jamie
>
>
>
>
next prev parent reply other threads:[~2009-07-16 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 12:18 [Qemu-devel] 2nd try: [PATCH] fix for bad macaddr of e1000 in Windows 2003 server with original Microsoft driver Naphtali Sprei
2009-07-15 18:51 ` Hollis Blanchard
2009-07-15 21:10 ` Jamie Lokier
2009-07-16 10:30 ` Naphtali Sprei [this message]
2009-07-16 13:31 ` Anthony Liguori
2009-07-16 15:17 ` Naphtali Sprei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A5F0154.8020408@redhat.com \
--to=nsprei@redhat.com \
--cc=hollisb@us.ibm.com \
--cc=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.