Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Quinn Jensen <jensenq@Lineo.COM>
Cc: jsun@hermes.mvista.com, Ralf Baechle <ralf@oss.sgi.com>,
	linux-mips@oss.sgi.com
Subject: Re: NFS root with cache on
Date: Mon, 05 Feb 2001 11:15:19 -0800	[thread overview]
Message-ID: <3A7EFBC7.9B7D6AF9@mvista.com> (raw)
In-Reply-To: 3A7EF431.2060903@Lineo.COM

Quinn Jensen wrote:
> 
> jsun@hermes.mvista.com wrote:
> 
> > Quinn Jensen wrote:
> >
> >>>> Is anyone else having trouble with NFS root on
> >>>> the 2.4.0 kernel?  It won't come up with the
> >>>> KSEG0 cache on unless I pepper the network driver
> >>>> with flush calls.
> >>>
> >>>
> >>> That's expected for most old network drivers that don't yet use tye
> he
> >>> new PCI DMA API documented in Documentation/DMA-mapping.txt.
> >>>
> >>> What driver is this?
> >>
> >> Both the stock 2.4.0 tulip and eepro100 drivers.  The
> >> problem doesn't happen when I go back to 2.3.99pre8.
> >>
> >
> > Did you set rx_copybreak to 1518?  I sent patches long time ago to the driver
> > authors for MIPS, but I am not sure they are not there.
> 
> Jun,
> 
> I have tried that in this case but it didn't help,
> because the receive skb data pointers all point to
> the KSEG0 view of the data anyway. 

I looked into similar problems a while back.  If I remeber correctly, the data
pointers do point to kseg0.  It is up to the driver to do appropriate
dma_cache_invalidate() (or some functions to that effect) at certain places.

What is the CPU?  It seems logical to suspect about the dma cache routines.

Jun

  reply	other threads:[~2001-02-05 19:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01 20:34 NFS root with cache on Quinn Jensen
2001-02-05  3:44 ` Ralf Baechle
2001-02-05 16:50   ` Quinn Jensen
2001-02-05 16:55     ` Kevin D. Kissell
2001-02-05 16:55       ` Kevin D. Kissell
2001-02-05 18:07     ` Jun Sun
2001-02-05 18:42       ` Quinn Jensen
2001-02-05 19:15         ` Jun Sun [this message]
2001-02-05 21:14           ` Quinn Jensen
2001-02-05 19:50       ` Ralf Baechle
2001-02-05 21:13         ` netbooting indy - update, elf2ecoff? Kenneth C Barr
2001-02-05 21:13           ` Kenneth C Barr
2001-02-06  6:32           ` Geert Uytterhoeven
2001-02-06 18:07             ` Klaus Naumann
2001-02-06 20:24               ` Florian Lohoff
2001-02-05 21:39         ` NFS root with cache on Alan Cox
2001-02-05 21:39           ` Alan Cox

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=3A7EFBC7.9B7D6AF9@mvista.com \
    --to=jsun@mvista.com \
    --cc=jensenq@Lineo.COM \
    --cc=jsun@hermes.mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@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