From: Franck <vagabon.xyz@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH] Add support for 4KS cpu.
Date: Tue, 4 Oct 2005 17:10:52 +0200 [thread overview]
Message-ID: <cda58cb80510040810y286b06bcx@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61L.0510041430120.10696@blysk.ds.pg.gda.pl>
2005/10/4, Maciej W. Rozycki <macro@linux-mips.org>:
> See my other comment in this thread. As to the SmartMIPS/crypto
> instructions -- unless they are going to be emitted by GCC for the kernel
> build (which I seriously doubt), there is no point in enabling them.
>
some assembly code could...
> > algorithms. And have some extra bits in TLB to protect pages from
> > being execute for example. These are the main differences that I can
>
> Now that may be of potential interest of the kernel, but again, that's in
> principle probably not specific to these processors,
>
hmm, I'm not an expert in MIPS cpu as you guys, so can you give me an
example of others processors that have such TLB features ?
> > remember. Big fat warning: I sent all support I have done for these
> > cpu, _not_ more, _not_ less. I agree it's almost nothing but it's a
> > start...
>
> Well, it's probably a bit too early for inclusion, but it's certainly not
> for a review. By sending changes here for discussion early you may avoid
> a lot of hassle later when you may discover a major update is required for
> them to be accepted. Good luck!
Actually Ralf asked for it in a previous thread.
Thanks
--
Franck
next prev parent reply other threads:[~2005-10-04 15:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 8:49 [PATCH] Add support for 4KS cpu Franck
2005-10-04 11:34 ` Maciej W. Rozycki
2005-10-04 12:38 ` Kevin D. Kissell
2005-10-04 13:29 ` Maciej W. Rozycki
2005-10-04 13:54 ` Kevin D. Kissell
2005-10-04 15:18 ` Franck
2005-10-04 16:01 ` Maciej W. Rozycki
2005-10-04 17:33 ` Franck
2005-10-05 6:55 ` Franck
2005-10-05 13:22 ` Maciej W. Rozycki
2005-10-05 18:04 ` Franck
2005-10-05 7:00 ` Franck
2005-10-05 9:46 ` Kevin D. Kissell
2005-10-05 13:20 ` Franck
2005-10-04 13:10 ` Franck
2005-10-04 13:54 ` Maciej W. Rozycki
2005-10-04 15:10 ` Franck [this message]
2005-10-04 17:11 ` Maciej W. Rozycki
2005-10-04 14:17 ` Ralf Baechle
2005-10-04 14:06 ` Ralf Baechle
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=cda58cb80510040810y286b06bcx@mail.gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@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