All of lore.kernel.org
 help / color / mirror / Atom feed
From: Epicom <epicom@idecnet.com>
To: Kari Hameenaho <kari.hameenaho@khaho.pp.fi>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PPC860 cachelines corrected for glibc, need to correct also in kernel ?
Date: Thu, 30 Sep 1999 09:16:31 +0200	[thread overview]
Message-ID: <37F30E08.448@idecnet.com> (raw)
In-Reply-To: 37F0FBC6.B4D8637A@khaho.pp.fi


Kari Hameenaho wrote:
> 
> There was previous correction in this mailing list for cachelines in glibc
> to be used in PPC860.
> 
> >Ok, here's how to build glibc for embedded PPC:
> 
> >First you must remove the assumption that cachelines are 32 bytes:
> >Apply this diff, and simply move sysdeps/powerpc/memset.S out of the
> >way for now:
> 
> >diff -ur orig/glibc-2.1.1/sysdeps/powerpc/dl-machine.c glibc-2.1.1/sysdeps/powerpc/dl-machine.c
> >--- orig/glibc-2.1.1/sysdeps/powerpc/dl-machine.c       Fri Mar  5 23:41:23 1999
> >+++ glibc-2.1.1/sysdeps/powerpc/dl-machine.c    Mon May 17 20:59:06 1999
> >@@ -250,7 +250,11 @@
> >         PowerPC processors have line sizes of exactly 32 bytes.  */
> >
> >       size_modified = lazy ? rel_offset_words : PLT_INITIAL_ENTRY_WORDS;
> >+#ifdef PPC_CACHELINESIZE_32
> >       for (i = 0; i < size_modified; i+= 8)
> >+#else
> >+      for (i = 0; i < size_modified; i+= 4)
> >+#endif
> >        PPC_DCBST (plt + i);
> >       PPC_DCBST (plt + size_modified - 1);
> >       PPC_SYNC;
> >
> 
> We have trouble with PCI bus master boards in Motorola MBX board (PPC860):
> seems like a cache problem, all data not correct as read from PCI bus.
> We have used kernels 2.2.5, 2.3.10 and 2.3.18.
> The memory area is reserved by __get_free_pages(GFP_KERNEL | GFP_DMA,5);
> 
> The situation is improved a lot (it may even be correctred totally) by
> changing
> cache setting in file ppc-asm/cache.h:
> 
> /* bytes per L1 cache line */
> #define        L1_CACHE_BYTES  32
> 
> =>
> 
> /* bytes per L1 cache line */
> #define        L1_CACHE_BYTES  16
> 
> There is also L1_CACHE_PAGES in this file, but it seems that that is not used
> anywhere.
> 
> Is this correct change or should we change something else to make access to
> DRAM more reliable
> from PCI ?
> Is anybody else having problems with PCI bus master access in PPC860 ?
> 
> ---
> Kari Hämeenaho

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~1999-09-30  7:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-28 17:32 PPC860 cachelines corrected for glibc, need to correct also in kernel ? Kari Hameenaho
1999-09-30  7:16 ` Epicom [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=37F30E08.448@idecnet.com \
    --to=epicom@idecnet.com \
    --cc=kari.hameenaho@khaho.pp.fi \
    --cc=linuxppc-embedded@lists.linuxppc.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 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.