From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Nandakumar NarayanaSwamy <nanda_kn@rediffmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 8139too.c problems
Date: Tue, 13 Aug 2002 16:07:02 -0400 [thread overview]
Message-ID: <3D5966E6.8060500@mandrakesoft.com> (raw)
In-Reply-To: 20020813104232.29562.qmail@mailweb34.rediffmail.com
Nandakumar NarayanaSwamy wrote:
> Resending the mail, since i have not received a copy of that...
> Sorry if ypu are receiving duplicate copies.
>
>
> Hi All,
>
> Sorry for disturbing the list again.
>
> I am using RTL8139C in our target board which is based on MIPS
> IDT32334 processor.
>
> The version of 8139too.c that i am using is 1.0.1 where as I am
> using a embedded linux which is based on Linux Kernel
> 2.4.5-pre1.
>
> When the packet is transmitted out, it is coming out as all
> 0's(captured using sniffer). I dumped the whole packet in
> rtl8139_start_xmit (). The packet is a valid ARP packet.
>
> My doubt is whether this 8139too.c is tested with MIPS processors?
> Because in one of the article i found that the supported
> processors are ARM, i386 etc.
8139too has been tested on big-endian and little-endian, 32-bit and
64-bit processors without showing the behavior you're seeing.
If the packet is fine in rtl8139_start_xmit, it sounds like a hardware
problem. There is certainly the possibility that your platform is
interacting poorly in some way with the driver, but that's a slim
possibility. There's no way to know more without you doing some testing
and experimentation yourself.
Jeff
prev parent reply other threads:[~2002-08-13 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 10:42 8139too.c problems Nandakumar NarayanaSwamy
2002-08-13 20:07 ` Jeff Garzik [this message]
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=3D5966E6.8060500@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nanda_kn@rediffmail.com \
/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.