From: Jun Sun <jsun@mvista.com>
To: christophe barbe <christophe.barbe@lineo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100 question: why SCBCmd byte is 0x80?
Date: Fri, 23 Mar 2001 09:34:36 -0800 [thread overview]
Message-ID: <3ABB892C.A47D6BA9@mvista.com> (raw)
In-Reply-To: <3ABA68EC.89B2DE99@mvista.com> <20010323115535.A16497@pc8.inup.com>
christophe barbe wrote:
>
> Which kernel are you using.
>
> I've had a similar problem with 2.2.18.
> I've backported 2.2.19pre changes to it.
> (i.e. apply on 2.2.18 a diff of the file drivers/net/eepro100.c made between 2.2.18 and the last 2.2.19pre)
> And since I've never seen this problem again.
>
> Christophe
>
Kernel is 2.4.2. It is a MIPS machine.
I don't really think it is a driver problem, because the same dirver works
fine on many other boards (including MIPS boards). In addition, I also tested
with tulip cards and I had the same symptom. I am convinced it is a low-level
problem (bus timing, PCI setting, buggy hardware, etc).
On the other hand, it could be a driver problem which is only exposed in this
particular board, although very unlikely.
BTW, does the eepro100 patch for 2.2.19pre apply to 2.4.2? Or it is already
in it?
Thanks.
Jun
> On jeu, 22 mar 2001 22:04:45 Jun Sun wrote:
> >
> > 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
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
> --
> Christophe Barbé
> Software Engineer
> Lineo High Availability Group
> 42-46, rue Médéric
> 92110 Clichy - France
> phone (33).1.41.40.02.12
> fax (33).1.41.40.02.01
> www.lineo.com
next prev parent reply other threads:[~2001-03-23 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 21:04 eepro100 question: why SCBCmd byte is 0x80? Jun Sun
2001-03-23 10:55 ` christophe barbe
2001-03-23 17:34 ` Jun Sun [this message]
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=3ABB892C.A47D6BA9@mvista.com \
--to=jsun@mvista.com \
--cc=christophe.barbe@lineo.fr \
--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