qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Naphtali Sprei <nsprei@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 2nd try: [PATCH] fix for bad macaddr of e1000 in Windows 2003 server with original Microsoft driver
Date: Wed, 15 Jul 2009 11:51:01 -0700	[thread overview]
Message-ID: <1247683862.3824.2.camel@slab.beaverton.ibm.com> (raw)
In-Reply-To: <4A5DC91F.7010009@redhat.com>

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.
> 
> Signed-off-by: Naphtali Sprei <nsprei@redhat.com>
> ---
>  hw/e1000.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/hw/e1000.c b/hw/e1000.c
> index 4ac8918..15598ab 100644
> --- a/hw/e1000.c
> +++ b/hw/e1000.c
> @@ -262,6 +262,8 @@ set_eecd(E1000State *s, int index, uint32_t val)
>      }
>      if (!(val & E1000_EECD_CS)) {              // rising, no CS (EEPROM 
> reset)
>          memset(&s->eecd_state, 0, sizeof s->eecd_state);
> +        // restore old_eecd's E1000_EECD_SK to avoid false detection of 
> a clock edge
> +        s->eecd_state.old_eecd = E1000_EECD_SK;
>          return;
>      }
>      s->eecd_state.val_in <<= 1;
> --
> 1.5.5.6

This fixes the problem for me.

-- 
Hollis Blanchard
IBM Linux Technology Center

  reply	other threads:[~2009-07-15 18:51 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 [this message]
2009-07-15 21:10   ` Jamie Lokier
2009-07-16 10:30     ` Naphtali Sprei
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=1247683862.3824.2.camel@slab.beaverton.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=nsprei@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).