linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Dale Farnsworth" <dale@farnsworth.org>
To: roger blofeld <blofeldus@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Lite5200 FEC Driver on linux 2.6 broken? (again)
Date: Tue, 16 Nov 2004 13:16:54 -0700	[thread overview]
Message-ID: <20041116201654.GA3088@xyzzy> (raw)
In-Reply-To: <20041116182609.68313.qmail@web53502.mail.yahoo.com>

On Tue, Nov 16, 2004 at 10:26:09AM -0800, roger blofeld wrote:
> Retransmissions from the lite5200 work OK now, but the occasional ACK
> packet is sent from the lite5200 with a bad checksum causing
> retransmissions. Perhaps another patch would fix this problem too?

I too have seen occasional errors, but I don't think it's a software
issue.

-Dale

  reply	other threads:[~2004-11-16 20:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 16:32 Lite5200 FEC Driver on linux 2.6 broken? roger blofeld
2004-11-15 17:34 ` Dale Farnsworth
2004-11-15 19:09   ` Lite5200 FEC Driver on linux 2.6 broken? (fixed) roger blofeld
2004-11-16 18:26   ` Lite5200 FEC Driver on linux 2.6 broken? (again) roger blofeld
2004-11-16 20:16     ` Dale Farnsworth [this message]
2004-11-16 21:28       ` roger blofeld
2004-11-18 20:22       ` Lite5200 FEC Driver on linux 2.6 broken? (fixed again) roger blofeld
2004-11-19 10:32         ` Sylvain Munaut
2004-11-19 14:53       ` roger blofeld
2004-11-21 16:10         ` Sylvain Munaut
2004-11-23 22:42       ` Lite5200 FEC Driver on linux 2.6 (updated) roger blofeld
2004-11-24  8:22         ` MPC5200 Cache coherency with BestComm issue (was: Lite5200 FEC Driver on linux 2.6 (updated)) Sylvain Munaut
2004-11-27 21:39       ` MPC5200 Cache coherency with BestComm issue roger blofeld
2004-11-28 23:22         ` Sylvain Munaut
2004-11-16 18:45   ` Lite5200 FEC Driver on linux 2.6 broken? Sylvain Munaut

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=20041116201654.GA3088@xyzzy \
    --to=dale@farnsworth.org \
    --cc=blofeldus@yahoo.com \
    --cc=linuxppc-embedded@ozlabs.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).