netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Manuel Perez Ayala" <mperaya@alcazaba.unex.es>
Cc: netdev@oss.sgi.com
Subject: Re: tg3 support broken on PPC, a workaround
Date: Wed, 11 May 2005 08:24:41 -0700	[thread overview]
Message-ID: <1115825081.8570.93.camel@rh4> (raw)
In-Reply-To: <20050511080446.fnstrvtzq8gk8884@158.49.151.11>

On Wed, 2005-05-11 at 08:04 +0200, Manuel Perez Ayala wrote:

> Working driver:
> 
> On init of driver:
> 
> tg3.c:v3.10 (September 14, 2004)
> PCI: Enabling device 0001:10:13.0 (0014 -> 0016)
> 
> tg3: tg3_test_dma #1: 76FF120F
> 

This tells me that your cache line size is 32 bytes.

Let's try some experiments and see what works and what doesn't. Please
hardcode the following values in tp->dma_rwctrl before it is written to
the register:

1. DMA read/write boundaries set to 256:

tp->dma_rwctrl = 0x76ff2d0f;

2. DMA read boundary 256, write boundary 32:

tp->dma_rwctrl = 0x76ff150f;

3. DMA read boundary 32, write boundary 256

tp->dma_rwctrl = 0x76ff2a0f;

4. Let's also try without asserting all byte enables:

tp->dma_rwctrl = 0x763f2d0f;

Thanks.

  reply	other threads:[~2005-05-11 15:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10  9:33 tg3 support broken on PPC, a workaround Manuel Perez Ayala
2005-05-10 16:52 ` Michael Chan
2005-05-10 19:12   ` David S. Miller
2005-05-10 19:43     ` Michael Chan
2005-05-10 21:15       ` David S. Miller
2005-05-10 20:26     ` David S. Miller
2005-05-10 20:14       ` Michael Chan
2005-05-10 21:23         ` David S. Miller
2005-05-10 20:49           ` Michael Chan
2005-05-10 20:32       ` David S. Miller
2005-05-10 22:13     ` Rick Jones
2005-05-10 23:21       ` Grant Grundler
2005-05-10 23:36         ` David S. Miller
2005-05-11  6:04   ` Manuel Perez Ayala
2005-05-11 15:24     ` Michael Chan [this message]
2005-05-12  9:28       ` Manuel Perez Ayala
2005-05-12 16:33         ` Rick Jones
2005-05-12 18:06           ` Manuel Perez Ayala

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=1115825081.8570.93.camel@rh4 \
    --to=mchan@broadcom.com \
    --cc=mperaya@alcazaba.unex.es \
    --cc=netdev@oss.sgi.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 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).