From: Sylvain Munaut <tnt@246tNt•com>
To: roger blofeld <blofeldus@yahoo•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Lite5200 FEC Driver on linux 2.6 broken? (fixed again)
Date: Fri, 19 Nov 2004 11:32:20 +0100 [thread overview]
Message-ID: <419DCBB4.6010201@246tNt.com> (raw)
In-Reply-To: <20041118202213.20094.qmail@web53504.mail.yahoo.com>
roger blofeld wrote:
>Adding a call
>
> flush_dcache_range((u32)skb->data, (u32)skb->data + skb->len);
>
> just before spin_lock_irq() in fec_hard_start_xmit() removes the
>remaining transmission checksum errors for me.
>-rb
>
>
>
Mmmm.
That should not be needed.
What tree are you exactly using ?
In mainstream XLB snooping is not configured so if you have the
mainstream + added DMA,
the problem may come from this.
Sylvain
next prev parent reply other threads:[~2004-11-19 10:32 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
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 [this message]
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=419DCBB4.6010201@246tNt.com \
--to=tnt@246tnt$(echo .)com \
--cc=blofeldus@yahoo$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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