From: Ralf Baechle <ralf@linux-mips.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Sharp <andy.sharp@onstor.com>, linux-mips@linux-mips.org
Subject: Re: paging problem with ide-cs driver
Date: Wed, 10 Oct 2007 12:25:51 +0100 [thread overview]
Message-ID: <20071010112550.GA1780@linux-mips.org> (raw)
In-Reply-To: <20071009220530.0416792b@the-village.bc.nu>
On Tue, Oct 09, 2007 at 10:05:30PM +0100, Alan Cox wrote:
> > Before I dive into this, does any of this ring a bell for anyone?
> > I'm using the ide-cs driver, TI yenta cardbus adapter driver, and sibyte
> > everything else.
>
> That has cache coherency painted all over it in bright flashing letters.
The Sibyte SOCs have hardware cache coherency and physically indeded
D-caches which makes I/O pretty much a nobrainer.
I-cache coherency is the thing that really needs babysitting on Sibyte
and the Sibyte I-caches are of a somewhat rare kind by being VIVT plus
an additional address space tag. Mostly because of code duplication
the Sibyte cachecode has its nice damp and dark corner where it did
bitrot away for a while. Thiemo and I recently found the standard
R4000 cache code to work more reliable for Sibyte so we're getting rid
of it for 2.6.24. The patch is in 06e523e89ec0322c4abcf41533d5380dfcd81f73.
It can easily be backported to older kernels so I suggest trying this
one.
(As collateral damage 06e523e89ec0322c4abcf41533d5380dfcd81f73 breaks
support for pass 1 BCM1250 parts. But it seems I'm the last one with one
of those ...)
Ralf
prev parent reply other threads:[~2007-10-10 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 20:26 paging problem with ide-cs driver Andrew Sharp
2007-10-09 21:05 ` Alan Cox
2007-10-09 21:41 ` Andrew Sharp
2007-10-10 11:25 ` Ralf Baechle [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=20071010112550.GA1780@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andy.sharp@onstor.com \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox