From: Thomas Petazzoni <thomas.petazzoni@enix.org>
To: linux-mips@linux-mips.org
Subject: Re: Some cache questions
Date: Tue, 28 Dec 2004 09:21:31 +0100 [thread overview]
Message-ID: <41D1178B.3090404@enix.org> (raw)
In-Reply-To: <20041228040240.34537.qmail@web52804.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
Hello,
Manish Lachwani a écrit :
> For chip revisions 1.0 and 1.1, there are some changes
> to the memory management subsystem for the kernel to
> work on the board (dual core). As already known, these
> versions dont support Shared state.
>
> I had made those changes to the 2.4.21 kernel. Maybe
> you can take a look at those changes and port them to
> 2.6 appropriately. However, there is more sanity in
> 1.2 version
Actually, my question was not really Linux-specific. On the second core,
I will not use the MMU, because this core will not run Linux, but a
custom code. Both cores will share informations through KSEG0, so I need
to maintain coherency between caches. What should I do in order to do
that ? Is it enough to set cache mode for KSEG0 to 4 (in the CONFIG
register) ?
I have only 1.0 and 1.1 cores, on home-made boards, so there's no way to
switch to 1.2.
BTW, do you have pointers, papers, information about a system running
Linux on a core, and some custom code on a second core, in order to have
real-time on the second core with very low latency ?
Thanks,
Thomas
--
PETAZZONI Thomas - thomas.petazzoni@enix.org
http://thomas.enix.org - Jabber: thomas.petazzoni@jabber.dk
http://kos.enix.org, http://sos.enix.org
Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E 1624 F653 CB30 98D3 F7A7
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-12-28 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 22:11 Some cache questions Brad Larson
2004-12-28 4:02 ` Manish Lachwani
2004-12-28 8:21 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-27 16:35 Thomas Petazzoni
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=41D1178B.3090404@enix.org \
--to=thomas.petazzoni@enix.org \
--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 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.