public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: Stany MARCEL <smarcel@pactenovation.fr>
Cc: Greg Ungerer <gerg@snapgear.com>, linux-m68k@vger.kernel.org
Subject: Re: M54xx FEC and DMA
Date: Mon, 15 Oct 2012 16:43:18 +0200	[thread overview]
Message-ID: <20121015144318.GA12485@frolo.macqel> (raw)
In-Reply-To: <1512C13C0C5EA947AE50B9B9AC314F470343F021@ATLAS.pactenovation.fr>

Hello Stany,

[CCing linux-m68k@vger.kernel.org]

On Mon, Oct 15, 2012 at 03:37:25PM +0200, Stany MARCEL wrote:
> Hello,
> 
>  
> 
> I have sent a patch on linuxm68k mailing list, a few minutes ago, that
> permits to use your driver correctly with MMU without caching issues.
> 
>  
> 
> The strategy is to map a memory zone used for dma allocation as non
> cachable. 

Bright idea.

> 
>  
> 
> It is a lot better than a complete flush at each network operation, and
> correct my issue of lost UDP frames.
> 
>  
> 
> With this and the read write operation replaced by __raw_* one Your FEC
> and MCD DMA works very well for me.

Thanks for the positive feedback.

I was not aware of any difference between __raw_writel and writel on m68k.

For the non-MMU case, I see:
arch/m68k/include/asm/io_no.h:#define __raw_writel writel

but now I have found  for the MMU case:
arch/m68k/include/asm/io_mm.h:#define writel(val,addr) out_le32((addr),(val))
arch/m68k/include/asm/raw_io.h:#define __raw_writel(val,addr) out_be32((addr),(val))

and I understand your problem (out_le32 vs out_be32), but I wonder:
should we not:

- try to understand/fix the difference between __raw_writel and writel in
CONFIG_MMU case (Greg, Geert ?)

- or go to out_be32

Best regards

Philippe

       reply	other threads:[~2012-10-15 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1512C13C0C5EA947AE50B9B9AC314F470343F021@ATLAS.pactenovation.fr>
2012-10-15 14:43 ` Philippe De Muyter [this message]
2012-10-16  5:44   ` M54xx FEC and DMA Greg Ungerer

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=20121015144318.GA12485@frolo.macqel \
    --to=phdm@macqel.be \
    --cc=gerg@snapgear.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=smarcel@pactenovation.fr \
    /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