public inbox for
 help / color / mirror / Atom feed
Subject: [Bug 1001668] New: Fix: phy_read() function returns bad values if interrupt occurs
Date: Thu, 06 Sep 2012 22:32:00 -0000	[thread overview]
Message-ID: <> (raw)

Please do not reply to this email. Use the web interface provided at:

           Summary: Fix: phy_read() function returns bad values if
                    interrupt occurs
           Product: eCos
           Version: CVS
          Platform: Custom (Customer specific)
        OS/Version: PowerPC
            Status: UNCONFIRMED
          Severity: minor
          Priority: low
         Component: Patches and contributions
             Class: Advice Request

Created an attachment (id=1931)
 --> (
cvs diff: if_fec.c interrupt handling fix

The phy_read() function can return bad values if interrupts occurs during
reading a PHY register.

During interrupt handling the iEvent_MII bit is incorrectly cleared. That bit
is polled in phy_read() and phy_write() functions and should not be cleared in
the interrupt handler.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2012-09-06 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 22:32 bugzilla-daemon [this message]
2012-09-09  9:37 ` [Bug 1001668] " bugzilla-daemon
2012-09-20 22:34 ` bugzilla-daemon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).