Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <Helge.Deller@ruhr-uni-bochum.de>
To: <parisc-linux@puffin.external.hp.com>
Subject: Re: [parisc-linux] lasi scsi driver
Date: Fri, 3 Mar 2000 02:34:03 +0100	[thread overview]
Message-ID: <00030302414501.19213@P100> (raw)
In-Reply-To: <007901bf8490$8db01ef0$a94abc0f@hungary.hp.com>

Hi,

Am Thu, 02 Mar 2000 schrieb Gyula Matics:
> > Aside from the mailbox problems, have you added code to flush/purge
> > entries for payload data?
> 
> It is not a clean mailbox system. It is mixing data and commands in the
> mailbox...
> 
> > > I know that the architecture supports setting a page non-cacheable.
> > > My question is if it is possible / good idea to set the mailbox page
> > > to non-cacheable?
> > 
> > Philipp Rumpf mentioned a possible implementation to me in a private
> > e-mail (make_page_uncached()). He's open to other ideas and/or
> > interfaces if another architecture has already solved this problem.
> 
> The driver was originally written for m68k and one can find this code
> fragments in it:
> 
>     cache_push(virt_to_phys((void *)(instance->hostdata[0])), 8192);
>     cache_clear(virt_to_phys((void *)(instance->hostdata[0])), 8192);
>     kernel_set_cachemode(instance->hostdata[0], 8192, IOMAP_NOCACHE_SER);

Theese function (in the same order) was used in the lasi-ethernet-driver too.
Maybe you want to take a look at the functions dma_cache_inv() and
dma_cache_wback(), which I defined  at the top of the lasi_82596.c driver.
Currently this is really only a bad hack, but I think this is the way you could
go until make_page_uncached() is available.... ?
This means:
cache_push() -> dma_cache_wback()   and
cache_clear() -> dma_cache_inv().
I just added this hack, since currently dma_cache_inv() is defined as
flush_all_caches(), and this function doesn´t INVALIDATES the cache.

> 
> > in Documentation/DMA-mapping.txt. (I reccomend version 2.3.47
> 
> OK, i'll read it.
> 
> Gyula

Helge.

  parent reply	other threads:[~2000-03-03  2:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-02 20:42 [parisc-linux] lasi scsi driver Gyula Matics
2000-03-02 21:19 ` Grant Grundler
2000-03-02 21:44   ` Gyula Matics
2000-03-03  0:50     ` [parisc-linux] Lasi Ethernet - update Helge Deller
2000-03-03  2:55       ` Bdale Garbee
2000-03-03 13:14         ` [parisc-linux] Lasi Ethernet - update (fixed!) Helge Deller
2000-03-03  1:34     ` Helge Deller [this message]
2000-03-03 15:52   ` [parisc-linux] lasi scsi driver willy
2000-03-03 19:10 ` Jerry Huck
2000-03-04 19:49   ` willy
2000-03-05  5:49     ` Grant Grundler
2000-03-05 14:29       ` [parisc-linux] uncacheable memory willy
2000-03-05 15:57         ` [parisc-linux] uncacheable memory (D370) rob hoppe
2000-03-05 16:05           ` willy
2000-03-06  6:26         ` uncacheable memory Grant Grundler
2000-03-05 18:34       ` [parisc-linux] lasi scsi driver Philipp Rumpf
2000-03-05 18:46   ` Philipp Rumpf
2000-03-05 21:05     ` Thomas Bogendoerfer
2000-03-07 19:33     ` Jerry Huck
2000-03-07 23:45       ` Philipp Rumpf
2000-03-08  0:33         ` Grant Grundler

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=00030302414501.19213@P100 \
    --to=helge.deller@ruhr-uni-bochum.de \
    --cc=parisc-linux@puffin.external.hp.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