From: Jun Sun <jsun@mvista.com>
To: linux-kernel@vger.kernel.org
Subject: eepro100 question: why SCBCmd byte is 0x80?
Date: Thu, 22 Mar 2001 13:04:45 -0800 [thread overview]
Message-ID: <3ABA68EC.89B2DE99@mvista.com> (raw)
I am trying to get netgear card working on a new (read as potentially buggy
hardware) MIPS board.
The eepro100 driver basically works fine. It is just after a little while
(usually 2 sec to 15 sec) network communication suddenly stops and I start see
error message like "eepro100: wait_for_cmd_done timeout!".
I looked into this, and it appears that the SCBCmd byte in the command word
has value 0x80 instead of the expected 0. I looked at the Intel manual, and
it says nothing about the value being 0x80.
Does anybody have a clue here? I suspect some timing is wrong or a buggy PCI
controller.
Please cc your reply to my email address. Thanks.
Jun
next reply other threads:[~2001-03-22 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 21:04 Jun Sun [this message]
2001-03-23 10:55 ` eepro100 question: why SCBCmd byte is 0x80? christophe barbe
2001-03-23 17:34 ` Jun Sun
2001-03-24 0:49 ` Steven Walter
2001-03-27 21:34 ` Ion Badulescu
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=3ABA68EC.89B2DE99@mvista.com \
--to=jsun@mvista.com \
--cc=linux-kernel@vger.kernel.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